Cannot get examples to work on 52-DK

Question

Still trying to get anything ta all to work on the nRF52-DK 
 
 I erased the chip 
 I flashed the soft device "soft_device_s132_v3.3.3" to address 0 and verified 
 built unmodified ~/nordic/SDK_v11.0.0/examples/ble_peripheral/ble_app_beacon/pca10040/s132/armgcc 
 Noticed that this example (andall others) had a serious error. Linker script links it at 0x1c000, but this overlaps the 3.0 soft device. Release notes for soft device say app should start at 0x1f000...examples being wrong is never a good sign... 
 modified linker script to link .text at 0x1f000 and start RAM usage at 0x20002000 
 built it 
 flashed to 0x1f000 
 still no go 
 attaching GDB shows that code runs until a call to SVCALL(SD_SOFTDEVICE_ENABLE... then the code jumps to softdevice, as expected, but it never returns, somewhere in the enable call the CPU HardFaults 
 
 SO: 
 
 What gives? 
 Why the obvious errors in the examples? 
 why does it not work at all? 
 
 Actual binary dump of the flash flashed with soft device and compiled unmodified (except linker script) sample app: mega.nz/

RK · Accepted Answer

Assuming you mean softdevice 132 v3.0.0 because there is no v3.3.3 
 The obvious error is because SDK 11 was released to support S132V2 not S132V3, it contains the V2 header files and not the V3 header files and the V2 start address and not the V3 start address. So the error is you're using an incompatible softdevice with the SDK/headers/linker scripts you're compiling against. 
 If you want to use the V3 softdevice then you need to change the include paths to point to the V3 softdevice headers (which come with the softdevice) and not the V2 ones as well as changing the linker scripts for the different memory requirements of the V3. That will mean you make structures of the correct size to send to all the calls. You may then also get compilation errors because of the changes between V2 and V3 which are documented in the migration guide, or you may find that the defaults work - you should read the migration guide anyway to see what work you have to do to use the V3 softdevice. 
 Or use the V2 one the SDK was designed for. 
 So "...examples being wrong is never a good sign..." should be "examples not even working should be a sign I've made a mistake". Perhaps your questions could be a little less snarky.