This is what I am working on,

That's quite neat    Good work.

first mismatch at byte 0x1f000

Is your bootloader larger than 124kb ????

strncpy expects char* not char[], hence things like the following can be valid.

Code:

char* Moo()
{
  static char bar[] = "Hello world";
  return bar + 1;
}

Edit: I think this is what I initially had in mind.

Edit2: @ the OP, where are you printing this or seeing the output? It could be something completely different is wrong.

What do you mean "appending 1" to textArray?  Do you mean adding 1? Or what?

Yes,

Code:

textArray++

If textArray[0] == 0, the strlen(textArray) would == 0 too. and no text should print.

It sounds more like you are appending 1 to the textArray pointer somewhere.

Could the COM port somehow still be in use?

I guess what we really need is automatic source control  

I would not want it to as I often do some modifications to a sketch, only to then upload it and revert back to the old version.

Most IDE's have the undo buffer persist beyond saving. That is what I would normally do.  Not sure if the Arduino IDE does that.

The Arduino does not save when you compile/upload. IMO that is silly. I have lost several sketches when my PC crashed and I did not save.

Now I have an OCD about it...

Did you press the reset button (if needed) before/during the upload?

Thanks moorecj. I saw that option before, but the documentation was confusing, so I didnt bother.

I agree, it is really annoying when it resets every time the USB bus does an enumeration.

It could be caused by anything.

I think it's like a bouncing button.

Perhaps add a test is code to check if returned value is 'out of expected range'.

I dont see anything wrong that is obvious. Weird indeed.

There is one tip however, notice that when it gets that 0.0 value, it also detects a new peak.

My guess would be that this new peak is probably so big, that it cant be printed correctly, as the Arduino does not print in exponential format.

So choose a sensible maximum, like 10000 perhaps, and discard any of those 'bogus' values, and just take the next sample.

Hope this helps

Make sure you are using the correct pins. They (10 - 13) are the spi pins, and should (or probably can) not be changed.

What is the errors?