lkcl | you automatically have read-perms | 00:09 |
---|---|---|
octavius | sure, thanks | 00:09 |
lkcl | i can add write but please don't randomly delete or change things, it's a massive cascade of dependencies | 00:09 |
octavius | Oh don't worry, I have enough to deal with the JTAG test XD | 00:10 |
octavius | I'll make sure to pay good attention | 00:10 |
lkcl | :) | 00:10 |
octavius | I prefer to follow the rule "Don't understand, don't change it", but even for the pinmux task I had to break that hahaha | 00:11 |
octavius | I'll be off, gn | 00:15 |
octavius | Morning lkcl. Perhaps a dumb question, but how do you open multiple terminals in a schroot? Do you invoke "schroot -c" in every terminal, or do you using a multiplexing program like tmux once inside schroot? | 08:58 |
octavius | Or do you just edit your files on the host system side (by cd'ing into /opt/schroot/...) | 08:59 |
lkcl | invoke schroot -c in every terminal | 13:09 |
lkcl | i copy the ssh key into the schroot home directory. | 13:09 |
octavius | Thanks lkcl, test_jtag_tap_srv.py now runs | 15:11 |
octavius | Now I'll try to add one of the tests to the testing_stage1.py file. In the Blinker module, you instantiated a JTAG object with an empty pinset (self.jtag = JTAG({}, "sync"). Is that because on line 221 the pins are added using add_io()? | 15:27 |
lkcl | the pinsets are a red herring, they are too early. | 17:18 |
lkcl | yes | 17:18 |
lkcl | octavius, yeah have a look at the constructor of JTAG and how it derives from Pins(). i bypassed that entirely | 18:42 |
lkcl | the reason is that if you don't, add_resource doesn't work properly. | 18:42 |
* lkcl dealing with combinatorial loops on the register hazards. deep joy. | 18:43 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!