I have been running firmware build 089.03 for a while ( six months or so) on a Due (clone) with a GAUPS add on from Amber Spyglass in the UK. I used settings similar to gShield.
Yesterday I decided I would try out build 100.26 on a spare Due.
First off I loaded up 089.03 onto it. This Due is naked with no other board or connections. It is just for a basic test. 089.03 ran, blinked the tx led and responded happily on the native port.
I then cloned the repository and built TestV9-g2v9k binary just to check things out. I used bossac to flash it to the Due. Unfortunately there was no flashing tx led and no sign of life on the native port.
I reverted back to 089.03 just to demonstrate that the Due is still OK and everything worked fine again.
I realise this is not a lot of information to go on. I am probably doing something stupid. Does anyone have a suggestion as to what my next step might be?
Dev machine is Ubuntu 16.04LTS 64bit and I do have the 32bit compatibility libraries, so compiles are just fine.
I had read issue 272 before, but my incompetence with git let me down. I got it right this time.
What had put me off the scent though, was that with the g2v9k test build I did, I got zero response on the native port or the programming port for that matter. I guess the two ports on the Due confuses things.
As you have likely found, 100.26 sets $ej=1, json mode sticky, by default.
Chilipeppr does not care, but it makes CLI interfacing difficult unless you like reading json responses.
Setting $ej=2 will switch back to auto mode.
Yes thanks. I am aware of that.
While desk testing I have no problem reading JSON through a CLI. After all, I am looking only to see that my settings have been correctly applied and to perform a few test moves before installing in a machine for full testing.
This topic is from the original forum (July 2017). Your reply starts a new discussion linked to it.