Which dev environment for my nRF52 DK?

[Bret Foreman]

Guys,

I'm stuck.

As we determined in ticket ID 300239, the nRF Connect SDK does not support my version 3.0.0 of the PCA10040 DK.

And as we determined in ticket ID 300238, Nordic is not supporting the sdk_config.h files for SES 5.42a. Specifically, there is no information for how to combine the configs for the different subsystems of the chip.

Assuming I'm starting from scratch, what should be my DK and SDK choices so I can get unblocked?

Regards,

Bret

[Amanda Hsieh]

Hi, 

As we determined in ticket ID 300239, the nRF Connect SDK does not support my version 3.0.0 of the PCA10040 DK.

Sorry to make you misunderstand. nRF52DK v3.0.0 can be supported both by NCS and nRF5 SDK. For NCS, you could use VS Code. For nRF5SDK, you could use the following tools:

 - ARM: MDK-ARM version 5.25   
 - GCC: GCC ARM Embedded 9.2020-q2.major
 - IAR: IAR Workbench 7.80.4
 - SES: SES 5.42a

Regards,
Amanda H

[Bret Foreman]

Did you read in ticket 300238 how the sdk_config.h file for SES 5.42a is not supported? How can you be recommending that tool?

[Amanda Hsieh]

Hi, 

Check out the UART module documentation and follow my colleague's suggestion in your case 300238. Please continue the discussion in that case. 

-Amanda H.

[Bret Foreman]

It sounds good in theory, but the NCS install is failing, as I described in ticket ID 300239.

[Bret Foreman]

We're going around in circles here. You keep telling me to use NCS, I tell you the NCS install is failing. Then you tell me to use SES, but the sdk_config.h files are unsupported. I ask for support on the sdk_config.h file and you tell me to use NCS.

[Amanda Hsieh]

Sorry to hear that feeling. I am trying to help you clarify the solution.  

Bret Foreman said:

I tell you the NCS install is failing

When you install NCS, you should open the example under ncs\v2.2.0-rc1 instead of SDK_17.1.0. Besides that, I don't think the NCS installation failed. At least, I don't see an error in the figures.  Not sure what is your application, but here are some NCS examples related to UART like 

• Low Power UART
• Peripheral UART

Bret Foreman said:

Then you tell me to use SES, but the sdk_config.h files are unsupported.

It's not unsupported. You would need to compare the sdk_config.h with a project that is using app_uart and copy and paste all configurations that may be missing as my colleague pointed out. 

-Amanda H.

[Bret Foreman]

There was no error in the NCS install. But when I open VS Code, it says that NCS is not installed. When I go to the Tool Chain Manager, it says it is.

If you want to support sdk_config.h, please point me to the documents that describe how to enable the UART. I looked at the sdk_config.h file for the uart example and nothing there matches the generic sdk_config.h file I'm using in my project. I posted screen shots in ticket ID 300238 and did not get any replay on how to resolve the conflict between the files.

I feel like I'm just repeating the same info again and again and you're not reading it.

[Amanda Hsieh]

Bret Foreman said:

when I open VS Code, it says that NCS is not installed.

Could you provide a snapshot of that?

See UART driver configuration. You could refer to sdk_config.h of the UART Example or use the example as the base.

Bret Foreman said:

I can tell from those that the Tool Chain Manager is simply broken and didn't install any of it.

Could you provide the log file?

What folders do you have under C:\ncs\v2.2.0-rc1?

-Amanda H.

[Bret Foreman]

Regarding the uart, how many times do I have to repeat that the sdk_config.h file in the uart example project is in conflict with the standard sdk_config.h file for starting a project? I sent you screen shots showing why. What more can I do to make it clear? How about if I attach both files so you can compare for yourself?

0827.sdk_config.hThis is the uart example

0827.sdk_config.hThis is my working project

Please tell me how to merge these so that my project has the UART enabled.

Here's the ncs folder and a screen shot of VS Code asking me to install it again: