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

Programming a custom PCB with host MCU and Murata MBN52832 through NRF52DK P20 pins. ( "No idcode detected" Error)

Hello. I have a custom board which contains S32K148 MCU and Murata MBN52832 BLE Module and several other modules like GPS, LTE etc. Board is powered via external 12 V adapter but through voltage regulators modules are powered with 3.3V.

I am using SEGGER Embedded Studio as IDE.

I am trying to program MBN52832 module through its SWD pins using NRF52DK's P20 pins and pin connections goes like this:

P20.SWDIO ----> Custom Board SWDIO

P20.SWCLK ----> Custom Board SWCLK

P20.VTG ----> P20.VDD (To activate external flashing)

P20.GND Detect ----> Custom Board GND ( Custom board and NRF52DK have common grounds on a breadboard )

Now the problem is when I try to flash my code into custom PCB I get the following error.

"Failed to connect to target. No idcode detected. Please check connection and Target Interface Type."

I have read almost every post about external programming on here DevZone but the suggested solutions on other posts did not work for my problem.

I double-checked the board for soldering problems etc.

Application works fine on NRF52DK's internal NRF52832 SoC so I do not think it's a software based problem.

I'd appreciate any suggestion regarding this matter. Thanks in advance.

Best regards,

Furkan

Top Replies

FurkanSenol over 3 years ago in reply to Vidar Berg +1 verified

Hi Vidar, After detecting the SWDCLK pin's problem we tried to diagnose why it is pulled-up to HIGH. It seems there were several internal issues on the board. Now I am working on different board and…

Parents

0 Vidar Berg over 3 years ago

Hi Furkan,

No idcode detected indicates that the debugger is unable to communicate with the target IC. This usually means that there is a connection problem, or that the IO voltages don't match. Can you measure the voltage on the SWDIO pad on your custom board when it is powered but not connected to the debugger? The SWDIO line has an internal pull-up hand should therefore match the VDD voltage on your board.

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Cancel
0 FurkanSenol over 3 years ago in reply to Vidar Berg

Hi Vidar,

Thanks for your reply. I measured the voltage on SWDIO and got the result of 3.31 Volts

Best regards,

Furkan
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 FurkanSenol over 3 years ago in reply to Vidar Berg

Hi Vidar,

Thanks for your reply. I measured the voltage on SWDIO and got the result of 3.31 Volts

Best regards,

Furkan
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Vidar Berg over 3 years ago in reply to FurkanSenol

Hi Furkan,

Thanks for confirming the pad voltage. You may also consider disabling the reverse voltage protection circuit on your DK to better match the IO voltage on your custom board, see the "Power supply" section of the DK user guide for instructions on how to do that.

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Cancel

0 FurkanSenol over 3 years ago in reply to Vidar Berg

Hi Vidar, thanks again for your reply.

I tried shorting the related solder bridge to bypass reverse voltage protection but results were the same. I also tried using nrfjprog to get more insight about the problem. Here is the log file. Maybe you can bring something out of it.

Fullscreen 8562.log.log Download

[2022-Feb-14 14:53:21] [ info] --------------------------------------------------------------------------------
[2022-Feb-14 14:53:21] [ info] nrfjprog -f nrf52 --reset --log 
[2022-Feb-14 14:53:21] [ info] nrfjprog version 10.15.2 external
[2022-Feb-14 14:53:21] [ info] --------------------------------------------------------------------------------
[2022-Feb-14 14:53:21] [ info] Load library at C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2022-Feb-14 14:53:21] [ info] Library loaded, loading member functions.
[2022-Feb-14 14:53:21] [ info] Member functions succesfully loaded.
[2022-Feb-14 14:53:21] [debug] [ Client] - open
[2022-Feb-14 14:53:21] [debug] [ Client] - start
[2022-Feb-14 14:53:21] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence 2b4b86f2-49d0-4667-b66c-76eb3060a38a.

[2022-Feb-14 14:53:21] [trace] [ Client] - Command open executed for 85 milliseconds with result 0
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2022-Feb-14 14:53:21] [debug] [ Client] - enum_emu_snr
[2022-Feb-14 14:53:21] [debug] [  JLink] - Logger sink registered in JLink logger
[2022-Feb-14 14:53:21] [debug] [  nRF52] - open
[2022-Feb-14 14:53:21] [debug] [  nRF52] - just_check_family
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - open_dll
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2022-Feb-14 14:53:21] [ info] [SeggerBackend] - Load library at C:\Program Files\SEGGER\JLink\JLink_x64.dll.
[2022-Feb-14 14:53:21] [ info] [SeggerBackend] - Library loaded, loading member functions.
[2022-Feb-14 14:53:21] [ info] [SeggerBackend] - Member functions succesfully loaded.
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - dll_version
[2022-Feb-14 14:53:21] [ info] [SeggerBackend] - Segger dll version 7.58.b loaded.
[2022-Feb-14 14:53:21] [trace] [ Worker] - Command open executed for 14 milliseconds with result 0
[2022-Feb-14 14:53:21] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0
[2022-Feb-14 14:53:21] [debug] [ Client] - connect_to_emu_with_snr
[2022-Feb-14 14:53:21] [debug] [  nRF52] - enum_emu_con_info
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - enum_emu_con_info
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Feb-14 14:53:21] [trace] [ Worker] - Command enum_emu_con_info executed for 5 milliseconds with result 0
[2022-Feb-14 14:53:21] [debug] [  nRF52] - connect_to_emu_with_snr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - connect_to_emu_with_snr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - ---just_enum_emu_snr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - ---just_get_num_emus
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - ---just_connect_to_emu_with_snr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - ---just_connect_to_emu_without_snr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - Segger logging enabled.
[2022-Feb-14 14:53:21] [trace] [  JLink] - Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
[2022-Feb-14 14:53:21] [trace] [  JLink] - Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
[2022-Feb-14 14:53:21] [trace] [  JLink] - Hardware: V1.00
[2022-Feb-14 14:53:21] [trace] [  JLink] - S/N: 682961260
[2022-Feb-14 14:53:21] [trace] [  JLink] - OEM: SEGGER
[2022-Feb-14 14:53:21] [trace] [  JLink] - Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
[2022-Feb-14 14:53:21] [trace] [  JLink] - TELNET listener socket opened on port 19021
[2022-Feb-14 14:53:21] [trace] [  JLink] - WEBSRV WEBSRV_Init(): Starting webserver thread(s)
[2022-Feb-14 14:53:21] [trace] [  JLink] - WEBSRV Webserver running on local port 19080
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 26.496ms returns "O.K."  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_Lock()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_GetHWStatus(...)  
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.172ms returns 0  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_ExecCommand("SetRestartOnClose = 0", ...).   
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.003ms returns 0x01  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_ExecCommand("DisableFlashDL", ...).   
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.003ms returns 0x00  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).   
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.007ms returns 0x00  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_SetHookUnsecureDialog  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_SetHookUnsecureDialog(...)
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.015ms returns 0  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_TIF_Select(JLINKARM_TIF_SWD)  
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.669ms returns 0x00  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_SetSpeed(2000)  
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.139ms  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_GetSN()  
[2022-Feb-14 14:53:21] [trace] [  JLink] - - 0.007ms returns 682961260  
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - read_debug_port_idr
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - read_debug_port_register
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - ---just_read_debug_port_register
[2022-Feb-14 14:53:21] [debug] [SeggerBackend] - coresight_configure
[2022-Feb-14 14:53:21] [trace] [  JLink] - JLINK_CORESIGHT_Configure()  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 101.416ms returns 0  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_select_debug_port_register
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Select AP 255, DP Bank 0, AP Bank 255
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.227ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.266ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.234ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.121ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.229ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.228ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.232ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.204ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.088ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.229ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.222ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.179ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.096ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.204ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.267ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.277ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.226ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.238ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.239ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.247ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.161ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.180ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.144ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.116ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.101ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.005ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.015ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.002ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.033ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.051ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 0.084ms  
[2022-Feb-14 14:53:22] [trace] [ Worker] - Command connect_to_emu_with_snr executed for 227 milliseconds with result -102
[2022-Feb-14 14:53:22] [trace] [ Client] - Command connect_to_emu_with_snr executed for 237 milliseconds with result -102
[2022-Feb-14 14:53:22] [debug] [  nRF52] - close
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_IsOpen()  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 0.054ms returns 0x01  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_Lock()  
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - close
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - disconnect_from_emu
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_disconnect_from_emu
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - is_connected_to_device
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_IsConnected()  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 0.032ms returns FALSE  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_is_debug_region_powered
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_read_debug_port_register
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_select_debug_port_register
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Select AP 255, DP Bank 0, AP Bank 255
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.197ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.196ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.089ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.161ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.098ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.071ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.025ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.081ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.059ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.100ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.043ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.092ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.135ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.133ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.177ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.138ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.146ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.162ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.090ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.189ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.064ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.187ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.083ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.177ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.227ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection. 
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.228ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.185ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.193ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.164ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)  
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 1.111ms returns -1  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_HasError()  
[2022-Feb-14 14:53:22] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Feb-14 14:53:22] [trace] [  JLink] - - 0.075ms  
[2022-Feb-14 14:53:22] [trace] [  JLink] - JLINK_Close()  
[2022-Feb-14 14:53:22] [trace] [ Client] - Command close executed for 132 milliseconds with result 0
[2022-Feb-14 14:53:22] [debug] [ Client] - terminate
[2022-Feb-14 14:53:22] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0
[2022-Feb-14 14:53:22] [debug] [SeggerBackend] - Segger Backend closed.
[2022-Feb-14 14:53:22] [debug] [  nRF52] - nRF family DLL closed
[2022-Feb-14 14:53:22] [trace] [ Worker] - Command close executed for 130 milliseconds with result 0
[2022-Feb-14 14:53:22] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0
[2022-Feb-14 14:53:22] [trace] [ Worker] - Executed 5 commands for 376 milliseconds
[2022-Feb-14 14:53:22] [debug] [ Client] - Worker process exited with code: 0
[2022-Feb-14 14:53:22] [debug] [ Client] - Worker process exited with code: 0
[2022-Feb-14 14:53:22] [debug] [ Client] - Child process terminated with result 0
[2022-Feb-14 14:53:22] [trace] [ Client] - Executed 5 commands for 469 milliseconds
[2022-Feb-14 14:53:22] [debug] [ Client] - terminate

Best regards,

Furkan

0 Vidar Berg over 3 years ago in reply to FurkanSenol

Hi Furkan,

The log did not provide any additional clues, unfortunately. It shows the same problem where the programmer is unable to communicate with the target.

Another thing you may try is to reduce the clock speed. This may help if you have long programming cables.

e.g.

$ nrfjprog --recover -c 125 // 125 KHz SWDCLK

Could you also include a picture of your setup?

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Cancel
0 FurkanSenol over 3 years ago in reply to Vidar Berg

Hi Vidar,

Sorry for late response I was on leave from work for a few days.

I tried reducing the clock speed but it did not help. We also tried some other connection setups. We broke out custom boards 3.3 V line to be able to supply the MBN52832 from DK and to avoid voltage differences on 3 V lines but we still cant get to program the module. You can see my setup in images below. I cant provide a full photo of custom board due to privacy issues but the thing is SWDIO, SWDCLK and GND pins are break-out pins from custom board.

I read in other posts that RESET and SWO pins are unnecessary for external programming. But I am wondering if they could help me solve my problem.

And my colleague had an idea. MBN52832 module's UART line is connected to S32K148 MCU. Could it prevent the module from communicating through SWD pins? ( Just a thought ).

Best regards,

Furkan
Cancel
Vote Up 0 Vote Down

Cancel
0 Vidar Berg over 3 years ago in reply to FurkanSenol

Hi Furkan,

Reset and SWO are optional, and SWO is rarely used anyway. The UART lines should not be a problem either.

Do you have only one board to test on?

Best regards,

Vidar
Cancel
Vote Up 0 Vote Down

Cancel