nRF52 SDK 0.9.2 temperature example uart problem

RE: nRF52 SDK 0.9.2 temperature example uart problem

Martin — Sat, 23 Apr 2016 16:33:30 GMT

Ok solved the Problem: Install the latest SEGGER J Link Drivers (V5.12c). Seems like there was an update regarding the USB UART driver.

RE: nRF52 SDK 0.9.2 temperature example uart problem

Martin — Sat, 23 Apr 2016 16:11:59 GMT

I have the same Problem. I also tried the UART example and added some debug LED states. It shows me that serial data is transmitted from the pc in the right way. However I cannot receive any serial data on the PC side. It does't work with any terminal client (Putty TeraTerm etc.) and also not on other systems (linux)...

Please help!

RE: nRF52 SDK 0.9.2 temperature example uart problem

Vidar Berg — Tue, 09 Feb 2016 13:51:12 GMT

I've not used the br@y terminal before, but it work fine when I tried it now. However, a colleague of mine have that have had varying success with it, he has experienced that it worked fine on some setups while failing on others. Not sure why that is, but could you please try with Putty or Tera Term to narrow down the problem?

RE: nRF52 SDK 0.9.2 temperature example uart problem

HSPalm — Tue, 09 Feb 2016 12:50:17 GMT

Did what you said now, used your .hex file. Unfortunately no difference.

I used nRFgo Studio:

Pressed "Erase all"
Loaded your .hex and programmed it via "Program Application" tab.

Reset the board and connected to computer via USB again.

Then used Terminal (by br@y) to monitor the serial port:

Settings: 38400,8,N,1, tried both with and without handshaking
No incoming data

Please see attached photos "attached": goo.gl/.../EeBRwh5CWfTAeQUT9

RE: nRF52 SDK 0.9.2 temperature example uart problem

Vidar Berg — Tue, 09 Feb 2016 10:18:28 GMT

Please try to following to ensure we are doing the same:

Do a complete flash erase
Program the attached temperature example
Do a system reset
Connect with a serial terminal (Tera Term,..) and set the baudrate to 38400

RE: nRF52 SDK 0.9.2 temperature example uart problem

HSPalm — Mon, 08 Feb 2016 15:58:32 GMT

Thanks for answering. Yes, I use the default method of bridging via the Segger chip. All though I am not so sure this is where the problem lies, cause I never see any activity on the UART pins and the buffer is never emptied.

I did update the J-link driver.

RE: nRF52 SDK 0.9.2 temperature example uart problem

Vidar Berg — Mon, 08 Feb 2016 14:44:49 GMT

Hi, are you using the on-board Segger chip for as UART <-> USB bridge (default)? I did work without any changes when I tried it here.

One thing to try is to update to the latest Segger driver if you haven't already -> download link and see if it makes any difference. It should enumerate as "Jlink CDC UART PORT (com xx) in device manager once the CDC driver is installed.

Attachement:

52_temp_example.hex