06:57 <snaz> oops wrong window mybad

07:31 <gamiee> hi karlp

07:34 <gamiee> about that ch347 and firmware, check out this: https://review.openocd.org/c/openocd/+/8746/3#message-8b62a5ff8e6bddbf9a459c6673ed06a522b2ff12

07:34 <gamiee> Tomas received firmware flash tool for ch347

07:57 <jjulian> PaulFertser: Sorry, had left early yesterday. That BSCAN tunnel in the riscv target looks similar, indeed. I also thought about implementing the encoding inside vexriscv.c. What held me back from this in the first place was the TMS encoding, as the state transitions seem to be fully controlled by the JTAG adapter and not the target. But I might

07:57 <jjulian> very well be overlooking something here

08:15 <jjulian> PaulFertser: In case you are interested, this is our implementation: https://github.com/jusst-engineering/openocd_riscv/tree/feature/lattice-hub

09:14 <PaulFertser> jjulian: looks quite OK actually. For a hack :)

09:16 <PaulFertser> I do not know of a really nice way unfortunately, it feels like it needs to be another layer of "interface" for that.

09:18 <Haohmaru> sometimes when i can't decide between 2 options - i toss a coin ;P~

09:18 <Haohmaru> other times i invent a third option and go with that one ;P~

09:24 <karlp> gamiee: yeah, I knew it could be reflashed, I had just misremembered it being advertised as a usb-hs mcu, but was mixing it up with ch378, or 564 maybe,

09:25 <karlp> also https://github.com/openwch/usb-jtag-spi is firmware for v30x with usb-hs too, which I would _guess_ is compatible? because why would they make it be different? (well.... maybe... I'v enot looked)

09:27 <Haohmaru> is this... a debugger?

09:27 <karlp> like it says, yes?

09:28 <karlp> it's the firmware for a usb2jtag/spi adapter...

09:28 <Haohmaru> but i guess, jtag only, no SWD

09:32 <karlp> in the same way that ft2232 "only" does jtag, sure...

09:32 <Haohmaru> *shrug*

10:02 <gamiee> karlp : ohhh. I wasn't aware of that at all. I thought all the functionality is done in sillicon