Simple Thingy52 Firmware Change

RE: Simple Thingy52 Firmware Change

Jørgen Holmefjord — Thu, 21 Sep 2017 06:48:05 GMT

Yes, you will need a cable like this one, to connect the DK to Thingy for programming.

RE: Simple Thingy52 Firmware Change

honest_trefor — Wed, 20 Sep 2017 17:06:21 GMT

Ok looks like I saw an answer to my question in another blog post, the P9 connector of the Thingy needs to connec to the P19 connector of the development kit. I do not have that cable so I'm going to move to the Over The Air solutions

RE: Simple Thingy52 Firmware Change

honest_trefor — Wed, 20 Sep 2017 15:10:32 GMT

Sorry for the potentially stupid question. What does the cable connection look like? is it wired between the host computer development kit board only? or is there a wired connection between the Thingy and the development kit as well?

RE: Simple Thingy52 Firmware Change

honest_trefor — Wed, 20 Sep 2017 14:56:02 GMT

Here are the last 5 lines of make -j when running it a second time

Compiling file: crc32.c make (e=2): The system cannot find the file specified. make: *** [clean] Error 2 make: *** Waiting for unfinished jobs.... Assembly file: gcc_startup_nrf52.S

and here is the output when running make -j a third time

rm -rf _build process_begin: CreateProcess(NULL, rm -rf _build, ...) failed. make (e=2): The system cannot find the file specified. make: *** [clean] Error 2 make: *** Waiting for unfinished jobs.... Linking target: nrf52832_xxaa_s132.out make[1]: Entering directory C:/Software/Build/Nordic-Thingy52-FW/project/pca20020_s132/armgcc Preparing: nrf52832_xxaa_s132.bin Preparing: nrf52832_xxaa_s132.hex ' text data bss dec hex filename 232032 4392 20236 256660 3ea94 _build/nrf52832_xxaa_s132.out ' make[1]: Leaving directory C:/Software/Build/Nordic-Thingy52-FW/project/pca20020_s132/armgcc

RE: Simple Thingy52 Firmware Change

honest_trefor — Wed, 20 Sep 2017 14:54:11 GMT

first and last five lines when runing make -j

fist 5: rm -rf _build process_begin: CreateProcess(NULL, rm -rf _build, ...) failed. echo makefile makefile Compiling file: main.c

...

last 5: Compiling file: nrf_drv_twi.c make (e=2): The system cannot find the file specified. make: *** [clean] Error 2 make: *** Waiting for unfinished jobs.... mkdir _build

I am using the nRF Conenct Andiod app to see the device. I am not sure if I am erasing the Thingy prior, but I am setting it to Dfu mode and I see 'ThingyDfu' on the Andriod app.

RE: Simple Thingy52 Firmware Change

Jørgen Holmefjord — Wed, 20 Sep 2017 14:47:01 GMT

I tried your approach (except flashing of the bootloader), and I'm seeing the updated name. What is failing when you are compiling with GCC? Which app are you using for checking the updated name? Are you able to see the device at all? Are you erasing the Thingy before flashing the updated application?