<cyrozap>
Aw, that's a bummer. The only ports I have available on this device are Ethernet, USB host, digital audio, micro-HDMI (really just DVI), and DVI-I.
<sb0>
how do you plan to debug it then?
<cyrozap>
JTAG?
<cyrozap>
Maybe I'll just boundary-scan really fast and use a very slow baud rate...
<sb0>
there are more efficient schemes for serial-over-JTAG. but you'll have to 1) write non-portable gateware to interface to the JTAG chain in your device 2) write non-portable software that creates pyts, virtual COM ports, etc. on your PC
<sb0>
might be better to take two GPIO pins and hook those up to an off-the-shelf serial/USB cable
<cyrozap>
Actually, a serial-over-JTAG module sounds like it would be a fun little project, so I think I'll try that first. This is an existing product with no GPIO available (unless I borrow some from the SPI chip or something), so I'd like to avoid soldering to it if I can help it.
<GitHub78>
[artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/v2SgV
<GitHub78>
artiq/master 9af1223 Sebastien Bourdeauducq: soc: add timer to kernel CPU system
_whitelogger_ has quit [Excess Flood]
_whitelogger has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
fengling_ has joined #m-labs
<cyrozap>
Wow, after looking through the MiSoC code, it doesn't look like it would be too difficult to make a completely-virtual UART peripheral, thanks to all the abstraction.
<GitHub24>
[misoc] sbourdeauducq pushed 1 new commit to master: https://git.io/v2SPV
FabM has quit [Quit: ChatZilla 0.9.92 [Firefox 44.0.2/20160210153822]]
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger has joined #m-labs
rohitksingh has joined #m-labs
_whitelogger has quit [Excess Flood]
_whitelogger has joined #m-labs
rohitksingh has quit [Ping timeout: 264 seconds]
<rjo>
whitequark: this latent polymorphism can be very surprising. http://paste.debian.net/411452/ both have very different outputs.
<sb0>
whitequark, what should be the return type of a C function which is used as a "-> TBool" syscall? int?
<rjo>
... the usage of TBool arguments would suggest that.
<rjo>
whitequark: and also is it correct that we tend to force argument types of kernels by giving default values to the arguments?
ylamarre has quit [Remote host closed the connection]
ylamarre has joined #m-labs
ylamarre has quit [Read error: Connection reset by peer]
key2 has quit [Ping timeout: 260 seconds]
_whitelogger has quit [Excess Flood]
_whitelogger has joined #m-labs
<rjo>
sb0: we need to start a bigger discussion on how kernels (more specifically coredevice runtime rtio api methods) should affect the timeline. we have on() off() with zero delay, pulse() that leave the timeline _after_ the pulse, dds.set() that is zero-delay, leaves the time "at" the set but affects the past hoping that there is nothing there. Now spi comes where at a device agnostic level you can only leave it either zero-delay or after the transaction is compl
<rjo>
etc etc. i have a few notes on this. will send it to the mailing list.