Whenever I am working in a project set up to run after a secondary bootloader I am not allowed to download the bootloader itself because it is to be written outside the memory map defined in the project. It makes sense as it protects you from overwriting your bootloader but when you are trying to download a bootloader it is a problem. An option to disregard the memory map of the current project would be really helpful.
Also, even if I load a different project with a memory map including the area intended for the secondary bootloader, CrossStudio refuses to download the hex file. If I close CrossStudio and reopen the same project, it downloads the bootloader with no problems. I think this issue may be a bug.
Idea Originally Posted by: Jes Vestervang Jensen 27/05/2011
Please sign in to leave a comment.