Flash arduino code (hex file) to Custom board based on nRF52810

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Wed, 18 Jan 2023 13:28:45 GMT

[quote user="KKaushik"]Could you please guide me to some examples to configure those GPIO pins to set HIGH or LOW?[/quote]

If you just wish to use them as GPIOs then you can do so with the regular GPIO API in your application directly.
If you would like to use them for a peripheral like the UART then you would have to modify the devicetree of your application so that they UART uses these pins instead of whichever pins you currently have assigned the UART.

Best regards,
Karl

RE: Flash arduino code (hex file) to Custom board based on nRF52810

KKaushik — Wed, 18 Jan 2023 13:12:37 GMT

[quote userid="87869" url="~/f/nordic-q-a/93528/flash-arduino-code-hex-file-to-custom-board-based-on-nrf52810/405481"]On the external board?[/quote]

Yes, I'm talking about the custom PCB.

I have connected male headers directly to the pins: P0.05 and P0.08 on the custom PCB.

Could you please guide me to some examples to configure those GPIO pins to set HIGH or LOW?

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Wed, 18 Jan 2023 13:06:20 GMT

[quote user="KKaushik"]Now when I flash the code it doesn't reset the code on nRF52840 DK. So I hope it uploads the code in custom PCB.[/quote]

That's good!
If the debugger reports that the flashing was successful, and the DK program is not overwritten, then you know that the application was written to the external target.

[quote user="KKaushik"]But I haven't given any testing led on the custom board. So is there a way to serial read from pins P0.5 & P0.8?[/quote]

On the external board?
P0.05 and P0.08 can be used as GPIOs, so this will depend on how you have routed the pins on your external board and how they are configured in your application.

Best regards,
Karl

RE: Flash arduino code (hex file) to Custom board based on nRF52810

KKaushik — Wed, 18 Jan 2023 11:24:52 GMT

Now when I flash the code it doesn't reset the code on nRF52840 DK. So I hope it uploads the code in custom PCB.
But I haven't given any testing led on the custom board. So is there a way to serial read from pins P0.5 & P0.8?

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Mon, 16 Jan 2023 14:42:23 GMT

[quote user="KKaushik"]The image I attached earlier, shows the same pins connection as in the reference image you have shared.[/quote]

It seems that you do not have the split from VDD to include VTG in your connections, and you do not have GND detect connected either, which is likely why your are unable to program the target.
Please connect these so that your connections match the image I shared earlier exactly.

[quote user="KKaushik"]I have flashed the code with VS code, not the Programmer software. So I want to know, do I have to use only Programmer software for custom board flashing?[/quote]

No, you can use any programmer as the programmer will tell the debugger how to flash it, and the debugger will decide which target it should flashed based on the availability of the SWD interface.

Please remedy the connections, and let me know if you are able to program the target as expected.

Best regards,
Karl

RE: Flash arduino code (hex file) to Custom board based on nRF52810

KKaushik — Fri, 13 Jan 2023 07:36:20 GMT

Yes, I have my schematic reviewed here only before production.

Here are the private ticket IDs :

Case ID: 297698
Case ID: 299051

The image I attached earlier, shows the same pins connection as in the reference image you have shared.

I have flashed the code with VS code, not the Programmer software. So I want to know, do I have to use only Programmer software for custom board flashing?

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Fri, 13 Jan 2023 07:27:17 GMT

Yes, if the Blinky application on the DK got overwritten it means that the DK was the target of the programming, not the custom board.

Please make sure that you have all the same connection in your setup as detailed in the image shared earlier.
Have you gotten a schematic review done on your custom board prior to its production? If you create a ticket here on DevZone with the schematics we can review your integration of the nRF onto your board, to see that everything looks alright.

Best regards,
Karl

RE: Flash arduino code (hex file) to Custom board based on nRF52810

KKaushik — Thu, 12 Jan 2023 20:03:40 GMT

Hello,

I have followed the same steps and flash programmer with blinky first. Then tried to program the Custom board with the programmer. But the programmer code got changed as per the new code.

So does that mean the code didn't flash in the custom board?

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Thu, 12 Jan 2023 14:13:01 GMT

Hello,

Please see the attached image to see how you can use your DKs onboard debugger to program an external target.

I also recommend programming the DK with the Blinky application, or similar, so that you can easily see that the correct target was programmed (since the DKs leds will just cycle indefinitely).

Best regards,
Karl

RE: Flash arduino code (hex file) to Custom board based on nRF52810

KKaushik — Thu, 12 Jan 2023 12:36:02 GMT

Hello,

I have got my custom PCB and nRF52840_DK. I'm trying to program the custom board, flashing through VSCode Blinky. But it only changes the code in the nRF52DK, not in the custom board.

RE: Flash arduino code (hex file) to Custom board based on nRF52810

Karl Ylvisaker — Thu, 03 Nov 2022 12:21:36 GMT

Hello,

Please see the Debug Out section of the nRF52 DK documentation for a thorough explanation of how to use the nRF52 DK to program your custom board / external SoC.
Your connections to your external board should look like this:

A convenience tip: I would recommend that you program your nRF52 DK with a blinky application (or something similar) so that when you use it to program your external SoC you can be sure that the programming target actually was the external SoC (because the Blinky application will be unaffected by your programming of the external SoC).

Best regards,
Karl