*** tpb has joined #tomu | 00:00 | |
*** coderobe has quit IRC | 00:27 | |
*** coderobe has joined #tomu | 01:51 | |
*** xkapastel has joined #tomu | 03:10 | |
*** xkapastel has quit IRC | 05:29 | |
*** GNUtoo has quit IRC | 14:27 | |
*** GNUtoo has joined #tomu | 14:30 | |
*** cedric has quit IRC | 15:09 | |
*** cedric has joined #tomu | 15:10 | |
*** cedric has joined #tomu | 15:10 | |
gio | Hello, I'm playing a little bit with the fomu-workshop. The usb-cdcacm is supposed to be modified to implement some interactive thing via USB, but I don't understand where in the code the USB data is processed. | 15:34 |
---|---|---|
gio | In particular, the README says that it returns every character it receives augmented by 1, and it works on my fomu. But I don't understand where this logic is implemented. | 15:35 |
xobs | gio: it's not really logic so much as it is just an interrupt handler: https://github.com/im-tomu/fomu-workshop/blob/master/riscv-usb-cdcacm/src/usb-epfifo.c#L240 | 16:26 |
tpb | Title: fomu-workshop/usb-epfifo.c at master · im-tomu/fomu-workshop · GitHub (at github.com) | 16:26 |
gio | xobs: Nice, thanks, now I see it. BTW, is there already some similar USB driver for fomu that gives me a kind of serial port between the PC and the fomu without me having to care too much about USB details? | 16:33 |
CarlFK | gio: I have seen a serial port connection to micropython on fomu, - is that close to what you are asking? | 16:41 |
CarlFK | gio: hmm, is "driver" pc os side, or fomu side of the usb connection? | 16:42 |
gio | CarlFK: I mean on the fomu side. You're right, I will investigate the micropython firmware and try to remove the micropython part. What remains should be what I want. | 16:47 |
CarlFK | gio: yay, I helped :p. more that may help: I wold look at the micropython c code for stdout things (printf?) and follow where those bytes go | 16:48 |
CarlFK | eventually they go over usb, so somewhere along that path is what you want | 16:49 |
gio | Now the problem becomes finding a micropython version that I can build from sources and make work. | 17:04 |
gio | If I upload the micropython binary that is in the fomu-workshop repository, it work. If I try to build it from the micropython repository, it builds, but it does not work. | 17:04 |
gio | (kernel complains USB is misbehaving) | 17:04 |
xobs | https://github.com/xobs/micropython/tree/fomu/ports/fomu | 17:06 |
tpb | Title: micropython/ports/fomu at fomu · xobs/micropython · GitHub (at github.com) | 17:06 |
xobs | Oh. Might be missing SET_ADDRESS functionality? | 17:06 |
gio | xobs: I tried that repository, both "fomu" and "2019-something-fomu" branches, but same result. | 17:07 |
gio | How do I know about SET_ADDRESS? | 17:07 |
gio | BTW, compiling the cdcacm example works, same toolchain and same fomu. | 17:08 |
xobs | This is the SET_ADDRESS patch: https://github.com/xobs/micropython/commit/573979203d20b42e468f95f4b6f1d9a63bb88d72#diff-597ddbd985b04dd62936e01274de3eae | 17:11 |
tpb | Title: fomu: support foboot 1.9+ · xobs/micropython@5739792 · GitHub (at github.com) | 17:11 |
gio | xobs: Wonderful, it works now! Thanks! :-) | 17:17 |
*** kaeso[m] has joined #tomu | 21:34 | |
*** techman83 has quit IRC | 22:00 | |
*** techman83 has joined #tomu | 22:03 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!