nRF51822 GCC Eclipse HardFault in SystemInit

RE: nRF51822 GCC Eclipse HardFault in SystemInit

RK — Mon, 13 Jul 2015 05:44:39 GMT

Right - because the GCC linker script puts the stack at the end of user memory - so if you tell it you have more memory than you do, it ends up in no-mans land. If you'd checked the stack pointer when running you'd have seen the area it pointed to was all 0xFF and you BX commands weren't writing anythign there.

RE: nRF51822 GCC Eclipse HardFault in SystemInit

matterama — Mon, 13 Jul 2015 03:23:56 GMT

Thank you for your suggestion. See below, it was a dumb mistake...

RE: nRF51822 GCC Eclipse HardFault in SystemInit

matterama — Mon, 13 Jul 2015 03:23:23 GMT

THANK YOU! I had the 32kB RAM in there....the date code on the chip had AC, which was mistakenly read as the chip type, not AA like it is!

RE: nRF51822 GCC Eclipse HardFault in SystemInit

Nguyen Hoan Hoang — Mon, 13 Jul 2015 02:30:49 GMT

Check your linker script. The RAM setting may be wrong. I suspect the 32KB settings in the LD while your chip may have only 16KB.

RE: nRF51822 GCC Eclipse HardFault in SystemInit

RK — Mon, 13 Jul 2015 01:31:34 GMT

Where's your stack pointer? Sounds like you're failing on the first return from a BX which makes me wonder where it's getting the address from. I assume at the start of the function it pushes r7 and lr to the stack, should be able to see where it's pushed them and what they are.