Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. maciekczwa
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    maciekczwa

    @maciekczwa

    1
    Reputation
    2
    Posts
    215
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    maciekczwa Follow

    Best posts made by maciekczwa

    • RE: nRF5 action!

      @alowhum

      Hi I managed to clear the access protection.

      I connected ebyte module directly to raspberry pi.

      I used this guide http://hivetool.org/w/index.php?title=BMD301 with little modifications

      Compiled openocd - current version - 7b94ae9e520877e7f2341b48b3bd0c0d1ca8a14b

      Added chip definition - I don't know if it is needed, I can check that - I have more modules to unlock

      diff --git a/src/flash/nor/nrf5.c b/src/flash/nor/nrf5.c
      index 31dd5aae..e01d7ddf 100644
      --- a/src/flash/nor/nrf5.c
      +++ b/src/flash/nor/nrf5.c
      @@ -204,6 +204,7 @@ static const struct nrf5_device_spec nrf5_known_devices_table[] = {
      
       	/* nRF52832 Devices */
       	NRF5_DEVICE_DEF(0x00C7, "52832", "QFAA", "B0",    512),
      +	NRF5_DEVICE_DEF(0x00C7, "52832", "QFN48", "B00",    512),
       };
      
       static int nrf5_bank_is_probed(struct flash_bank *bank)
      

      Started openocd:

      openocd -f interface/raspberrypi-native.cfg -c "transport select swd; set WORKAREASIZE 0" -f target/nrf52.cfg
      

      Connected with telnet to port 4444
      Commands:

      nrf52.dap apreg 1 0x0c
      nrf52.dap apreg 1 0x04 0x01
      reset
      

      I tried also with st-link but I think it doesn't support dap commands? Can anyone confirm that?

      After clearing access protection I am able to successfully flash chip with st-link.
      Now it shows in logs:
      Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
      Before it was:
      Info : nrf52.cpu: hardware has 0 breakpoints, 2 watchpoints

      Good luck with unlocking your modules:)

      posted in My Project
      maciekczwa
      maciekczwa

    Latest posts made by maciekczwa

    • RE: nRF5 action!

      @alowhum

      Hi I managed to clear the access protection.

      I connected ebyte module directly to raspberry pi.

      I used this guide http://hivetool.org/w/index.php?title=BMD301 with little modifications

      Compiled openocd - current version - 7b94ae9e520877e7f2341b48b3bd0c0d1ca8a14b

      Added chip definition - I don't know if it is needed, I can check that - I have more modules to unlock

      diff --git a/src/flash/nor/nrf5.c b/src/flash/nor/nrf5.c
      index 31dd5aae..e01d7ddf 100644
      --- a/src/flash/nor/nrf5.c
      +++ b/src/flash/nor/nrf5.c
      @@ -204,6 +204,7 @@ static const struct nrf5_device_spec nrf5_known_devices_table[] = {
      
       	/* nRF52832 Devices */
       	NRF5_DEVICE_DEF(0x00C7, "52832", "QFAA", "B0",    512),
      +	NRF5_DEVICE_DEF(0x00C7, "52832", "QFN48", "B00",    512),
       };
      
       static int nrf5_bank_is_probed(struct flash_bank *bank)
      

      Started openocd:

      openocd -f interface/raspberrypi-native.cfg -c "transport select swd; set WORKAREASIZE 0" -f target/nrf52.cfg
      

      Connected with telnet to port 4444
      Commands:

      nrf52.dap apreg 1 0x0c
      nrf52.dap apreg 1 0x04 0x01
      reset
      

      I tried also with st-link but I think it doesn't support dap commands? Can anyone confirm that?

      After clearing access protection I am able to successfully flash chip with st-link.
      Now it shows in logs:
      Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
      Before it was:
      Info : nrf52.cpu: hardware has 0 breakpoints, 2 watchpoints

      Good luck with unlocking your modules:)

      posted in My Project
      maciekczwa
      maciekczwa
    • RE: nRF5 action!

      I have the same problem with brand news ebyte modeules.

      Here are my openocd logs:

      Open On-Chip Debugger 0.10.0-dev-gdc53227 (2016-04-09-13:45)
      Licensed under GNU GPL v2
      For bug reports, read
      http://openocd.org/doc/doxygen/bugs.html
      debug_level: 2
      0x4000
      Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
      adapter speed: 10000 kHz
      Info : Unable to match requested speed 10000 kHz, using 4000 kHz
      Info : Unable to match requested speed 10000 kHz, using 4000 kHz
      Info : clock speed 4000 kHz
      Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
      Info : using stlink api v2
      Info : Target voltage: 3.241270
      Info : nrf52.cpu: hardware has 0 breakpoints, 2 watchpoints
      Error: timed out while waiting for target halted
      TARGET: nrf52.cpu - Not halted
      in procedure 'program'
      in procedure 'reset' called at file "embedded:startup.tcl", line 478
      in procedure 'ocd_bouncer'

      embedded:startup.tcl:454: Error: ** Unable to reset target **
      in procedure 'program'
      in procedure 'program_error' called at file "embedded:startup.tcl", line 479
      at file "embedded:startup.tcl", line 454
      wybrany port szeregowy at file "embedded:startup.tcl", line 454
      nie istnieje albo Twoja płytka nie jest podłączona

      posted in My Project
      maciekczwa
      maciekczwa