SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Wed, 15 Jul 2015 13:11:13 GMT

Your IAR settings should match the ones like you showed in KEIL, There must be some way in IAR that you can make this in .icf file? But iif you cannot have IRAM2 configuration , then you must make some other way to make sure that globals in dfu_ble_svc.c go to NoInit part of RAM. else your code will not work. This thread has become very long, if you have any other doubts regarding it, please open another thread.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Wed, 15 Jul 2015 11:14:29 GMT

Are you talking about this settings at Keil uVIsion?

Is that the reason why it is splitted into iRAM1 and 2?

But I'm not sure if I can split it when I use IAR.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Mon, 13 Jul 2015 09:09:55 GMT

your welcome.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Mon, 13 Jul 2015 08:57:46 GMT

Alright!! Thanks alot!! You are the best!

I really appreciate you for helping a novice developer like me T.T.

Have a nice day~

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Mon, 13 Jul 2015 08:02:17 GMT

I think it does not really matter with RAM, because after the bootloader DFU is done there will be a system reset, so they can overlap. Correction 15.07.2015

It matters with IRAM settings with bootloader and make sure it does not conflict with softdevice. Bootloader uses softdevice to advertise etc, so they need to work hand in hand. sorry for the initial wrong information.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Mon, 13 Jul 2015 07:53:56 GMT

Thanks, but what about the RAM?

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Mon, 13 Jul 2015 06:59:13 GMT

you are right, when you are using bootloader you should use 0x16000 size 0x26000 for application settings. It normally worked until now with that settings even with bootloaders as applications were luckily small enough not to cross that dangerous line :)

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Mon, 13 Jul 2015 06:39:58 GMT

About 3), isn't that the setting when the firmware is not using the bootloader?

Since the bootloader's start address is 0x0003 C000, if I set the

application's size to 0x0002 9000 (0x0001 6000 ~ 0x003 EFFF) , won't it corrupt the bootloader?

Also the iRAM as well, does it?

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Mon, 13 Jul 2015 05:57:59 GMT

Your settings will be right for an application using S110 7.x softdevice, Bootloader always goes to 0X3C000 til the last page of the available flash

2)MBR and Softdevice are merged into one hex, MBR starts at 0x0000 and softdevice in that hex starts at 0x1000. When we say start, we mean that the start of vector table for that unit is located at that address. We need these start addresses to make a proper jump of transferring interrupt context from MBR to softdevice.

3)You application goes to the the address in the layout you have pointed in your point 2) Which is in your case 0x16000 --> Look here

Not 100% sure, may be Håkon can answer it.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Thu, 09 Jul 2015 13:07:45 GMT

no problem, please update us after you have tried it and accept the answer if it works :)

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Thu, 09 Jul 2015 13:05:24 GMT

Okay! Thanks for your help. I apologize that I couldn't thought whether it was iRAM or iROM and the typo

of the wrong address. I was replying with my phone so I messed up. Anyway thanks a million!!!

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Thu, 09 Jul 2015 12:58:03 GMT

Yes you need to change below in your dfu7_2.icf file (not 0x3C00 but 0x3C000. This is IROM not IRAM)

define symbol __ICFEDIT_intvec_start__ = 0x0003C000;
/*-Memory Regions-*/
define symbol __ICFEDIT_region_ROM_start__ = 0x0003C000;

yes your bootloader does not fit from 0X3C000 to end of flash if you do not set maximum optimizations. You can try it yourself and see that the linker will complain when you build your project with low optimzation level.

My bad, "debug version" is not the right word to use here, sorry, i meant "non optimized version".

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

MANGO — Thu, 09 Jul 2015 12:52:09 GMT

Due to other work, I cannot try it right now but

I just 1) need to change the linker script manually to download my bootloader at 0x3C00

and change the code optimization to high, right?

There are some points I didn't understand.

First, what do you mean by "debug version of the bootloader"?

What's the difference with the bootloader which runs at run mode?

Second, compared to Keil uVision, IAR doesn't have the option for setting the bootloader address?

I found threads that says set IRAM to 0x3C00 and I think there's no option at IAR.

Lastly, why using high level optimization is needed? To decrease the size of my firmware's code size?

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Thu, 09 Jul 2015 10:33:13 GMT

Hi Mango, I tried your project, Like Håkon said, you have to download your bootloader at 0X3C000, so you have to change the linker files. The debug version of your bootloader is big, so turn the optimizations to high and then you can compile it. I checked it atleast does not get a hardfault. If this is the same for you, please accept Håkon's answer

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Håkon Alseth — Wed, 08 Jul 2015 17:00:25 GMT

Hi Mango922,

Unfortunately, I do not have IAR installed on my home computer, but I can spot one issue. Your linker file, dfu7_2.icf, does not have the correct start address for the DFU bootloader start address set in dfu_types.h::BOOTLOADER_REGION_START.

You'll then get a hardfault as the softdevice forwards you to an unprogrammed section of the flash. Change these sections in the linker script:

*snip*
/*-Specials-*/
define symbol __ICFEDIT_intvec_start__ = 0x0003C000;
/*-Memory Regions-*/
define symbol __ICFEDIT_region_ROM_start__ = 0x0003C000;
*snip*

Forgive me if I am forgetting/not seeing any other issues, I'll team up with @Aryan tomorrow if you have any other issues.

Cheers, Håkon

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Wed, 08 Jul 2015 12:42:49 GMT

Thanks, i'll try it tomorrow, today i am kind of stuffed with other things.

RE: SDK 7.2 - DFU Bootloader - HardFault after calling sd_mbr_command

Susheel Nuguru — Wed, 08 Jul 2015 10:05:30 GMT

can you please give me your IAR project file, i can try your setup here. I do not see IAR support to that example, so i am assuming you made it yourself.