Home/Support/Support Forum/Customising Bootloader - Net+OS
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Customising Bootloader - Net+OS

0 votes
Hi All,

My application size is ~1.6Mb and by default only ~1.2Mb is allocated for an application memory on the Digi ConnectMe9210 module (I am using the 4Mb Flash, 8Mb RAM version). I've changed the memory allocation in my project to allow up to 2Mb of application memory. The project compiles and runs correctly in Debug with the JTAG enabled module on the development board. When I re-compile the project in Release build configuration, two files are generated within the Release sub-folder -> rom.bin and image.bin. I try to use FTP to update the rom.bin on a non-JTAG module and the whole process kind of works and the module resets after a quit command, however after reset it still powers up with the old bootloader as the memory allocation hasn't changed and the bootloader baudrate stays at 9600 (I am using 115200 throughout my project and customised bootloder).

Does anybody know if I need to do something else to update the bootloader?

Thanks for your help!

K
asked Jan 17, 2014 in NET+OS by kamaz187 New to the Community (10 points)

Please log in or register to answer this question.

2 Answers

0 votes
Do you have a serial cable attached to the serial port set up for viewing the dialog? What does the dialog say in a round the time of the FTP process and the completion of FTP, writing to FLASH and rebooting? I have never seen the behavior you are describing and I have reflashed many a module.

Also just for completeness, what version of NET+OS are yo developing with?
answered Jan 17, 2014 by dakotas_dad Veteran of the Digi Community (694 points)
0 votes
The issue has just been resolved with the help of Digi. Apparently if your application is outside the pre-configured application size, then you need to first bootload it with a smaller (<1.2Mb in size) application, which is configured for higher application siez (via right-click on the project name-> properties-> Net+OS -> Memory map) and only then you can bootload the bigger application image.

Apparently this issue has been resolved and should only appear on older modules (this is the very last character in the module serial number).

Another thing to bear in mind is that the bootloader has been overwritten, but in order for the serial port baud rate to change you have to change the NVRAM parameters at power up.
answered Jan 17, 2014 by kamaz187 New to the Community (10 points)
...