Right. I considered hex display, but got stuck on how to robustly switch between a hex-mode and an ascii-mode. Unicode complicates this.
The firmware is all open-source though, and upgrade is easy, just dropping a UF2 image onto the device. So future custom protocols should be no problem.
Yeah, different firmware for different display modes is probably OK. It helps sell more hardware... ;)
It probably isn't worth the effort, but "out-of-band" signalling could be a method.
e.g. ISTR some Arduino boards have used the 1200 baud setting to trigger entry to the bootloader. Not sure why 1200 baud was chosen rather than something really obscure like 75 baud!
Looks good James - can I have one of those large Freznel lenses (Terry Gilliam's "Brazil" movie) - so I can actually read it ;)
lol, maybe provide one as an add-on for the campaign!
This sounds really handy, and I've long planned something similar (although not quite as small).
In addition to terminal mode, does it support hex display for binary protocols? Custom firmware for other protocol decoding?
FYI you mention "terminal width of 40 characters" above but on the CS page the specs say "Terminal text resolution 60x23 characters".
Right. I considered hex display, but got stuck on how to robustly switch between a hex-mode and an ascii-mode. Unicode complicates this.
The firmware is all open-source though, and upgrade is easy, just dropping a UF2 image onto the device. So future custom protocols should be no problem.
Thanks, I'll get that typo fixed with CS.
Yeah, different firmware for different display modes is probably OK. It helps sell more hardware... ;)
It probably isn't worth the effort, but "out-of-band" signalling could be a method.
e.g. ISTR some Arduino boards have used the 1200 baud setting to trigger entry to the bootloader. Not sure why 1200 baud was chosen rather than something really obscure like 75 baud!
> firmware is all open-source though
Excellent!