cmcgrath5035

How are you powering the DUE – from the USB, or from independent supply?

Are you familiar with Chilipeppr?

http://chilipeppr.com/tinyg

and

https://plus.google.com/communities/104346367498010042037

It has implemented extensive execution tracking as part of the essential management of buffer fill.
I would play with it a bit, study how the tracking mechanics are implemented, then selectively leverage the parts that might be helpful. It is all Open Source code.

At the OS level(Win__ I assume) I see no reason why two tinyG’s would not connect simultaneously. The USB front end of tinyG is an ftdi discrete USB to serial device. So two tinyGs is really the same as two any other identical USB devices being connected , each should get a unique COMx port name.

I don’t know enough about WIN port assignments, specifically would they always connect as COMX and COMY, repeatedly?
In linux, udev could be used, I think, to set you computer up to always connect to a specific port based on some unique characteristic of the tinyG device (a serial number, etc). You may need to hack about a bit with this.
You would need to inform your control program that COMX was for Keypad motion, COMY for Card swipe, for example.

I have not done any G2 builds in a while, but will say you should not have to muck with the makefile. Stay away (treat as RO) from makefiles unless you are a make_guru.
Your third try form, with SETTINGS_FILE= , should do the trick.

Did you ‘make clean’ first?

IIRC, make will place your binaries (.bin and .elf) in the …/src/github.com/synthetos/g2/TinyG2/bin/gshield/ directory.
If that directory already exists, a new bin will not be built, even if all the .o files do build.
My personal method is to rename the directory there with something like gshield_mybuildxxx/. If it flashed OK, I would determine what build it was (the $fb parameter) and reedit the directory name to add that. Otherwise, you have no way to know what version you have except to run it.

Give that a try.

Yes, once tinyG2’s bootloader is installed, the native port will reflash as well..

I believe the process using the programming port is there for first time programming of tinyG2 into DUE. The programming port is implemented with a small microcoded device that emulates a USB port but has a hard coded boot interface to support the generic Arduino sketch loading process.

Footnote: Be sure to watch the build process for errors. G2 frequently makes changes or adds parameters as newer versions are created. I got burned by simply copying my_settings.h from an old version to the new settings directory in the new version tree. Make displayed a number of errors, streaming quickly across the console, when my_settings.h did not supply some expected (and required) new parameters. I use ‘diff’ to compare settings files.

Are you using Firefox 44.0.2?
I use Chrome mostly for CP, but sometimes check FF and it seems to be OK too.
EXCEPT, the security police at Mozilla have decided that openGL is a big risk. Google Firefox openGL, you find fixes you have to make to get it running. This just started for me with FF44.

Thanks for the AdBlock reference, I’ll give it a look

Have you run G2 with Chilipeppr in the past?

There is a start up buglet – the interface will appear to hang at startup, you need to click the continue – ‘~” in the TinyG widget for startup to complete.

Based on what I think I see in your screenshot, I am not sure you are getting that far.

In the Serial Port JSON Server widget(lower right corner of window), I believe there is a red background the click button for the /dev/ACM0 port, which indicates that the port is currently not the ‘default’ SPJS port.
Click the checkmark to deselect the port, then click again to reselect. Your goal is a green background.

Some additional info: the behavior you noted,

If I reset the board letting it connected, the rx line start to blink slowly (2sec on, 2sec off),

Is normal, it is a G2 heartbeat, G2 firmware is running and sane. If the heartbeat stops, G2 has crashed for some reason.

• This reply was modified 10 years, 1 month ago by cmcgrath5035.
• This reply was modified 10 years, 1 month ago by cmcgrath5035.

I occasionally run CoolTerm on openSUSE. You having issues installing or running it?

Are you connected to the DUE main port or programming port?
You want the main port.

Is G2 installed on the Due?
In CP, it should appear as /dev/ttyACM0 and ACM1