build another 5340 hardware by 5340dk

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 08:54:19 GMT

[quote userid="4240" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417324"]The app core and netcore must be programmed separately. The netcore hex will be located in <build>/<child image>/zephyr/. The name of the child image is hci_rpmsg if you build a regular Bluetooth project.[/quote]

But as far as I know,according this page:(devzone.nordicsemi.com/.../hex-file-explain-about-5340-development),It says: merged_domains.hex -> Represents the merged image of application core and network core, so I was wondering if the network core and network core could be burned together. And like the light_blub routine I burned, if it's a hex file on zephyr, shouldn't this be the application core along with the network core?

RE: build another 5340 hardware by 5340dk

Vidar Berg — Fri, 24 Mar 2023 08:44:05 GMT

[quote userid="124120" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417302"]What about "light_blub"? I don't think it matters[/quote]

The OS scheduler is configured to use the 32KHz clock. So, if you have selected the wrong clock source (i.e. crystal oscillator on a board that doesn't have a crystal), you will not be able to run any of the examples.

[quote userid="124120" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417301"]I have another question, if I burn this zephyr.hex file through Programmer, is the network core and application core burned together? Or if I want to burn them separately, where is the corresponding hex file directory, which I don't know much about[/quote]

The app core and netcore must be programmed separately. The netcore hex will be located in <build>/<child image>/zephyr/. The name of the child image is hci_rpmsg if you build a regular Bluetooth project.

An overview of the different hex files generated by a build can be found here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/app_dev/multi_image/index.html#what-image-files-are

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 07:52:45 GMT

Thank you.I added 32k crystal to my own board and found that the app runs normally and the LED lights up, but I haven't tested CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in prj.conf, I will test it again later, I think it should be OK.

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 07:12:59 GMT

[quote userid="4240" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417300"]是的，很有可能。在 blinky 示例中，尝试将CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC =y 添加到 prj.conf 文件。这会将时钟源更改为内部 RC 振荡器。[/quote]

What about "light_blub"? I don't think it matters

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 07:10:30 GMT

[quote userid="4240" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417294"]You are missing one directory in the path. It should be in E:\ncs\v2.3.0\zephyr\samples\basic\blinky_pwm\build\zephyr\zephyr.hex[/quote]

I have another question, if I burn this zephyr.hex file through Programmer, is the network core and application core burned together? Or if I want to burn them separately, where is the corresponding hex file directory, which I don't know much about

RE: build another 5340 hardware by 5340dk

Vidar Berg — Fri, 24 Mar 2023 07:09:33 GMT

Yes, most likely. In the blinky sample, try to add CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to the prj.conf file. This changes the clock source to the internal RC oscillator.

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 07:07:13 GMT

That's right. Now that you mention it, I realize my board doesn't have 32kHz crystal.Is that why the program didn't start

RE: build another 5340 hardware by 5340dk

Vidar Berg — Fri, 24 Mar 2023 07:04:16 GMT

Does your board include the 32 KHz crystal?

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 07:03:04 GMT

I have tried burning other routines, such as light_switch and light_blub for matter, blinky and blinky_pwm for basic under zephyr

RE: build another 5340 hardware by 5340dk

Vidar Berg — Fri, 24 Mar 2023 06:52:59 GMT

Hi,

[quote userid="124120" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417292"]E:\ncs\v2.3.0\zephyr\samples\basic\blinky_pwm\build\zephyr.hex[/quote]

You are missing one directory in the path. It should be in E:\ncs\v2.3.0\zephyr\samples\basic\blinky_pwm\build\zephyr\zephyr.hex

[quote userid="124120" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417292"]2. I can't find my DK board where it seems to be connected to Programmer software[/quote]

Is your DK not being displayed in the Programmer app?

[quote userid="124120" url="~/f/nordic-q-a/98022/build-another-5340-hardware-by-5340dk/417292"]3. Whether I short-connect VOD and VTG to external boards, which are the same for Programmer software[/quote]

Yes, the SWD connections need to be the same as when you are programming in VS code.

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 06:44:55 GMT

Hi，

I burned light_blub using VSCODE. I also tried burning zephyr's blinky_pwm. After burning it, I measured the LED1 pins and found no PWM output, proving that the program didn't seem to be running on my board. An additional question I would like to ask is if I want to program my board through the Programmer in nRF Connect for Desktop:
1. If I want to burn blinky_pwm, where is the corresponding hex file directory? Is it in this path? E:\ncs\v2.3.0\zephyr\samples\basic\blinky_pwm\build\zephyr.hex
2. I can't find my DK board where it seems to be connected to Programmer software
3. Whether I short-connect VOD and VTG to external boards, which are the same for Programmer software

RE: build another 5340 hardware by 5340dk

Vidar Berg — Fri, 24 Mar 2023 06:42:39 GMT

Thanks. This means the external board is being programmed. So, the next step will be to find out why the FW fails to run correctly on it. Have you checked if your board works with any of the other SDK examples?

RE: build another 5340 hardware by 5340dk

ChuckRui — Fri, 24 Mar 2023 01:24:40 GMT

I have thought carefully and I understand what you mean. I have also verified it. When I short connected VDD and VTG and unplugged SWDIO and SWCLK, I tried to burn through VSCODE, but the error was shown as below
(Failed to enable coprocessor with unknown error.
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".)
When I plug in SWDIO and SWCLK, the program can burn normally, I think at least now can prove that the program has been successfully burned into the external board

RE: build another 5340 hardware by 5340dk

Vidar Berg — Thu, 23 Mar 2023 20:28:35 GMT

Hi,

Maybe I misunderstood what you meant, but I thought you were unsure whether the debugger on the DK was correctly loading the FW image to the external board or if it was programming the FW to the chip on the DK itself.

[quote user="ChuckRui"]you mean that after short, unplug SWDIO and SWDCLK, this time will be burned to the external board[/quote]

I meant to suggest this as a test to verify that the programming fails when you remove the SWD connections. This way you can confirm that you are programming the correct target, at least.

Have you tried to program other less complex applications to the board to see if they run OK on your board? The Bluetooth peripheral_lbs sample for instance?

RE: build another 5340 hardware by 5340dk

ChuckRui — Thu, 23 Mar 2023 14:40:13 GMT

Hi Vidar：

I don't think I understand.normally, I build with VSCODE and flash is burned into DK, but when I short-circuit SWDIO/SWDCLK, do the same flash operation, or even rebuild once, it will be burned to the external board, you mean to tell me not to short-circuit and try to burn, To see if it's normal? I think this must be normal because he will burn it into DK. Or I understand wrong, you mean that after short, unplug SWDIO and SWDCLK, this time will be burned to the external board, if this time can still burn normally, it means that I will burn the program to DK. Is that how you understand it?

RE: build another 5340 hardware by 5340dk

Vidar Berg — Thu, 23 Mar 2023 12:31:13 GMT

Hello,

To make sure you are programming the nRF on the ext. board, and not the one on the DK, could you try to disconnect the SWDIO/SWDCLK line and see if you are still able to flash without errors? If it still works, then that means you are programming the DK and not your board.

Best regards,

Vidar