This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bootloader size exceeds limit in DFU but the actual size is smaller

Bootloader.rar

Hi, I am using Segger Embedded Studio to make a custom bootloader using S110, sdk 10.0.0. I am having a problem with the size of the bootloader, when I compile the code size is about 24 kbytes and if I upload to the chip using the programmer it goes without any problem, but if I try to do an upload using DFU it returns an error of limit size exceeded.

I debugged to see what size was returning and it is saying that the bootloader has 0x7000 bytes but it is not true, the bootloader is much smaller than this. So my question is am I missing any configuration that is making the bootloader size seems bigger than actualy is?

Thanks!  

Parents Reply
  • sorry for the delay, we are having very thin staffing here in Norway due to vacations. 

    It seems like probably the command you used to generate the DFU package might have gone wrong. Hard to say, since you managed to find out that the problem is that the DFU thinks that the size is too big, can you also debug to see how that number went in there? If not,  can you give me your project/binaries so that i can reproduce it here and try to debug

    Unfortunately, there might be delays in responses, like i mentioned as many are away on vacation.

Children
Related