| *** tpb has joined #tomu | 00:00 | |
| alecthegeek | I have the bootloader working. Cool | 00:01 |
|---|---|---|
| *** alecthegeek has quit IRC | 00:02 | |
| *** alecthegeek has joined #tomu | 00:19 | |
| xobs | alecthegeek: cool! | 00:59 |
| *** NoGodDamnIdea has quit IRC | 00:59 | |
| *** alecthegeek has quit IRC | 00:59 | |
| *** alecthegeek has joined #tomu | 01:02 | |
| *** alecthegeek has quit IRC | 03:05 | |
| *** alecthegeek has joined #tomu | 03:15 | |
| xobs | Cool! Someone got eChronos running on Tomu: https://github.com/schnommus/echronos-sandbox/tree/tomu | 03:28 |
| tpb | Title: GitHub - schnommus/echronos-sandbox at tomu (at github.com) | 03:28 |
| *** alecthegeek has quit IRC | 03:45 | |
| *** alecthegeek has joined #tomu | 03:52 | |
| *** alecthegeek has quit IRC | 03:57 | |
| *** alecthegeek has joined #tomu | 04:01 | |
| dtornabene | this is super cool | 04:01 |
| *** dtornabene has quit IRC | 04:06 | |
| *** dtornabene has joined #tomu | 04:06 | |
| *** alecthegeek has quit IRC | 04:34 | |
| *** alecthegeek has joined #tomu | 04:48 | |
| *** dtornabene has quit IRC | 05:16 | |
| *** alecthegeek has quit IRC | 05:16 | |
| *** dtornabene has joined #tomu | 05:17 | |
| *** dtornabene has quit IRC | 05:18 | |
| *** alecthegeek has joined #tomu | 05:19 | |
| *** alecthegeek has quit IRC | 06:14 | |
| *** nrossi has joined #tomu | 06:20 | |
| *** alecthegeek has joined #tomu | 06:22 | |
| *** alecthegeek has quit IRC | 06:39 | |
| *** alecthegeek has joined #tomu | 06:41 | |
| *** alecthegeek has quit IRC | 07:07 | |
| *** alecthegeek has joined #tomu | 07:14 | |
| *** alecthegeek has quit IRC | 07:37 | |
| *** alecthegeek has joined #tomu | 07:41 | |
| *** alecthegeek has quit IRC | 08:06 | |
| *** alecthegeek has joined #tomu | 08:11 | |
| *** alecthegeek has quit IRC | 08:48 | |
| *** _anomaly_ has joined #tomu | 09:00 | |
| _anomaly_ | hi, is my interpretation of the tomu website correct in that to program a usb-accessible bootloader on the v0.3 boards we still need to attach an external ttl uart to the pads n the board - but can skip the pullup resistor? | 09:03 |
| _anomaly_ | *pads on the board | 09:03 |
| _anomaly_ | also, should the boards handed out at LCA2018 already have that bootloader? If so I think I might have gotten a bad unit | 09:05 |
| _anomaly_ | it appears as a cdc-acm device but after i attach a termial emulator to the tty device it just prints garbage, using 115200 8,n,1 | 09:07 |
| _anomaly_ | *terminal | 09:07 |
| nbags[m] | _anomaly_: mine didn't work right away but after stopping ModemManager it worked | 09:08 |
| _anomaly_ | not using modemmanager | 09:09 |
| _anomaly_ | i don't think, i'll check | 09:09 |
| _anomaly_ | nope | 09:09 |
| nbags[m] | I don't know then. Mine also didn't work with screen right away but did with minicom. But that was something weird going on with me I guess | 09:10 |
| _anomaly_ | ok, i am using screen, i'll try minicom | 09:10 |
| _anomaly_ | yer that's weird | 09:13 |
| _anomaly_ | screen just spews stuff constantly, but minicom has a little spat but then works | 09:13 |
| _anomaly_ | wonder what's different | 09:13 |
| _anomaly_ | thanks for the pointer though at least I can do something with it now :) | 09:13 |
| nbags[m] | And I also couldn't get the firmware on it with minicom but I gave up at that point cause I I has stuff to do | 09:14 |
| nbags[m] | Np | 09:14 |
| *** alecthegeek has joined #tomu | 09:19 | |
| _anomaly_ | "*Don't* press 'd' otherwise you'll need to use JTAG to recover the device (that is destructive upload that clears the bootloader)." | 09:39 |
| _anomaly_ | haha well i wish i read that about 3 seconds earlier | 09:39 |
| * _anomaly_ fetches the soldering iron | 09:40 | |
| nbags[m] | Oh that sucks | 09:47 |
| *** myNameIs has joined #tomu | 10:07 | |
| *** myNameIs has quit IRC | 10:12 | |
| CRImier | _anomaly_ I wonder if that's bad UX and could be safeguarded, by having to use a 2- or 3-character sequence | 10:38 |
| *** SergeiG has quit IRC | 10:41 | |
| *** SergeiG has joined #tomu | 10:43 | |
| *** alecthegeek has quit IRC | 11:00 | |
| _anomaly_ | CRImier: confirmation prompt wouldnt go astray | 11:14 |
| CRImier | That depends on whether the bootloader is meant to be exposed to people | 11:15 |
| CRImier | Also, the flash space used for it | 11:15 |
| _anomaly_ | i think 'delete and overwrite yourself' should have a confirmation either way | 11:16 |
| CRImier | If you have, say, 512 bytes for a bootloader, it might be more space-efficient to implement sequence parsing | 11:16 |
| _anomaly_ | but code size is always a concern | 11:16 |
| CRImier | As opposed to storing and displaying a string | 11:16 |
| CRImier | See, bootloader code area might be limited (I don't know if it's actually the case for tomu, but I know it is for some systems) | 11:19 |
| _anomaly_ | doesnt need to be a long string, just something to break the process in the case of spurious input or noise on the uart | 11:20 |
| _anomaly_ | maybe require the unique identifier | 11:20 |
| _anomaly_ | either way, with the way screen weirds out a stray 'd' is far too easy | 11:23 |
| kyaputen | bootloader space is shared with the rest of the programs | 11:58 |
| kyaputen | so the smaller it is, the larger other program you can put on the tomu board | 11:58 |
| kyaputen | from what I guess, the final board will have a dfu bootloader (xobs actually completed first version) | 11:59 |
| xobs | _anomaly_: If you're at LCA, you can use the tester jig we've got set up. | 12:00 |
| xobs | The DFU bootloader is a hair over 4kB, but still jumps to offset 0x4000 so that all the old code will still work (provided it resets the watchdog timer). | 12:00 |
| xobs | Code is free, however, to erase offsets 0x1400-0x4000 if it needs to use it for e.g. storage, or store code there. | 12:01 |
| kyaputen | what is below <0x1400 ? | 12:02 |
| kyaputen | also: on the bluepill with a dfu bootloader, they have a way (didn't look into it yet) to force dfu mode even if the program is running | 12:03 |
| kyaputen | I wonder how they do it | 12:03 |
| kyaputen | (so you don't need to reset a watchdog) | 12:03 |
| _anomaly_ | xobs: i think i saw it when leaving the hall, will it be there tomorrow as well? | 12:07 |
| xobs | _anomaly_: As long as nothing happens to it, it'll be there until the end of Friday. | 12:08 |
| _anomaly_ | ok ta | 12:08 |
| xobs | kyaputen: What do you mean "force dfu mode"? | 12:08 |
| xobs | With Tomu, if a program writes 0x74624346 to address 0x20000000 and reboots, it will enter DFU mode. Documented here, but perhaps I should call it out some more: https://github.com/im-tomu/tomu-bootloader/blob/master/API.md#boot-token | 12:14 |
| tpb | Title: tomu-bootloader/API.md at master · im-tomu/tomu-bootloader · GitHub (at github.com) | 12:14 |
| SergeiG | xobs: new bootloader works great! since it leaves some extra space below 0x4000, would it make sense to support set address command, so that one could upload binary with command like "dfu-util -d 1209:70b1 -s 0x1400:leave -D myfile.bin" ? | 13:49 |
| kyaputen | xobs: lemme check | 14:02 |
| kyaputen | this: https://pastebin.com/9WBKyQEe | 14:04 |
| tpb | Title: dfu-util: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be req - Pastebin.com (at pastebin.com) | 14:04 |
| kyaputen | I was referring to "Determining device status: state = appIDLE, status = 0 | 14:05 |
| kyaputen | Device really in Runtime Mode, send DFU detach request..." | 14:05 |
| kyaputen | I'm not good enough at dfu to know what that means | 14:05 |
| *** nrossi has quit IRC | 19:56 | |
| xobs | SergeiG: I didn't implement that command. I actually didn't know about it! Perhaps we can do that in a future version. | 22:43 |
| xobs | The solution I came up with was to look at offset 0x98, which ordinarily is an interrupt vector, but if the lower 16 bits are 0x6fb0 then treat bits 16-23 as the load offset. | 22:45 |
| xobs | Toboot sets those values correctly, which is how Toboot is able to replace itself. | 22:45 |
| xobs | See https://github.com/im-tomu/tomu-bootloader/blob/master/API.md#toboot-configuration-values (though again, it would be nice to call out that value more clearly.) | 22:46 |
| tpb | Title: tomu-bootloader/API.md at master · im-tomu/tomu-bootloader · GitHub (at github.com) | 22:46 |
| *** drewww has joined #tomu | 22:46 | |
| *** drewww has quit IRC | 22:53 | |
| *** seb__ has joined #tomu | 23:32 | |
| *** schnebbus has joined #tomu | 23:37 | |
| *** seb__ has quit IRC | 23:46 | |
| *** nullobject has joined #tomu | 23:47 | |
| *** schnebbus has quit IRC | 23:48 | |
| nullobject | Hi all, I got my tomu device in my LCA swag but I'm having trouble running anything on it. I've tried uploading the blinky example using minicom on macos, but it doesn't seem to be working. Any pointers would be much appreciated :) | 23:48 |
| *** mijofa has joined #tomu | 23:50 | |
| *** schnebbus has joined #tomu | 23:52 | |
| *** k-man has joined #tomu | 23:58 | |
| k-man | hi | 23:58 |
| k-man | what device does the tomu turn up as on linux? | 23:58 |
| k-man | under /dev | 23:58 |
| mijofa | k-man: With the original bootloader it came up as /dev/ttyACM0 for me | 23:59 |
| k-man | i flashed mine | 23:59 |
| *** drewww has joined #tomu | 23:59 | |
| *** drewwwau has joined #tomu | 23:59 | |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!