I'm glad I could find where the problem was coming from, and hope you can find a fix for future versions.
I did saw several peoples having the exact same issue on the internet...
The right place to go is the new OneDesk page
. This code-sense case was raised and solved.
Just one more question, are you planning to include a "sort of debugger" as the one included in "Visual Micro" for boards like Arduino or Chipkit? I know that a true debugger is impossible to implement with those boards because they have not any hardware debugger but maybe one like the "Visual Micro" one ?
Visual Micro is using a technique called code injection
for providing some sort of debugging. This monopolises the serial interface and is basically the same as Serial.print()
Arduino doesn't provide any debugging facility except the Serial.print()
. chipKIT programmer costs USD27 and doesn't support GDB.
To perform real debugging, a hardware debugger is required.
As at today, the only boards featuring such built-in debugger are the LaunchPad boards from Texas Instrument:
- MSP430G2 LaunchPad with 16-bit 16 KB flash, 512 bytes RAM, 16 MHz MCU, at USD10
- MSP430F5529 LaunchPad with 16-bit 128KB flash, 8 KB RAM, 25 MHz MCU, at USD13
- and Stellaris LaunchPad now Tiva C LaunchPad with ARM 32-bit 256 KB flash, 32 KB RAM, 80 MHz MCU including FPU, at USD13, best value ever
They are supported by Energia, a fork of Arduino, and of course by embedXcode
with external debugging
. They share the same language and the same framework.
Give the LaunchPad a try: they are cheaper and more powerful!