nRF51-DK mBed code not working on nRF51822 custom hardware (but using nRF51822-mkit target half-works...)

[seajayshore]

Question for anyone familiar with mBed code on nRF51 devices (I have cross posted on mBed, but trying my luck here too):

I'm developing an nRF51822 program using the nRF51-DK dev kit which claims to support development for both the nRF51822 & nRF51422 SoCs.

Everything works fine when run on the nRF51422-based dev. board itself, but when uploading the same firmware via nRFgo to some custom hardware that uses the nRF51822 chip the code never seems to work.

I've tried simple programs (just blinking) and more complex BLE-based programs. Nothing seems to work.

Oddly I can compile code for the nRF51822-mkit target and most things (BLE, blinking) run OK on the custom hardware. In this case I'm having trouble getting SPI & I2C working when compiled for the nRF51822-mkit target...

Any suggestions to solve either problem?

Do I need to do something else to make nRF51-DK code run on nRF51822 hardware?

Or do I need to do something else to make SPI & I2C devices run OK with nRF51822-mkit compiled firmware?

Any help is appreciated! Thanks.

[Anders Strand]

The first thing that strikes me is that your custom hardware does not have the same pin connections as the dev kits. Are you able to configure the SPI and i2c pins in your mBed code? The difference between the mKit and the newest development kits is that the mKit uses an older version of the nRF51. Which hardware revision of the nRF51 are you using on your custom hardware?

[Tanasis!]

Maybe you are not configuring Flash/RAM correctly in the linker and/or the clock-freq in the softdevice. Check this one: turlucode.com/.../