RayTac mdbt42q-p512kv2 programming issue with custom board

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

AhmetSafi — Thu, 06 Nov 2025 20:43:54 GMT

Hi,

No, I cannot flash the image via west — only ST-Link is working. Thank you for your time and support. I’ve decided to stick with ST-Link, as I also found out that I can use RTT via Telnet to view the “LOG_INF” outputs. I believe I can complete my project using OpenOCD.

Best regards,

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

Amanda Hsieh — Thu, 06 Nov 2025 20:30:10 GMT

[quote user="AhmetSafi"]Starting flash is erasing flash successfully I can not see my device on scan result after flash.[/quote]

Are you able to flash the image without issue now? If so, maybe you should check the device log or test the project on the nRF52DK.

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

AhmetSafi — Thu, 06 Nov 2025 18:34:53 GMT

Hi,

Here is flash command output

And here is log file:

devzone.nordicsemi.com/.../6281.nrfutil_2D00_device.log

Starting flash is erasing flash successfully I can not see my device on scan result after flash.

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

Amanda Hsieh — Wed, 05 Nov 2025 20:05:41 GMT

Could you run

set NRFUTIL_LOG=trace
west flash (or whatever invocation you used)

in a terminal in vscode, and then send the log from <USERHOME>/.nrfutil/logs/nrfutil-device.log?

via

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

AhmetSafi — Wed, 05 Nov 2025 18:32:51 GMT

Here is JlinkExe and "nrfutils device recover" outputs:

And here is my connections:

Here is my PCB layout:

The component between VBATT and VDD is 0R resistor. I guess this should be a problem.

Here is flashing log:

I checked VTG pin with a multimeter and my custom board correctly provide 3 volts.

Thanks you for you support I hope this will be enough to diagnose my problem.

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

Amanda Hsieh — Tue, 04 Nov 2025 17:34:28 GMT

You can refer to this post for the connection and check by the J-Link Commander, also answer the questions in my previous reply. Please also provide a picture to show how you connect the custom board to the nRF52 DK.

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

AhmetSafi — Tue, 04 Nov 2025 15:04:21 GMT

I have an update on my issue. I successfully managed to program my custom Raytac board using an ST-Link v2 and OpenOCD.

I was able to erase the chip with this command:
openocd -f interface/stlink.cfg -f target/nrf52.cfg -c "init" -c "halt" -c "nrf5 mass_erase" -c "reset exit"

And I successfully flashed my merged.hex file with this command:
openocd -f interface/stlink.cfg -f target/nrf52.cfg -c "program merged.hex verify reset exit"

For my prj.conf, I'm using these clock settings:
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_LF_ALWAYS_ON=y

I used these lines because my board does not have an external crystal oscillator and I must use the internal RC oscillator.

I still don't know why the onboard J-Link on my nRF52 DK wouldn't work, even with the P19 port empty. If you see any mistake I might have made in my DK setup, please let me know. It's a bit difficult to debug this way (with OpenOCD) since there is no Virtual COM port.

Thanks for help in advance.

RE: RayTac mdbt42q-p512kv2 programming issue with custom board

Amanda Hsieh — Tue, 04 Nov 2025 14:54:51 GMT

Hi,

[quote user=""]My custom board is powered with a solid 3V.[/quote]

Do you power both your cusbom board and the nRF52DK?

What is the detected VTref value when you open the J-Link Commander?

[quote user=""]All P20 connections (GND, SWDCLK, SWDIO, RESET) are wired correctly per the DK user guide.[/quote]

Check this post.

[quote user=""] is there a special nrfjprog or nrfutil command other then "recover" needed to force the DK's J-Link to use the P20 port? I tried vs code board recover and nrf tool recovering but it did not help.[/quote]

Please run "nrfutil self-upgrade" and "nrfutil upgrade" to upgrade nrfutil and nrfutil device versions, then execute "nrfutil version" and "nrfutil list" to check they are the latest version nrfutil 8.1.1 and device 2.15.1. Now, you can run "nrfutil device recover". If it still cannot help, please provide the log.

[quote user=""]If I give up on the DK, will a J-Link EDU Mini work correctly with a 3V (not 3.3V) target board? I will buy j-link edu if it will work.[/quote]

Yes, here is a use case Error -160 on nrfjprog when verify nrf52840 using J-Link EDU Mini for nRF52840, but I think it also applies to nRF52832.

[quote user=""]Can I recover chip with using ST-link?[/quote]

We don't test with ST-Link, and we are not familiar with ST-Link.

Regards,
Amanda H.