2560 RobotDyn (non genuine 2560)
and using Xloader to program hardware.
other than a code indent highlighter addin a standard install of AS/MS7
Just after some opinions from the great unwashed!!!
Whilst I wait for MS7 to uninstall and hard drive checking to complete I thought I'd post a question here about some issues I am finding with MS7 and see if my issues are my naivety or an actual problem.
I am increasingly finding my code is not working properly when I upload it to my 2560 development board. Because I am new to C programming and the AS/MS7 environment I can't help think I am doing something wrong but I am beginning not to think this is not the case.
Now the first I noticed was that my serial port configuration and data transfer didn't seem to be that reliable. No matter how many times I power cycled nothing worked. Very often I would program the same code again and it would work as expected. Often if I copied my code into ArduinoIDE it proved to be more successful.
I did post a question recently and a contributor suggested as I am an ISR I make sure the internal pull-ups where enabled OK but the issues still occasionally reoccur. Then was the situation that for 1 byte change in a while loop eg. 0xBf to 0xBC caused a 2K, 300B or 600B difference in compiled code. Then there was a situation that when I was simulating code the simulator dropped out of the normal look when at the end of a function and start stepping through the code in a disassembly window and all my watch variable didn't update.
The latest is that my previously working 'top half' of my code which included the standard _delay_ms(2) stopped working then started working with 2ms delays now 1ms. However if I changed them to _delay_us(2000) it would work once on than stop, change back to ms work again for a couple of runs. then stop or change the time base again to 1.5mS aarrgghh!!
Yes - the first line of my code specify the F_CPU 16MHz base speed.
I have 'repaired' AS7 a couple of times and it doesn't seem to help, Like I said I am now completely uninstalling/reinstalling like I said I'm just curious what others think - how many times can these be reprogrammed without beginning to fail? Are they like EEPROMs and only have a certain number of flash program cycles?
Ove rto you chaps and chapesses