I'm having issues executing any Zephyr project on a breadboard connected to a ISP1302. It works fine on the nRF51-DK but anything I try a final hardware nothing happens. Tried LED blink, UART comms and now a beacon (because it doesn't rely on any GPIO).
I'm trying to run the zephyr beacon sample. The ISP1302 docs doesn't specify the variant of the nRF51822 on it, but it says 128kb flash and 16kb sram, so I'm assuming it's the nRF51822_QFAB
I can follow all the instructions to compile the hex/bin as per devzone.nordicsemi.com/.../ without issues.
I'm using the nrf51_blenano as a base with only 2 changes:
depends on SOC_NRF51822_QFAB
So basically assuming the same board (ble nano is very plain empty) and just changed the specific SoC.
Compilation goes fine (make BOARD=nrf51_blenano), then I'm using a ST-Link/V2 and OpenOCD to flash the SoC without issues too:
flash write_image <full path>/zephyr.hex 0
If I execute the same process on the nRF51-DK it goes without issues. Only difference is make BOARD=nrf51_pca10028 and use ./nrfjprog --program file.hex to code.
./nrfjprog --program file.hex
With the dev kit I can see the advertised beacon (using app from Google Play) and with the ISP1302 it doesn't.
For everything I tried it's usually the same. It works on the dev-kit but not on final hardware (was also trying earlier an WT51822
Do your board have a 32.768 kHz crystal? If not, you can try this solution.
Thanks Jørgen! That was exactly it. Maybe an update to this devzone.nordicsemi.com/.../ post mentioning it would be useful for developers. It's great to "Hello World" on the dev kit, but when the same code doesn't work directly on the SoC can be very frustrating (and time consuming).