nRF52832 Custom board designing on single side pcb

RE: nRF52832 Custom board designing on single side pcb

awneil — Mon, 07 Oct 2019 14:00:07 GMT

You may have misunderstood the term "module" as used in this context.

When Nguyen Hoan Hoang and I recommend that you use a module, we are referring to a component which contains the nRF52832 and essential RF parts, and you then incorporate into your PCB design - like this:

RE: nRF52832 Custom board designing on single side pcb

Kaja — Mon, 07 Oct 2019 13:40:53 GMT

Great,

I just replied you.

For the public ticket:

It's not easy to do the grounding correctly in just one layer, it's very important to ground the RF components properly. Also, for good antenna gain, the ground plane needs be be as large as possible, not small traces.

We have not done any reference designs with one layer, and we do recommend using 2 or more layers.

Best regards,
Kaja

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Sun, 06 Oct 2019 12:14:43 GMT

Thank you guys recommendation for a well made Nordic modules I can use.

But, I am trying to make my own pcb substrate, lines to make my own module. I know my skill and knowledge with designing or testing PCB is too lack to make a one, but want to make working anyway module.

Thank you by the way

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Sun, 06 Oct 2019 12:11:19 GMT

I attached two files on message to you Kaja. Hope you review my HW designs

RE: nRF52832 Custom board designing on single side pcb

awneil — Fri, 04 Oct 2019 15:02:34 GMT

[quote userid="3482" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb/213457"]May I suggest you to use a module[/quote]

Absolutely!!

It seems that you don't have much experience with designing or testing PCBs.

And this is not just any PCB - it is a radio system!

RF design is a specialist subject, requiring specialist skills, experience, and test equipment.

devzone.nordicsemi.com/.../191537

Unless you have those skills - a module really is the answer!

Nordic have a list of modules here:

https://www.nordicsemi.com/Software-and-Tools/3rd-Party/3rd-party-modules

RE: nRF52832 Custom board designing on single side pcb

awneil — Fri, 04 Oct 2019 14:56:55 GMT

[quote userid="76601" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb/213345"]by multimeter ( not sure its a right way to verifying). [/quote]

A multimeter won't show you if you have noise, glitches, drop-outs, etc on your supply.

As noted earlier, you single-sided design with thin tracks is quite likely to suffer from such things!

[quote userid="76601" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb/213345"]Is there any other method to verify the power?[/quote]

As mentioned earlier, you need an oscilloscope!

RE: nRF52832 Custom board designing on single side pcb

Nguyen Hoan Hoang — Fri, 04 Oct 2019 14:50:58 GMT

Probably a bad solder. Try reflow it.

May I suggest you to use a module such as this https://www.crowdsupply.com/i-syst/blyst-nano.

Everything is builtin all you need to do is to connect power and SWD. With this you can even reduce your current PCB size by half.

RE: nRF52832 Custom board designing on single side pcb

Kaja — Fri, 04 Oct 2019 09:43:35 GMT

Schematic and layout would be good

Best regards,
Kaja

RE: nRF52832 Custom board designing on single side pcb

awneil — Fri, 04 Oct 2019 09:30:37 GMT

schematic?

RE: nRF52832 Custom board designing on single side pcb

awneil — Fri, 04 Oct 2019 09:23:29 GMT

[quote userid="76601" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb/213345"]by multimeter ( not sure its a right way to verifying). [/quote]

A multimeter won't show you if you have noise of glitches on your power supply!

As I said earlier, these - and brown-outs - are a high risk on your design.

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Fri, 04 Oct 2019 09:19:33 GMT

Which HW design files do you need? I have pcb layouts and bills of materials file.

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Fri, 04 Oct 2019 09:16:34 GMT

I tried to check the power on my board by multimeter ( not sure its a right way to verifying). and found out that VDD is 2.8V.

Technically, with multimeter I checked the voltage of line which is supposed to connected to VDD of nRF chip. So I think If my soldering is not perfect, it could be the VDD on my nRF chip.

Is there any other method to verify the power?

Thank you.

RE: nRF52832 Custom board designing on single side pcb

Kaja — Fri, 04 Oct 2019 07:41:29 GMT

Hi,

make sure you power the pcb. Let us know if you where able to connect or not.

If you want me to give you a HW review, please upload HW design files, if you want you make the case private or make a new private ticket, or share in this public case.

Best regards,
Kaja

RE: nRF52832 Custom board designing on single side pcb

Nguyen Hoan Hoang — Thu, 03 Oct 2019 14:37:38 GMT

The log shows that the link was not able to talk to your board. There are no responses from your board. Verify that the power VDD on your board is correct first.

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Thu, 03 Oct 2019 14:01:33 GMT

Sorry for my ambiguity.

First, I connect my DK board with my PC. Then physically connect the VDD, VTG, GND, SWDIO, SWDCLK pins in DK board to my custom board. After that, I started programming from command 'nrfjprog' and Arguments '--family nrf52 --eraseall --log'.

I will check the suggestions you tagged. Thanks again.

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 13:55:45 GMT

Segger have some suggestions on resolving connection issues:

https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 13:54:06 GMT

You didn't follow the suggestion on how to post it so it's legible.

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 13:53:55 GMT

Remember that we can't see what you're doing - you have to explain clearly, completely, and in detail!

[quote userid="76601" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb/213218"]The error message shows up when I connect my custom board[/quote]

What, exactly, do you mean by "connect"

physically plug things together ?
try to launch a connection in your IDE ?
other ??

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Thu, 03 Oct 2019 13:43:54 GMT

Sorry, the file is not uploaded as Insert with unknown reason. I copy the all lines in the log.log file.

2019-Oct-03 22:28:39 --------------------------------------------------------------------------------
2019-Oct-03 22:28:39 nrfjprog --family nrf52 --eraseall --log
2019-Oct-03 22:28:39 nrfjprog version 9.8.1
2019-Oct-03 22:28:39 --------------------------------------------------------------------------------
2019-Oct-03 22:28:39 nRF_open_dll
2019-Oct-03 22:28:39 . nRF52_open_dll
2019-Oct-03 22:28:39 . . nRF52_dll_version
2019-Oct-03 22:28:39 nRF_enum_emu_snr
2019-Oct-03 22:28:39 . nRF52_enum_emu_snr
2019-Oct-03 22:28:39 . . nRF52_enum_emu_snr
2019-Oct-03 22:28:39 nRF_enum_emu_snr
2019-Oct-03 22:28:39 . nRF52_enum_emu_snr
2019-Oct-03 22:28:39 . . nRF52_enum_emu_snr
2019-Oct-03 22:28:39 nRF_close_dll
2019-Oct-03 22:28:39 . nRF52_close_dll
2019-Oct-03 22:28:39 . . nRF52_is_connected_to_emu
2019-Oct-03 22:28:47 --------------------------------------------------------------------------------
2019-Oct-03 22:28:47 nrfjprog --family nrf52 --eraseall --log
2019-Oct-03 22:28:47 nrfjprog version 9.8.1
2019-Oct-03 22:28:47 --------------------------------------------------------------------------------
2019-Oct-03 22:28:47 nRF_open_dll
2019-Oct-03 22:28:47 . nRF52_open_dll
2019-Oct-03 22:28:47 . . nRF52_dll_version
2019-Oct-03 22:28:47 nRF_enum_emu_snr
2019-Oct-03 22:28:47 . nRF52_enum_emu_snr
2019-Oct-03 22:28:47 . . nRF52_enum_emu_snr
2019-Oct-03 22:28:47 nRF_enum_emu_snr
2019-Oct-03 22:28:47 . nRF52_enum_emu_snr
2019-Oct-03 22:28:47 . . nRF52_enum_emu_snr
2019-Oct-03 22:28:47 nRF_connect_to_emu_with_snr
2019-Oct-03 22:28:47 . nRF52_connect_to_emu_with_snr
2019-Oct-03 22:28:47 . . nRF52_is_connected_to_emu
2019-Oct-03 22:28:47 . . nRF52_enum_emu_snr
2019-Oct-03 22:28:47 . . nRF52_connect_to_emu_with_snr
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: Hardware: V1.00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: S/N: 682584698
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: TELNET listener socket opened on port 19021
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Starting webserver
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0060ms, 0073ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Webserver running on local port 19080
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0064ms, 0077ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns O.K.
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0066ms, 0079ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_GetHWStatus(...)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0003ms, 0083ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: There is no generic nRF52 device in J-Link, so we select NRF52832_xxAA.

2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("Device = NRF52832_xxAA", ...).
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: XML file found at: C:\Program Files (x86)\SEGGER\JLink_V640\JLinkDevices.xml
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0003ms, 0089ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: C:\Program Files (x86)\SEGGER\JLink_V640\JLinkDevices.xml evaluated successfully.
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0155ms, 0241ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetRestartOnClose = 0", ...).
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0001ms, 0244ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("DisableFlashDL", ...).
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0001ms, 0247ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetDbgPowerDownOnClose = 1", ...).
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0001ms, 0250ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0001ms, 0253ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_TIF_Select(JLINKARM_TIF_SWD)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0002ms, 0256ms total)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: JLINK_SetSpeed(2000)
2019-Oct-03 22:28:47 . . . nRF52_connect_to_emu_without_snr: JLink: (0002ms, 0259ms total)
2019-Oct-03 22:28:48 nRF_read_device_version
2019-Oct-03 22:28:48 . nRF52_read_device_version
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: returns 0x01
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: (0002ms, 0263ms total)
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_device
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_device: JLink: returns FALSE
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_device: JLink: (0002ms, 0266ms total)
2019-Oct-03 22:28:48 . . nRF52_readback_status
2019-Oct-03 22:28:48 . . . nRF52_is_ctrl_ap_available
2019-Oct-03 22:28:48 . . . . nRF52_read_access_port_register
2019-Oct-03 22:28:48 . . . . . nRF52_coresight_configure
2019-Oct-03 22:28:48 . . . . . nRF52_coresight_configure: JLink: JLINK_CORESIGHT_Configure()
2019-Oct-03 22:28:48 . . . . . nRF52_coresight_configure: JLink: returns 0
2019-Oct-03 22:28:48 . . . . . nRF52_coresight_configure: JLink: (0103ms, 0371ms total)
2019-Oct-03 22:28:48 . . . . . nRF52_power_debug_and_system_regions
2019-Oct-03 22:28:48 . . . . . . nRF52_write_debug_port_register
2019-Oct-03 22:28:48 . . . . . . nRF52_write_debug_port_register: JLink: JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
2019-Oct-03 22:28:48 . . . . . . nRF52_write_debug_port_register: JLink: returns -1
2019-Oct-03 22:28:48 . . . . . . nRF52_write_debug_port_register: JLink: (0003ms, 0375ms total)
2019-Oct-03 22:28:48 . . . . . . nRF52_write_debug_port_register: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

2019-Oct-03 22:28:48 . . . . . nRF52_power_debug_and_system_regions: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

2019-Oct-03 22:28:48 nRF_close_dll
2019-Oct-03 22:28:48 . nRF52_close_dll
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: returns 0x01
2019-Oct-03 22:28:48 . . nRF52_is_connected_to_emu: JLink: (0002ms, 0378ms total)
2019-Oct-03 22:28:48 . . nRF52_disconnect_from_emu
2019-Oct-03 22:28:48 . . . nRF52_is_connected_to_device
2019-Oct-03 22:28:48 . . . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()
2019-Oct-03 22:28:48 . . . nRF52_is_connected_to_device: JLink: returns FALSE
2019-Oct-03 22:28:48 . . . nRF52_is_connected_to_device: JLink: (0002ms, 0381ms total)
2019-Oct-03 22:28:48 . . . nRF52_unpower_debug_and_system_regions
2019-Oct-03 22:28:48 . . nRF52_disconnect_from_emu: JLink: JLINK_Close()

RE: nRF52832 Custom board designing on single side pcb

KYUBEEN — Thu, 03 Oct 2019 13:42:21 GMT

The error message shows up when I connect my custom board to my DK board with this configuration.

DK board Custom board

VDD, VTG --------------------------------> VDD

GND -----------------------------------------> GND

SWDIO --------------------------------------> SWDIO

SWDCLK ------------------------------------> SWDCLK

As followed the recommendations in error message, I got log file(inserted on this reply) but still have no idea what brings this problem.

Also, trying to find out how to using Segger tools and scope my power supply to check drooping.

Thank you for your kind replys 'awneil' and 'Nguyen Hoan Hoang'

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 13:22:33 GMT

[quote userid="76601" url="~/f/nordic-q-a/52858/nrf52832-custom-board-designing-on-single-side-pcb"]Any recommends[/quote]

The message you posted gives you two recommendations on things to do - have you done those?

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 13:20:22 GMT

KYUBEEN - It's not clear if the J-Link never connects, or if it's connecting but losing the connection - please clarify!

As Nguyen Hoan Hoang says, if it's never connecting, that'll be a fault in your board (design and/or construction).

The J-Link tools will tell you what supply voltage is being detected on the target - is it correct?

RE: nRF52832 Custom board designing on single side pcb

Nguyen Hoan Hoang — Thu, 03 Oct 2019 13:14:18 GMT

Looks like the jlink could not connect to your board. Check the power and the SWD pins. Could be soldering issue.

RE: nRF52832 Custom board designing on single side pcb

awneil — Thu, 03 Oct 2019 12:43:57 GMT

It's better to copy & paste those messages as text (as for source code, but omit step 3) - not as a picture!

When, exactly, do you get those messages?

Have you tried just using the Segger tools - to rule Keil out of the equation ?

Have you put a scope on your power supply at the nRF pins - it could be that the power supply is "drooping" due to the peak current demand of the radio.

ie, you're getting a brown-out.

This is especially likely on a single-sided board - with no ground or power planes. Your traces are all very thin!