Closed rminnich closed 1 year ago
Now, on startup, you can do this: mount -t 9p -o trans=tcp,noextend 10.0.0.1 /armory and then
ls /armory ls /armory/dev /armory/tamago-example.log
In follow-on commits, where devices are also visible, we can do this sort of thing:
see how things are set: cat /armory/dev/blue {"color": "blue","state": "on", "lasterror": }
Control them: echo off | sudo dd of=/armory/dev/blue conv=notrunc
(the notrunc is sadly necessary)
If you have a graphics device on a board you can draw to it from the linux host.
You can develop a driver that runs on the host, and, when it works, compile it into the example with no changes.
Now, on startup, you can do this: mount -t 9p -o trans=tcp,noextend 10.0.0.1 /armory and then
ls /armory ls /armory/dev /armory/tamago-example.log
In follow-on commits, where devices are also visible, we can do this sort of thing:
see how things are set: cat /armory/dev/blue {"color": "blue","state": "on", "lasterror":}
Control them: echo off | sudo dd of=/armory/dev/blue conv=notrunc
(the notrunc is sadly necessary)
If you have a graphics device on a board you can draw to it from the linux host.
You can develop a driver that runs on the host, and, when it works, compile it into the example with no changes.