SW device "no target connected " nRF52840

[Marcos Tadeo]

Hello

Im developping in nrf52840 , and created a pcb using nrf52840 qiaa 7x7

configuration

are we need to do something to first time?

because im trying to program but keil shows this 

i have no idea if need to charge a bootloader something like that, we are checking the circuit connections 

but we would like to konw if need to do  to the first time using nrf52840 qiaa 7x7 

thanks and regards

[Senchoi]

Are you supplying the power to the device? As debuggers don't supply power when connected, I guess it could be a similar issue.

[Marcos Tadeo]

Hello 

yes, we checked the power supply and its ok apparently , 1.8v in "VDD nrf" tag
I saw a post says the chip dont have a "bootloader " precharged, then that reason i cant to program the microcontroller , is this correct?

i was thinking, didnt need to do it

if yes , how can i do that ?

thanks and regards

[ketiljo]

Marcos Tadeo said:

yes, we checked the power supply and its ok apparently , 1.8v in "VDD nrf" tag

Check if the debugger supports 1.8 V. Not all does that.

You can program the device using the SWD interface without any bootloader. 

[Marcos Tadeo]

Hello 

I was checking the circuit and i did some modifications , now i was traying to add a bootloader to my IC 

i have seen the tutorial 

the cmd shows this error

i saw the datasheet nrf52840

and this post also

Disabling CTRL-AP for nRF52840 DK does not work for new nRF52833 board

i didn't catch that , how can i disable CTRL -AP, i was thinking that is the reason that i cant to program my IC,  because according to the post , "The newest revision devices (with improved APPROTECT) always requires a recover as the first step to program a blank IC (as it is locked by default, and the recover unlocks it, allowing you to write to the UICR and include firmware that unlocks it semi-permanently)."

can you help me ?

 thanks regards 

[Håkon Alseth]

Hi,

 

With newer IC revisions of the nRF52-series, an improved APPROTECT has been implemented, meaning that a recover must be performed first in order to open up the device. Please see this informational notice for more details:

https://infocenter.nordicsemi.com/pdf/in_141_v1.1.pdf?cp=4_0_2_7

 

This effectively means that you need to issue an ERASEALL command first, then program your firmware. I would recommend that you reach out to the openocd community to ask if this feature is implemented.

If you use a segger based debugger, you can use "nrfjprog --recover" and "nrfjprog --program <hexfile> --sectorerase --verify" to program.

 

Kind regards,

Håkon

[Marcos Tadeo]

hello,

thank you for your reply

Can I do it using hardware (pin  P0.18 press reset)? if no, then i need to buy a segger debuger 

becasue  im using ST Link v2,  I tried to send the command but not works, 

I tried to convert stlink to jlink also, no changes the result 

thnaks and regards 

[Håkon Alseth]

Hi,

 

Marcos Tadeo said:

Can I do it using hardware (pin  P0.18 press reset)?

No, you will need to issue SWD AP commands over the SWD interface to recover the nRF.

Marcos Tadeo said:

I tried to convert stlink to jlink also, no changes the result 

The picture that you posted shows that nrfjprog cannot find any jlink capable debuggers. are you certain that it enumerates properly as a J-Link device?

 

If you have a nRF5-series DK, you can use that as a debugger.

 

Kind regards,

Håkon

[Marcos Tadeo]

Håkon Alseth said:

are you certain that it enumerates properly as a J-Link device?

I have these one 

segger web site

Converting ST-LINK On-Board Into a J-Link

I will buy a J-link debugger, and im going to try again 

thanks and regards 

[Marcos Tadeo]

Hello

i did it, you right , i used the command nrfjprog --recover using a j-link debugger and now my IDE detected the micro i can program it also

thanks and regards 

[Håkon Alseth]

Hi,

 

Great to hear that the programming/recovering is now working!

 

Kind regards,

Håkon