• State Not Answered
  • Replies 9 replies
  • Subscribers 68 subscribers
  • Views 1096 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 299992
Options

Getting blinky to build with SES

Bret Foreman

I'm trying to get blinky to build using SES. It would be great if I could start with an example that builds and work from there, but apparently you guys don't have such a thing. So I copied the blinky project to a new folder and tried a build. Just as with the original blinky, I get an error concerning the .text and .rodata tags in the flash_placement.xml file:

So I remove those lines from the flash_placement and try to build again. It fails with a whole new set of errors:

  • 0

    Hi Bret,

    Thank you for contacting DevZone at NordicSemi.

    Sorry to hear that you are struggling to build a basic example.

    Nordic provides a whole set of examples for different use-cases. This snapshot just shows some of the examples that are peripheral examples in the SDK example folder.

    Next, I am opening blinky project for pca10040 board.

    And simply by pressing f7 (build) you can see the successful compilation. Here I am also showing the version of SES I am using.

    It is also worth noting that nRF5 SDK v17 have used SES 5.42a for test and verification.

    Moreover, Nordic's current SDK is "NRF Connect SDK" also called nCS, and the latest version is 2.2.0. It is very easy to getting started with nCS using VS Code and that is the recommended way by Nordic.

    With Regards,

    Naeem

  • 0 in reply to Naeem Maroof

    Naeem,

    I see that you are using a "down rev" version of SES. In fact, it's a really old version. I'm using the latest version 7.10. I can see many exchanges in the devzone forums about how later versions of SES don't work with the latest DKs. In those cases, the developers had to modify the projects to get them to work.

    So here's my question: Is it better to go backward in SES revisions until I find one that works with blinky or to modify blinky to work with the latest version of SES?

    I've already established in a different devzone support thread that VS Code does not support DK PCA10040 version 3.0.0. So it has to be SES.

    Regards,

    Bret

  • 0 in reply to Naeem Maroof

    I should mention, also, that the GUI programmer doesn't work with this DK either. It appears to load the hex file, but the board won't advertise. I can load the same hex file with the command line loader and everything works. I suspect the bug that causes the GUI loader to fail is also baked into VS Code and that's why it won't work. But I have no evidence either way.

  • 0 in reply to Bret Foreman

    Hi Bret,

    I am not an expert user of SES, and I was also having such questions. Nonetheless, what I hear from experts is that it is better to use a downgraded version. Otherwise, it could be a lot of extra work, and as the newer versions of SES were not used for testing and verification, in case of any further problem our response would be pretty much same: Use a downgraded version.

    With regards,

    Naeem

  • 0 in reply to Naeem Maroof

    Naeem,

    So I went to the Segger download site and selected version 5.42a like so:

    Note that there are two similar links. It turns out they both download slightly different versions of SES 7.10.

    In both links, the file that was downloaded was the version 7.10 installer, not the 5.42a installer. Either Segger has an error on their download site or the old 5.42a version is no longer available.

    Where did you get SES version 5.42a? Do you have an installer for it?

    Note that this DK does not work with VS Code so I must get SES to work. Can you get an expert involved so we can solve this?

Related