This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf5340 Zephyr Project Development Windows

I am working on porting a project from the old sdk to the nrf5340 and the nrf connect sdk documentation seems to be incorrect and i am having major issues even getting this thing stood up.   I am working on windows 10 using the latest version of nrf desktop and nrf connect tool chain manager.  While i have managed to move the peripheral hr monitor project to my own workspace the development documents seem to be wrong.  In trying to separate the project into different source files there is no entry to add new file to cMakeFileLists and when i manually add it to the file there is no obvious way to reimport it.  The only way for the new files to share the project dependencies is to re open the project with the File->Open nRF Connect SDK Project.  This is really frustrating since any time i want to add a new file i have to re open the entire project and then redo the entire file structure otherwise all i get is one large blob of files.  I need to know if this is an install issue or if this is actually how this is currently working as this is adding a lot of time and frustration trying to figure out even how to set up the basic project let alone start working with the rtos.  This is a real roadblock and any help would be appreciated.

Thanks,

Parents
  • Sorry for the late reply,

    I've notified project lead, but I'm afraid there's not much we can do about it in the short term. If this is a blocking issue I suggest you look into using an editor like VS code and building the project with West. You'd still need to add source files to the CMakeLists manually, but you won't have to go through the grueling process of remaking the file structure in SES. 

    BR,
    Håkon Holdhus

Reply
  • Sorry for the late reply,

    I've notified project lead, but I'm afraid there's not much we can do about it in the short term. If this is a blocking issue I suggest you look into using an editor like VS code and building the project with West. You'd still need to add source files to the CMakeLists manually, but you won't have to go through the grueling process of remaking the file structure in SES. 

    BR,
    Håkon Holdhus

Children
  • I don't understand why you would present your product to support IDE based development if this is not a feature.  Going the route you suggest is like linux kernel development and is much harder to debug and properly develop low power product.  How was the online guide developed if these features do not actually exist?  I have high speed capture compare and other features that i need to port and debug and this is going to make it far more difficult than it should be.  Is there a timeline for when this will be working?

Related