| *** tpb has joined #timvideos | 00:00 | |
| *** Bertl_zZ is now known as Bertl | 00:30 | |
| mithro | CarlFK: https://docs.google.com/a/mithis.com/forms/d/18JPnOeavLZDBsA_WOXru34bbcpXRuF7qpfwdQnQdFOM/viewform | 00:36 |
|---|---|---|
| tpb | Title: Sign in - Google Accounts (at docs.google.com) | 00:36 |
| CarlFK | mithro: Your response has been recorded. thanks for poking me | 01:15 |
| *** rohitksingh has quit IRC | 02:25 | |
| *** rohitksingh has joined #timvideos | 02:40 | |
| *** rohitksingh has quit IRC | 02:46 | |
| *** miselin2 is now known as miselin | 03:33 | |
| *** miselin has joined #timvideos | 03:33 | |
| *** mithro-work has joined #timvideos | 03:55 | |
| *** mithro-work has quit IRC | 03:55 | |
| *** Bertl is now known as Bertl_zZ | 06:10 | |
| mithro | ysionneau: you wouldn't happen to be around? | 07:36 |
| ysionneau | I'm around! | 09:41 |
| mithro | ysionneau: so it turns out that EEPROM part we ended up getting ignores the address pins | 10:25 |
| mithro | ysionneau: And responds to all addresses in the EEPROM range :( | 10:25 |
| ysionneau | ouch :( | 10:26 |
| mithro | the FX2 also detects people fiddlying with it's master (IE a master collision) and then stops loading | 10:26 |
| mithro | the best solution I've come up with so far is to create a very minimal "second stage bootloader" and put that in the EEPROM | 10:27 |
| ysionneau | yep I guess it's your best move :/ | 10:27 |
| ysionneau | it always boots from i2c/real-eeprom, but then downloads another firmware via another protocol talking to the fpga | 10:28 |
| mithro | ysionneau: so it seems like the smallest bootloader I've been able to make still uses the I2C interface | 10:28 |
| mithro | I can fit one in ~50 bytes | 10:29 |
| ysionneau | nice! | 10:29 |
| ysionneau | but if the bootloader uses i2c to retrieve the fw, it will still get answers from the real eeprom, right? isn't that an issue? | 10:30 |
| mithro | ysionneau: I send a non-EEPROM addres | 10:31 |
| ysionneau | ah so the eeprom ignores the address pins but still only answers to some eeprom related slave addresses | 10:32 |
| mithro | Basically the last 3 bits of the address are in "don't care mode" | 10:37 |
| mithro | ysionneau: what I wanted to ask you is, why is the fx2 firmware segment in firmware.h 0x3FB8 big? | 10:39 |
| *** se6astian|away is now known as se6astian | 11:20 | |
| *** rohitksingh has joined #timvideos | 11:40 | |
| *** Bertl_zZ is now known as Bertl | 11:46 | |
| *** se6astian is now known as se6astian|away | 11:51 | |
| *** Bertl is now known as Bertl_oO | 12:57 | |
| MaZderMind | fyi: the first releases produced with voctomix on the 32C3 are online: https://www.youtube.com/playlist?list=PLIoqMTM7qDWouZPzI-JZP5uOyZgWfIzDK | 14:49 |
| MaZderMind | Livestream is running here: https://streaming.media.ccc.de/32c3/sendezentrum/ | 14:49 |
| tpb | Title: Sendezentrum FullHD Video – 32C3 Streaming (at streaming.media.ccc.de) | 14:49 |
| *** Bertl_oO is now known as Bertl | 15:21 | |
| *** se6astian|away is now known as se6astian | 15:58 | |
| *** Bertl is now known as Bertl_oO | 19:40 | |
| *** CarlFK has quit IRC | 20:15 | |
| *** rohitksingh has quit IRC | 20:55 | |
| *** se6astian is now known as se6astian|away | 22:04 | |
| *** CarlFK has joined #timvideos | 22:07 | |
| *** ChanServ sets mode: +v CarlFK | 22:07 | |
| *** nueces has joined #timvideos | 22:12 | |
| nueces | hi all, I see that a few pages that are included in a iframe like this https://code.timvideos.us/ideas/ don't work correctly | 22:19 |
| mithro | nueces: yeah - I tried to enable https:// and it broke a bunch of things | 22:19 |
| nueces | I get a 301 (redirect) but the iframe is not loaded, I test that on chrome and ffox | 22:19 |
| mithro | nueces: and I haven't gotten around to fixing it yet | 22:20 |
| nueces | mithro, that could be because the iframe is loading a few imgs from http instead off https like images in the issue 207 | 22:31 |
| nueces | then the browser refuse to load the whole content | 22:31 |
| *** nueces has quit IRC | 22:41 | |
| ysionneau | mithro: what do you mean about 0x3fb8 ? what's this number about? | 23:14 |
| ysionneau | if the question is "why is thhe firmware so big?" it's because I'm using a very naive approach to convert the fx2 fw into the eeprom content | 23:16 |
| ysionneau | in the eeprom you can store "regions" with a start address and a size, allowing you to leave areas untouched | 23:16 |
| ysionneau | instead of that, I'm dumping the entire firmware in .bin and then I'm only using one big fat region which start at the beginning of the fw and has the size of the fw | 23:17 |
| ysionneau | one way to have a smaller eeprom content would be to parse the intel hex format and use several smaller regions, to skip big unused spaces | 23:17 |
| mithro | Yeah | 23:18 |
| ysionneau | did you get the i2c stuff to work then? with your own bootloader protocole ? | 23:19 |
| ysionneau | were you able to load an fx2 fw? | 23:19 |
| mithro | I ran into the problem that some of my firmware has data in the scratch region - 0xE000 which made the EEPROM 64k big | 23:19 |
| mithro | But I have now created C+Python code which is able to understand the fx2 config format | 23:20 |
| ysionneau | in my tests, I think the fw was almost 64k big also IIRC | 23:25 |
| ysionneau | ah now I see the 3Fb8 indeed in the fx2fw array, yes it's big and could be optimized | 23:31 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!