nRF5 action!

maciekczwa

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:)

alowhum

@maciekczwa said in nRF5 Bluetooth action!:

nrf52.dap apreg 1 0x0c

Thanks for the tip! Unfortunately ST-Link V2 gives:

> nrf52.dap apreg 1 0x0c
invalid command name "nrf52.dap"

(same with just "dap", which I had tried earlier).

NeverDie

@omemanti That PIR sensor lens sure has a small footprint. I'll be interested to hear how well it performs and whether you like it or not.

Omemanti

@neverdie it's the AM612, and in the little tests I did so far, it did great.

alowhum

@maciekczwa If you could share a guide to unlocking these devices, I would be very grateful. I'm have a bit of trouble still. I create an JLink device form an STM32. But even that gives the same general error on all my modules.

nrfjprog --recover
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

I tried lots of DLL versions, and a new version of nrfjprog.. no luck.

nrfjprog --recover --log
nrfjprog verion 9.7.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.

Mars Warrior

@alowhum, you seem to need Jlink Commander:

@toyman said in nRF5 Bluetooth action!:

@alowhum I intentionally asked you because I know the problem exists.
You need to erase the chip via Jlink Commander. Neither nrfjprog nor anything alse will work (AFAIK)
Actually, it was @NeverDie who found it in the beginning of his quest with nrf52. "The thing that started it all" (c)

Furthermore, It would be nice to have a small step-by-step guide to unlock and then program the ebyte module.
@Omemanti and @NeverDie are using these modules, so should be able to write something up that works for other ppl ;-)

(My ebyte modules are still on their way)

Omemanti

@mars-warrior @alowhum

For uploading code onto the Ebyte modules I use an ST-Link V2 (2 dollar USB modules).

Install the USB-Driver using Zadig
Connect the DIO, CLK VCC, and GND.
For testing purposes, I soldered just the tips of some Dupont cables to the Ebyte module and put the female parts on the ST-link.
The first time I want to upload code, I first "burn the bootloader" (Tools => burn Bootloader) (https://forum.mysensors.org/topic/6961/nrf5-bluetooth-action/386)
This will give an error.
After that, you should be able to upload sketches.

Nca78

@omemanti said in nRF5 Bluetooth action!:

The first time I want to upload code, I first "burn the bootloader" (Tools => burn Bootloader) (https://forum.mysensors.org/topic/6961/nrf5-bluetooth-action/386)
This will give an error.
After that, you should be able to upload sketches.

That's what I suggested earlier but it seems it didn't work. But I don't remember if it was with an stlink.

Omemanti

@alowhum
maybe a very stupid question, but did you check all the wires and after that if your computer uses the right drivers.

I took me quite a while to figure this out myself. Especially the driver part messes things up. Errors everywhere that referred to different problems, but after I used Zadig they all disappeared.

NeverDie

@mars-warrior said in nRF5 Bluetooth action!:

@Omemanti and @NeverDie are using these modules, so should be able to write something up that works for other ppl

As I've said many times previoiusly, I use the nRF52 DK to program external modules, and it's what I recommend for noobs because it's relatively hassle free. If you're able to use the $2 st-link v2 programmer then great, my hat's off to you. If not, I recommend the nRF52 DK rather than get frustrated and give up.

alowhum

@neverdie said in nRF5 Bluetooth action!:

nRF52 DK

Which hardware programmer do you use with that?

I find many of these software packages, like Segger's JLink stuff, are made for Windows (I'm on a mac).

gohan

@alowhum you can still install windows on it :sweat_smile:

Omemanti

@alowhum by programmer you mean in something like the Arduino ide? That's what I use ( I both use the nrf52dk =>j-link aswell the st-link v2 => st-link)

alowhum

@Omemanti I didn't realise the nRF52-DK was a hardware device. I thought it was a software program.

On the picture you provided (thanks!), are pin 6 and 8 connected to a serial port to read what's going on? Your ground is connected in a different place than mine (I connect it next to the VCC pin). I suspect both those side-pins near the antenna, at the top, where you have soldered something, are ground too, right?

Omemanti

@alowhum said in nRF5 Bluetooth action!:

@Omemanti I didn't realise the nRF52-DK was a hardware device. I thought it was a software program.

The nrf52 dev kit= > NRF52 Dev kit

To connect the DK to a module :
DK Ebyte module
GND(detect) => GND
SWDIO => SWDIO
SWDCLK => SWCLK
VTG => 3,3V
3,3V => 3,3V
GND =>GND

select J-link and there you go.

On the picture you provided (thanks!), are pin 6 and 8 connected to a serial port to read what's going on?

I used Pin 6 and 8 to connect to a FTDI to read out the serial. Since you can tell the sketch where to put the RX and TX I just connected them to 6 & 8.

Your ground is connected in a different place than mine (I connect it next to the VCC pin).

the Ebyte module has multiple GND connections, I messed the one next to the VCC up so I connected them next to the antenna. Just because I was easy ;)

I suspect both those side-pins near the antenna, at the top, where you have soldered something, are ground too, right?

Indeed!

alowhum

JLinkExe gives me this:

WARNING: RESET (pin 15) high, but should be low. Please check target hardware.

I already had some signs these EByte modules have a reset issue. As it they are constantly being reset. This points to that again. hmm.

Omemanti

@alowhum

Hey, sorry, I'm not familiar with your error messages.

Can you please sum everything up what you did so far and what your setup looks like (pic)

Drivers
Libraries
what software you use
Number of modules you tested
etc

just to retrace your steps ( It might be useful to post it in a separate topic to keep this one cleaner ) => https://forum.mysensors.org/category/5/troubleshooting