AnsweredAssumed Answered

STM32L476QE flashing verfication fails if binary size crosses to 256K

Question asked by devKhan on Jan 26, 2016
Controller : STM32L476QE 
Compiler: arm-none-eabi-gcc.exe (GNU Tools for ARM Embedded Processors) 4.7.4 20140401 (release) [ARM/embedded-4_7-branch revision 209195]
Program end into hard-fault handler before even breaking to main
 Removed previous log, as i think its problem while flashing.
We are using JLink Lite to flash the stm32l476qe , and if binary size is greater than 256K it gives below error
J-Link: Flash download: Flash programming performed for 2 ranges (6144 bytes)
J-Link: Flash download: Total time needed: 2.981s (Prepare: 0.120s, Compare: 2.726s, Erase: 0.068s, Program: 0.055s, Verify: 0.000s, Restore: 0.011s)
 
****** Error: Programming failed @ address 0x08040000 (block verification error)
Verification failed @ address 0x0803E800
Error while programming flash: Verify failed.
 
Loading binary file release/xxxx.bin
Reading 265592 bytes data from target memory @ 0x08000000.
Verify failed @ address 0x08040000.
Expected 91 read 00
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.

Read value from BANK2,
J-Link>mem 0x08040000 40
08040000 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08040010 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08040020 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
08040030 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
it gives all zeros , but binary
ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de ef be ad de


I raised same request in J-Link segger forum http://forum.segger.com/index.php?page=Thread&threadID=2899
I don't know this problem is from Jlink side or STM32L476qe side, can anyone please provide input, so that we can proceed in right direction? It would be great help.

Outcomes