Sometimes the editor will suddenly show lots (~40) of compile errors. Usually just one file but other times more than one. When I build the project, it compiles without errors. I'm getting 'Symbol TimeTick could not be resolved', 'Type OS_MBOX could not be resolved.'.
I have tried closing and open the IDE, 'Refreshing' the project, 'Clean build'. It seems the errors are all related to Netburner constants or classes. The files were all compiling fine earlier in the day. Yes, I have made some changes, but nothing that should have caused these 'spurious' errors. I can download the program to the board and the program runs normally.
This has come up a few times and usually will seem to go away by itself or I cannot remember the exact steps I did clear these errors. These errors seem to be just in a few files, I use TimeTick, Post and Pend in other places and they are all fine.
Is there some file I need to delete so the IDE will rebuild the files?
Suddenly editor shows lots of compile errors.
Re: Suddenly editor shows lots of compile errors.
I switched to Debug mode and the "errors" went away, maybe that is what I did in the past, but did not connect the two?
Re: Suddenly editor shows lots of compile errors.
I think that would only happen if you are using function calls and/or variables that are only available in debug mode. Personally, I think its always better to develop in release mode so that all the development time is also release test time. If you can specify what the errors are I can try to help.
Remember that debug mode for any platform, not just NetBurner, will disable instruction cache, data cache and optimization. It has to in order to be able to debug each line. In addition, NetBurner features such as SRAM fast ram acceleration for network buffers and code execution that greatly benefits from no wait state fast ram must also be disabled. So your application is going to run slower. So if you have an application with timing requirements and develop in debug, using any manufacturers tools, you then have to go back and see what effect the debug settings had.
I too used to always use a debugger because the tools for whatever processor I was using kind of forced it with jtag downloads and the environment. But with NetBurner network downloads that issue goes away. The network downloads to flash during development are the same mechanism you use for field updates, if enabled.
Remember that debug mode for any platform, not just NetBurner, will disable instruction cache, data cache and optimization. It has to in order to be able to debug each line. In addition, NetBurner features such as SRAM fast ram acceleration for network buffers and code execution that greatly benefits from no wait state fast ram must also be disabled. So your application is going to run slower. So if you have an application with timing requirements and develop in debug, using any manufacturers tools, you then have to go back and see what effect the debug settings had.
I too used to always use a debugger because the tools for whatever processor I was using kind of forced it with jtag downloads and the environment. But with NetBurner network downloads that issue goes away. The network downloads to flash during development are the same mechanism you use for field updates, if enabled.