Hi.
We got Thingy for power measurement purposes. I tried first the it out of box and it works fine. Same with pre-built image.
However if I build the SDK example and flash it (Seggert j-link and nrfjprog) the I get super quick blue led flash and device doesn't appear as bt device. It seems like it's in reset loop. I've also tried using the eclipse to debug the issue, however it doesn't reach the start of main brakepoint and doesn't fe respond to pause. Also it can only show the disassembly, no code. If I use our regular sw for PCA10040 based on nRF5_SDK_12.3.0_d7731ad I can run it fine with debugger, pause, etc.
Do we have some problem with bootloader or softdevice here? Perhaps gcc version? The Makefile claims that package should use s132_nrf52_2.0.0_softdevice.hex. Isn't that a bit old? It wasn't also part of the .zip file.
This is out-of-box build with these instructions:
https://nordicsemiconductor.github.io/Nordic-Thingy52-FW/ (apart from keil stuff)
make happes with make and make flash commands on armgcc directory. Noteworthy also that regardless of the firmware I flash I have to toggle the power key to get it running.
For testing purposes I trialed this:
nrfjprog --eraseall -f nrf52
nrfjprog --program ~/Downloads/thingy_v2.1.0.HW_1.0.hex -f nrf52 (works OK)
make (in thingy_sdk_v2.1.0/project/pca20020_s132/armgcc)
make flash (reset loop)
I've also tried with soft device (s132_nrf52_2.0.0_softdevice.hex) added to mix, but that stays completely dead and device draws over 1mA:
nrfjprog --eraseall -f nrf52
make
make flash_softdevice
make flash (no signs of life)
my makefile.posix:
GNU_INSTALL_ROOT := /usr/local/gcc-arm-none-eabi-5_2-2015q4
GNU_VERSION := 5.2.1
GNU_PREFIX := arm-none-eabi
My environment:
Eclipse Neon.3 Release (4.6.3)
Ubuntu 16.04 LTS
Seggert j-link ultra+
Thinky52 1.0.1