This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I can flash in nRF51822-EK but it's not working

I use mac os x sierra on MacBook pro 2016. And I followed this link.

I took following things in order.

  1. I moved gcc-arm-none-eabi-5_4-2016q3 to /usr/local/gcc-arm-none-eabi-5_4-2016q3

  2. I moved nRF51_SDK_10.0.0_dc26b5e to ~/Library/Nordic/nRF51_SDK_10.0.0_dc26b5e

  3. I moved s110_nrf51_8.0.0 to ~/Library/Nordic/s110_nrf51_8.0.0

  4. I edited ~/Library/Nordic/nRF51_SDK_10.0.0_dc26b5e/components/toolchain/gcc/Makefile.posix like this.

     GNU_INSTALL_ROOT := /usr/local/gcc-arm-none-eabi-5_4-2016q3  
     GNU_VERSION := 5.4.3  
     GNU_PREFIX := arm-none-eabi
    
  5. I went to ~/Library/Nordic/nRF51_SDK_10.0.0_dc26b5e/examples/peripheral/blinky/pca10028/blank/armgcc. And I compiled by make all. After comiplation I got this messages.

     rm -rf _build
     rm -rf _build/*.o
     echo  Makefile
     Makefile
     mkdir _build
     Compiling file: system_nrf51.c
     Compiling file: main.c
     Compiling file: nrf_delay.c
     Compiling file: gcc_startup_nrf51.s
     Linking target: nrf51422_xxac.out
     Preparing: nrf51422_xxac.bin
     Preparing: nrf51422_xxac.hex
     
        text	   data	    bss	    dec	    hex	filename
         988	    104	     28	   1120	    460	_build/nrf51422_xxac.out
    
  6. I typed JLinkExe -device nrf51822_xxaa -if swd -speed 4000. I got this messages. (I removed S/N)

     SEGGER J-Link Commander V6.14b (Compiled Mar  9 2017 08:48:44)
     DLL version V6.14b, compiled Mar  9 2017 08:48:31
     
     Connecting to J-Link via USB...O.K.
     Firmware: J-Link V10 compiled Jan  9 2017 17:48:51
     Hardware version: V10.10
     S/N: ********
     License(s): GDB
     VTref = 2.576V
    
     
     Type "connect" to establish a target connection, '?' for help
     J-Link>
    
  7. I typed erase, I got this messages.

     Target connection not established yet but required for command.
     Device "NRF51822_XXAA" selected.
     
     
     Found SWD-DP with ID 0x0BB11477
     AP-IDR: 0x04770021, Type: AHB-AP
     AHB-AP ROM: 0xF0000000 (Base addr. of first ROM table)
     Found Cortex-M0 r0p0, Little endian.
     FPUnit: 4 code (BP) slots and 0 literal slots
     CoreSight components:
     ROMTbl 0 @ F0000000
     ROMTbl 0 [0]: F00FF000, CID: B105100D, PID: 000BB471 ROM Table
     ROMTbl 1 @ E00FF000
     ROMTbl 1 [0]: FFF0F000, CID: B105E00D, PID: 000BB008 SCS
     ROMTbl 1 [1]: FFF02000, CID: B105E00D, PID: 000BB00A DWT
     ROMTbl 1 [2]: FFF03000, CID: B105E00D, PID: 000BB00B FPB
     ROMTbl 0 [1]: 00002000, CID: B105900D, PID: 000BB9A3 ???
     Cortex-M0 identified.
     Erasing device (nRF51822_xxAA)...
     Comparing flash   [100%] Done.
     Erasing flash     [100%] Done.
     Verifying flash   [100%] Done.
     J-Link: Flash download: Total time needed: 5.406s (Prepare: 0.016s, Compare: 0.000s, Erase: 5.387s, Program: 0.000s, Verify: 0.000s, Restore: 0.002s)
     Erasing done.
    
  8. I typed loadbin _build/nrf51422_xxac.hex 0. I got this messages.

     Downloading file [_build/nrf51422_xxac.hex]...
     Comparing flash   [100%] Done.
     Erasing flash     [100%] Done.
     Programming flash [100%] Done.
     Verifying flash   [100%] Done.
     J-Link: Flash download: Flash programming performed for 1 range (2048 bytes)
     J-Link: Flash download: Total time needed: 0.181s (Prepare: 0.034s, Compare: 0.089s, Erase: 0.021s, Program: 0.012s, Verify: 0.000s, Restore: 0.022s)
    
  9. Finally I typed r, g, exit in order.

But the LEDs in nRF51822-ek were not blinking. What did I do wrong?

Parents
  • The tutorial was written for SDK 6, which is 3-4 years old, in e.g. SDK 10, nRF51-EK is not directly supported. The nRF51 chip that is on the nRF51-EK is an early revision of the nRF51 chip that is not supported on SDK versions after SDK 6. Glad to hear that you are moving over to the new and better nRF52.

Reply
  • The tutorial was written for SDK 6, which is 3-4 years old, in e.g. SDK 10, nRF51-EK is not directly supported. The nRF51 chip that is on the nRF51-EK is an early revision of the nRF51 chip that is not supported on SDK versions after SDK 6. Glad to hear that you are moving over to the new and better nRF52.

Children
No Data
Related