Direct test mode change pin assign

RE: Direct test mode change pin assign

kevin seo — Mon, 11 Nov 2019 10:56:09 GMT

I'm solved this problem!

I made mistake.

Thank you.

RE: Direct test mode change pin assign

haakonsh — Fri, 08 Nov 2019 09:51:56 GMT

"However, it does not work in direct test mode."
What are the symptoms?

RE: Direct test mode change pin assign

kevin seo — Thu, 07 Nov 2019 13:44:08 GMT

In the radio test example, uart works well with pins 2 and 29. However, it does not work in direct test mode.

RE: Direct test mode change pin assign

kevin seo — Thu, 07 Nov 2019 13:41:47 GMT

I have 3 nrf52840DK boards. but everything didn't work...

RE: Direct test mode change pin assign

haakonsh — Thu, 07 Nov 2019 09:19:51 GMT

I do not know myself, it might be ESD damage to those pins. You can check for ESD damage by toggling the pin and monitor it with an oscilloscope. A pin with blown ESD fuses will behave very strange.

It could also be that those pins are a bit too capacitively loaded, if that's the case you need to set the GPIO drive strength to high for those pins. See nrf_gpio_cfg and nrf_gpio_pin_drive_t. The high drive strength option is called NRF_GPIO_PIN_H0H1.

RE: Direct test mode change pin assign

kevin seo — Wed, 06 Nov 2019 23:33:13 GMT

baud rate is 19200.

I don't know why didn't work p0.02, p0.29....

RE: Direct test mode change pin assign

haakonsh — Wed, 06 Nov 2019 09:34:20 GMT

The low-frequency label applies to RF compliance as any high-frequency stuff on these pins will disrupt the radio. High frequency is >10kHz in this regard

I do not know why the p0.02 and p0.29 pins do not work properly with UART on the DK.
What baud rate are you using?

RE: Direct test mode change pin assign

kevin seo — Tue, 05 Nov 2019 23:45:45 GMT

In the data sheet, pins 2 and 29 are labeled low frequency i / o. Is this related to this? If use a pin other than the low frequency pin, it works fine. If yes, can you tell me where the document says it should not be?

RE: Direct test mode change pin assign

kevin seo — Tue, 05 Nov 2019 23:23:40 GMT

Uart baudrate is 19200.

When uart 6, 8 pins worked fine, but if change to pins 2,29, it does not work.

Hang at NRF_BREAKPOINT_COND, a breakpoint in the app_error_fault_handler function.

RE: Direct test mode change pin assign

haakonsh — Tue, 05 Nov 2019 14:43:27 GMT

Have you scoped the UART lines?

RE: Direct test mode change pin assign

kevin seo — Tue, 05 Nov 2019 12:49:33 GMT

no. I'm use only j link debug.

RE: Direct test mode change pin assign

haakonsh — Tue, 05 Nov 2019 10:09:25 GMT

Are you using logging?

RE: Direct test mode change pin assign

kevin seo — Tue, 05 Nov 2019 09:36:26 GMT

I want to use pins 2,29 instead of pins 6 and 8.

I changed the cts and rts but it didn't work

RE: Direct test mode change pin assign

haakonsh — Tue, 05 Nov 2019 09:10:55 GMT

From Connector interface:
P0.05, P0.06, P0.07, and P0.08 are used by the UART connected to the interface MCU. For more information, see section Virtual COM port.

Try changing CTS and RTS as well. If that does not work then you probably need to turn off any logging.