Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

Kenneth — Wed, 13 Dec 2023 10:40:36 GMT

Hello,

Actually zephyr doesn't cause much overhead, you can find some numbers here:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/zephyr/samples/basic/minimal/README.html

You can find some bare metal examples here:
https://github.com/zephyrproject-rtos/hal_nordic/tree/master/nrfx/samples/src

Kenneth

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

trackerfx — Tue, 12 Dec 2023 23:46:48 GMT

Well, this is embarrassing. You are correct, I am using the older SDK. However, I did get it to work.

Unfortunately, I don't think the SDK Connect will be a good match for me. I'm a bare-metal programmer and don't care for the added abstraction of an RTOS. To be honest, I'm not even sure what benefit could possibly come from using one. Don't they use up precious resources? What are the cost-benefits of Zepher?

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

Kenneth — Sun, 05 Nov 2023 21:24:48 GMT

Hello,

Can you show me what your SDK folder look like, which of these is it?

Kenneth

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

trackerfx — Sat, 04 Nov 2023 20:08:54 GMT

NRF_LOG_INFO is a library function used in the tutorial I referenced in the original post and has nothing to do with the SDK I'm using. Also, 'MBR', 'softdevice', and 'application area' are all terms used on your programming software and haven't changed (that I'm aware of) ever. Honestly, I'm beginning to wonder if you know what you're talking about. Since you don't seem believe me, here's another screenshot.

Now, since this has gone largely ignored for over a week, would you mind pushing this to someone who will give it some attention? I really need answers.

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

Kenneth — Thu, 02 Nov 2023 12:56:10 GMT

But if you have your own board with UART interface that you want to display on a terminal window in Windows I suggest you for instance try to get something similar to:
https://ftdichip.com/products/ttl-232r-3v3/

Kenneth

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

Kenneth — Thu, 02 Nov 2023 12:52:53 GMT

[quote user="trackerfx"]I'm still waiting for support. Is anyone still following this ticket?[/quote]

Yes and no, looking at the last replies you made I still get the sense that you are actually working on the nRF5 SDK, and not the nRF Connect SDK. At least the descriptions "NRF_LOG_INFO", "MBR", "softdevice and application area" all seem to point to nRF5 SDK. So based on that my initial reponse still seem to be valid?

Kenneth

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

trackerfx — Wed, 01 Nov 2023 23:11:16 GMT

I'm still waiting for support. Is anyone still following this ticket?

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

trackerfx — Mon, 30 Oct 2023 00:15:03 GMT

I did a bit more testing and discovered that the nRF52840-DK board is responsible for the 'z' output to the terminal. With or without my board connected, it does this anytime the default BLE app code is present on it. (Turn on the BLE app with the DK board erased and it automatically programs this code.) With the DK board erased, the terminal no longer outputs anything, even with my board connected. Should the NRF_LOG_INFO function work with my board connected through the DK board or do I need a direct connection to my PC?

Something else I noticed, and this may be totally unrelated, was that reading back the program on the DK board showed the MBR, softdevice, and application areas, but when I do the same on my board it only shows the MBR and softdevice. (See below.) The thing is, I can see my device advertising, and the device name, etc. is correct. Wouldn't that imply that the application is present?

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

trackerfx — Sun, 29 Oct 2023 03:39:28 GMT

Yes, I have the nRF Connect SDK and I did finally figure out that he's using 2 boards in the tutorial. I got the sample code that he used to work with the nRF Connect BLE Application; I can connect and view the GAP and GATT data but when I connect with puTTY it just repeatedly prints the letter z to the screen. I assume that means that something is asleep but I've never seen that behavior and it's certainly not something I put in my code. Is this something you're familiar with? I was hoping to use the data printed to puTTY for troubleshooting. I should be getting a message when connecting and disconnecting but nothing is going to the monitor except a constant string of z's. While this is happening, powering off my custom board has no effect on the puTTY terminal.

RE: Follow-up to 2 J-Link devices reported when connecting nRF52840-DK.

Kenneth — Mon, 23 Oct 2023 11:23:41 GMT

Hello,

We don't provide technical support for new development on the nRF5 SDK (unless you are already familiar with the nRF5 SDK platform). For new development you should be using the nRF Connect SDK. Reasons why to switch to the nRF Connect SDK:
https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement

To get familiar with the nRF Connect SDK: https://academy.nordicsemi.com/

Looking quickly at the video tutorial you are looking at, be aware that he has at least two nRF52xxx DK's connected. One that he is developing on (COM9 in his case), and a second (COM7 in his case) that is used by the nRF Connect BLE app.

Kenneth