01:53 <slagernate> perhaps my radiant isn't working is bc I'm running Ubuntu 22.04. It ran a few times but now it seems broken when using the blinky.v and blinky.pdc from the example in pjroxide: `@E| Mal-formed command line - please check for extra ` `quotes in macro specification'. Has anyone tried radiant on Ubuntu 22.04? Even the gui is whacked. Maybe I should

01:53 <slagernate> revert to a previous OS / use a docker / VM.

19:35 <tpw_rules> i failed many moons ago and on a completely different platform, but even today i still cannot get litex_term to upload a file over jtag

19:36 <tpw_rules> safe mode does not help. it just says unexpected response from device: 'b'E''

19:37 <tpw_rules> the bios works great and the memory test passes

19:38 <tpw_rules> i can type stuff in and run commands fine

19:39 <cr1901> You're not going to like this response, but I'm pretty sure I've seen this error before and I forget the solution

19:39 <tpw_rules> the file is only a few kilobytes. even uploading a 3 byte file does not work

19:40 <tpw_rules> i'm just ranting to build energy to dig into the code

19:43 <tpw_rules> so the E means timeout which means either the value is too short or the timer is broken

20:58 <tpw_rules> patched the timeout out of the bios and the upload runs at a breathtaking 74 bytes per second

20:59 <tpw_rules> not sure why. reading back from the jtag port seems to go quite quickly

21:00 <tpw_rules> like the donut demo is clearly cpu limited, not waiting for characters to be received

21:16 <tpw_rules> the protocol is symmetric, this makes no sense. is it an interrupt problem or something?

21:55 <tpw_rules> ok cool, some minor tweaks to the tcl and now we're above 1000 bytes per second

21:55 <tpw_rules> (wow that is a cursed language)

23:24 <tpw_rules> cr1901: just filed a PR to fix this properly, do you still have a setup which uses jtag_uart?

23:33 <cr1901> No, not on me, I'm afraid :/