Building with Microlib:
s_tx_buffer 0x100015d0 Data 2050 bluetooth_frame_handler.o(.bss) STACK 0x10001dd8 Section 304 startup_lpc11xx.o(STACK)
"s_tx_buffer" goes until 0x10001DD2 - but the stack grows backwards...? This causes data corruptions - of course!
withuot Microlib:
s_tx_buffer 0x100015cc Data 2050 bluetooth_frame_handler.o(.bss) .bss 0x10001dd0 Section 96 libspace.o(.bss) HEAP 0x10001e30 Section 0 startup_lpc11xx.o(HEAP) STACK 0x10001e30 Section 304 startup_lpc11xx.o(STACK) Heap_Mem 0x10001e30 Data 0 startup_lpc11xx.o(HEAP) Stack_Mem 0x10001e30 Data 304 startup_lpc11xx.o(STACK)
Which looks better and indeed causes no corruptions.
Any updates?
Any news? Keil update of serious linker bug imminent?
Update for MDK-ARM released two days ago.
http://www.keil.com/download/product/
No doubt, a rush release to fix the Dealy linker bug.
But wait. No mention of it in the release notes.
Jeez, must be a tough one for the Keil development team to fix!?
i get a error in link. u got fix????
Maybe the OP will give us an update on that nasty Dealy bug?