| *** tpb has joined #tomu | 00:00 | |
| *** awe00 has quit IRC | 00:01 | |
| *** emeb has quit IRC | 00:01 | |
| *** rohitksingh has quit IRC | 00:10 | |
| *** rohitksingh has joined #tomu | 00:38 | |
| *** whatnick has joined #tomu | 00:42 | |
| *** tom_ has joined #tomu | 00:58 | |
| *** tom_ has quit IRC | 01:03 | |
| *** whatnick has quit IRC | 01:04 | |
| *** rohitksingh has quit IRC | 01:13 | |
| *** rohitksingh has joined #tomu | 01:44 | |
| *** futarisIRCcloud has joined #tomu | 03:35 | |
| TomKeddie | mithro: I'm back in town, hoping to close that RGB PR. The gateware I build unmodified from your repo doesn't give me a bios prompt on icebreaker. Is this something new? I'm following the micropython wiki (https://github.com/timvideos/litex-buildenv/wiki/HowTo-FuPy-on-iCE40-Boards) Any debug tips? I guess I could look at recent PRs and roll back to see where it broke? | 03:52 |
|---|---|---|
| tpb | Title: HowTo FuPy on iCE40 Boards · timvideos/litex-buildenv Wiki · GitHub (at github.com) | 03:52 |
| *** rohitksingh has quit IRC | 05:13 | |
| *** rohitksingh has joined #tomu | 05:36 | |
| *** rohitksingh has quit IRC | 05:50 | |
| mithro | TomKeddie: I had something working on the icebreaker recently but will check again when I get to the camp | 06:54 |
| mithro | Just landed in Berlin | 06:54 |
| *** xkapastel has joined #tomu | 07:48 | |
| *** cedric has quit IRC | 07:49 | |
| *** cedric has joined #tomu | 07:49 | |
| *** cedric has joined #tomu | 07:49 | |
| xobs | Well, I think I have the SET_ADDRESS issue solved. It works with both the dummyusb and epfifo cpu interfaces. | 07:55 |
| xobs | The only thing I have to do now is get the updater working again. | 07:55 |
| xobs | I recently rewrote the updater to make it harder to brick a Fomu by pulling power during an update. But it seems not well tested. At least it's not bricking my test unit! | 07:57 |
| *** olasd has quit IRC | 09:41 | |
| *** olasd has joined #tomu | 09:44 | |
| *** awe00 has joined #tomu | 09:51 | |
| *** futarisIRCcloud has quit IRC | 10:34 | |
| *** xkapastel has quit IRC | 11:07 | |
| TomKeddie | mithro: thanks, no rush. Enjoy the camp. | 11:43 |
| MadHacker | xobs: "Not bricking" is a good starting point. :) | 12:17 |
| *** awe00 has quit IRC | 12:47 | |
| tmbinc | xobs: is an EVT2 still good? (the one you gave me in december) | 12:54 |
| tmbinc | I could test the SET_ADDRESS fix then if it resolves my issue | 12:54 |
| tmbinc | but actually i think for whatever reason windows is asking for descriptor 0x0600, which FOMU STALLs as it doesn't exist | 12:55 |
| tmbinc | ... i have no idea why windows would ask for that descriptor | 12:55 |
| *** awe00 has joined #tomu | 13:07 | |
| xobs | tmbinc: they're about the same, yeah. I just haven't built a bitstream for it yet. | 13:11 |
| tmbinc | ok just flashed top-of-tree foboot and worked fine (i.e. on linux; still not on windows) | 13:12 |
| tmbinc | so yeah EVT2 seems to work fine for me; if you have a fix, I can test it | 13:13 |
| MadHacker | I've a fomu here for testing too, and I don't mind if it bricks it and I need to JTAG it back to health later. | 13:25 |
| MadHacker | (Well, SPI) | 13:25 |
| *** awe00 has quit IRC | 13:37 | |
| *** emeb has joined #tomu | 14:01 | |
| tnt | psa, I'm at the camp, I have free fomu hackerboards and also test jig to flash them. | 14:12 |
| xobs | I'm in an airport. I'll be at camp in... Some number of hours. Probably in about 18 hours. | 14:13 |
| xobs | MadHacker: thanks for the help. I'm glad you're able to test it, and I'm sorry you have to! | 14:14 |
| xobs | It's requesting descriptor 0600? | 14:14 |
| tmbinc | this maaay be related with me having UsbDk (that spice USB redirection thingie) installed | 14:15 |
| tmbinc | But all other USB devices still work | 14:15 |
| tmbinc | I've checked the Windows USB ETW but meh i fail at windows | 14:15 |
| tmbinc | Best I could figure out it fails at "reading the device descriptor with 0xC0000004" (USBD_STATUS_STALL_PID ) | 14:16 |
| xobs | tmbinc: oh. Hmm... Yes, I didn't check for USB resets. It was a Stage 1 Hack. | 14:16 |
| tmbinc | but the Urb indicates that's while reading the device descriptor, not while reading a random other descriptor | 14:16 |
| xobs | Though if it's stalling, then that means it's actually responding. | 14:16 |
| tmbinc | I think the STALL response is actually fine | 14:17 |
| tmbinc | after that it's doing 80 00 00 00 00 00 02 (GET_STATUS) | 14:17 |
| tmbinc | which the device responds "00 00" which should be fine | 14:17 |
| tmbinc | then windows is doing 00 09 01 00 00 00 00 00 (set configuration 0), which should be fine as well | 14:18 |
| xobs | You sure it's not Windows asking for the USB high speed descriptor? You're supposed to stall those. | 14:18 |
| tmbinc | then it doesn't do anything [visible; i think OV isn't showing me the port reset] and then it's reading the device descriptor from address 0 | 14:18 |
| xobs | That seems normal. | 14:18 |
| tmbinc | but why is it not happy / why is it port-resetting? | 14:19 |
| xobs | And dfu-util -l or wishbone-tool can't see it? | 14:19 |
| tmbinc | (aside from the fact that it doesn't handle the reset) | 14:19 |
| tmbinc | well it keeps attempting to read the device descriptor after that, and it appears as "code 43" in the device manager | 14:19 |
| xobs | That does seem ungood. | 14:20 |
| xobs | Well. Hopefully we can coax the Beagle into working again. | 14:20 |
| tnt | tmbinc: can you post the ovftdi log ? | 14:21 |
| tmbinc | xobs: I have a $$$ commercial USB3 analyzer (Teledyne/LeCroy) but I'm not ready to admit defeat yet and stop using OV to debug it :) | 14:21 |
| tmbinc | tnt: http://tmb.elitedvb.net/tmp/M5N7G6xXmH/fomu2.pcap | 14:21 |
| tmbinc | ignore the crap at beginning and end | 14:22 |
| tmbinc | (needs nightly wireshark) | 14:22 |
| tnt | tmbinc: arf yeah, I don't use wireshark, I just use the text log. | 14:23 |
| tmbinc | i have that, too, just a second | 14:24 |
| tmbinc | http://tmb.elitedvb.net/tmp/fomu.log | 14:28 |
| tmbinc | xobs: you're right, 0x0600 is the "device qualifer" and should be STALLed | 14:30 |
| tmbinc | so that's not the issue | 14:30 |
| tnt | Yeah, there is really nothing wrong in that log. | 14:32 |
| tmbinc | ooh, maybe this is the missing address filter overall? | 14:32 |
| tmbinc | if i unplug my FS keyboard, it'll work | 14:32 |
| tmbinc | so likely the hub doesn't have a per-port TT | 14:32 |
| tmbinc | tnt: I don't understand the final "READ DEVICE DESCRIPTOR" from address 0 though | 14:33 |
| tmbinc | why is it doing that? | 14:33 |
| tnt | Well , but bus was reset between that and the set configuration before. | 14:37 |
| *** awe00 has joined #tomu | 14:38 | |
| tmbinc | ok indeed the set_address fix (taken from master) fixes it | 14:40 |
| tnt | interesting the OV log shows really nothing wrong :/ | 14:41 |
| tmbinc | maybe the issue happens in the beginning - we see a couple of "IN" tokens to address 21 | 14:46 |
| tmbinc | and the OV will respond to those | 14:46 |
| tmbinc | so it caused a reset of my FS keyboard on the same TT | 14:47 |
| tmbinc | so the READ DEVICE DESCRIPTOR we see at the end is really meant for the keyboard, but since both devices respond, it never works | 14:47 |
| tmbinc | this is also why - in the other log - we see a couple of NAKs but no furhter retries | 14:47 |
| tmbinc | (because the OV saw the NAK from FOMU, but the host likely saw something else / nothing valid) | 14:48 |
| xobs | tmbinc: it shouldn't be naking with the fix. Are you still seeing that? | 14:48 |
| tmbinc | http://tmb.elitedvb.net/tmp/fomu2.log | 14:49 |
| tmbinc | note how it keeps polling 30.1 | 14:49 |
| tmbinc | (which appears to be the keyboard) | 14:49 |
| tmbinc | and no NAKs anymore | 14:49 |
| tmbinc | (from fomu) | 14:49 |
| tmbinc | I think it's fixed | 14:50 |
| xobs | The beginning is kinda ugly, though. | 14:50 |
| tmbinc | the noise? | 14:51 |
| xobs | Yeah. Is that just something floating? | 14:51 |
| tmbinc | I think that's just the hub being high impedance or maybe high speed? | 14:51 |
| tmbinc | it's an openvizsla problem | 14:51 |
| xobs | Oh, okay! | 14:52 |
| xobs | So I'll work on the updater and then we can push the update. | 14:53 |
| tmbinc | can the bootloader be updated? | 14:53 |
| tmbinc | i forgot, is it just in flash at 0? | 14:53 |
| xobs | It's possible to load 1.9 onto a production unit to test it. I've done that, so I concur it works. | 14:53 |
| xobs | I have an updater that's half written. Two, actually. | 14:53 |
| tmbinc | Happy to test that on an EVT :) | 14:54 |
| xobs | One is a naive proof of concept that'll Brick your device if you unplug it during the 17 seconds it takes to update. | 14:54 |
| xobs | The new one cuts the critical window down to just a few ms. | 14:54 |
| tmbinc | how? | 14:54 |
| xobs | tmbinc: the first thing it does is check itself to make sure it's valid. The next thing it does is erase block 0 and make it point to itself. | 14:56 |
| xobs | Sp it'll resume the update if it gets reset. | 14:56 |
| tmbinc | ah using this "boot applet"? | 15:00 |
| xobs | tmbinc: https://github.com/im-tomu/foboot/blob/master/booster/README.md | 15:04 |
| tpb | Title: foboot/README.md at master · im-tomu/foboot · GitHub (at github.com) | 15:04 |
| xobs | Wow. I stopped writing mid sentence. | 15:10 |
| tmbinc | nit: 20097151 has an extra 0 :) | 15:12 |
| xobs | That's around the time I started working on the new version of the USB core. The idea was to try avoiding needing to update at all. Guess that's not happening now. | 15:12 |
| tmbinc | well it was close i guess? | 15:15 |
| xobs | I'm glad I had it ready. | 15:15 |
| xobs | When I tried it earlier today it just gave an error. I don't have the ability to debug it at the moment. | 15:18 |
| xobs | I'll try hooking up https://github.com/im-tomu/valentyusb/blob/master/src/usb-epfifo.c (and adding SET_ADDRESS support to that file), which should be enough to placate the host to let me hook up gdb. | 15:20 |
| tpb | Title: valentyusb/usb-epfifo.c at master · im-tomu/valentyusb · GitHub (at github.com) | 15:20 |
| xobs | Brb, taking off now. | 15:20 |
| tmbinc | see you tomorrow | 15:23 |
| *** xkapastel has joined #tomu | 15:34 | |
| *** awe00 has quit IRC | 15:35 | |
| mithro | I'm sitting in a hammock in the hardware hacking village | 16:03 |
| mithro | tnt: I'm at camp too! | 16:05 |
| *** awe00 has joined #tomu | 16:16 | |
| *** im-tomu_ has left #tomu | 16:28 | |
| *** kristianpaul has joined #tomu | 16:28 | |
| kristianpaul | \o/ | 16:28 |
| *** im-tomu_ has joined #tomu | 16:28 | |
| *** awe00 has quit IRC | 16:32 | |
| xobs | mithro: sounds pleasant. | 16:47 |
| *** awe00 has joined #tomu | 16:59 | |
| tnt | mithro: \o/ | 17:01 |
| tnt | I'm at the Singularity city hacker tent. I also have a bunch of icebreaker boards for sale at a discount in addition to the free fomus. | 17:02 |
| xobs | I feel like I should have brought more evt boards. | 17:07 |
| xobs | But I also have a bunch of busted dvt boards that people can turn into jewellery. | 17:08 |
| *** awe00 has quit IRC | 17:12 | |
| *** im-tomu_ has left #tomu | 17:24 | |
| *** im-tomu_ has joined #tomu | 17:24 | |
| mithro | tnt: I have lots of Fomu boards + chubby + pano logic devices | 17:30 |
| *** xkapastel has quit IRC | 17:44 | |
| *** NoGodDamnIdea has joined #tomu | 18:00 | |
| *** emeb has left #tomu | 18:10 | |
| *** awe00 has joined #tomu | 18:24 | |
| *** r has joined #tomu | 19:16 | |
| *** tmarble has joined #tomu | 20:04 | |
| *** renatosrabelo has joined #tomu | 20:19 | |
| renatosrabelo | hi guys. Is there a fomu channel ? | 20:20 |
| tnt | sort of. You're in it :) | 20:21 |
| renatosrabelo | my fomu just arrived. Is there a quick start guide like tomu ? | 20:21 |
| renatosrabelo | i guess the this one | 20:24 |
| renatosrabelo | https://github.com/im-tomu/fomu-toolchain | 20:24 |
| tpb | Title: GitHub - im-tomu/fomu-toolchain: A collection of tools for developing for Fomu (at github.com) | 20:24 |
| tmarble | I just got my fomu too.. it's adorable! micropython just worked^TM :) | 20:41 |
| shapr | I've been working through https://p.xobs.io/td19/ and https://github.com/im-tomu/fomu-workshop with my fomu | 20:47 |
| tpb | Title: Fomu: An FPGA in your USB Port (at p.xobs.io) | 20:47 |
| *** W1lkins has quit IRC | 20:52 | |
| *** W1lkins has joined #tomu | 20:53 | |
| shapr | I'm cautiously trying to upgrade my crowdsupply fomu from 1.8.7, is it correct that I should run "python3 foboot-bitstream.py --revision evt" ? | 21:55 |
| shapr | that is, inside foboot/hw from https://github.com/im-tomu/foboot ? | 21:55 |
| tpb | Title: GitHub - im-tomu/foboot: Bootloader for Fomu (at github.com) | 21:55 |
| *** emeb has joined #tomu | 21:58 | |
| *** xkapastel has joined #tomu | 22:00 | |
| shapr | once I've modified the source and produced riscv-blink.elf how do I load that file onto the fomu? | 22:12 |
| shapr | well, dfu-util -D riscv-blink.elf didn't seem to kill anything? | 22:14 |
| shapr | I want to build verilog-blink for my crowdsupply-shipped fomu, would I set FOMU_REV=evt1 ? | 22:18 |
| shapr | needs to be FOMU_REV=pvt1 the other options don't work! | 22:23 |
| *** futarisIRCcloud has joined #tomu | 23:17 | |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!