sng has quit [Read error: Connection reset by peer]
sng__ has quit [Remote host closed the connection]
monstr has joined #u-boot
sng has joined #u-boot
monstr has quit [Ping timeout: 260 seconds]
sng has quit [Remote host closed the connection]
prabhakarlad has quit [Quit: Client closed]
slobodan has joined #u-boot
sng has joined #u-boot
sng__ has joined #u-boot
sng_ has quit [Read error: Connection reset by peer]
sng has quit [Remote host closed the connection]
prabhakarlad has joined #u-boot
vagrantc has joined #u-boot
mckoan is now known as mckoan|away
haritz has joined #u-boot
haritz has quit [Changing host]
haritz has joined #u-boot
frieder has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 246 seconds]
monstr has joined #u-boot
monstr has quit [Read error: No route to host]
monstr_ has joined #u-boot
<Hammdist>
hello all. I would like to trace some I/O of u-boot. the problem is how do I transfer the trace to my computer. I know there is a command that will dump the trace to the serial port, but unfortunately my version of `screen` gets borked when the logging to file feature is enabled. are there any other options?
<Hammdist>
I'm on debian sid with screen version 4.9.0-4
ikarso has quit [Quit: Connection closed for inactivity]
monstr_ has quit [Remote host closed the connection]
<marex>
Hammdist: use something else, like minicom ?
mmu_man has joined #u-boot
<Tartarus>
Uh, I've never heard of the log feature in screen failing
<Tartarus>
it'll happily capture binary garbage, even
<Hammdist>
by borked I mean it skips ranges of characters (apparently "randomly") and they do not appear on the screen nor in the file. I'll give minicom a try
<Tartarus>
Ah
<Tartarus>
I would look to the serial connection itself, not the sw
<Hammdist>
works %100 when file logging is off though *shrug*
<Tartarus>
odd, yeah
slobodan has quit [Remote host closed the connection]
slobodan has joined #u-boot
<vagrantc>
Hammdist: i also recently learned about "tio" which has some nice features