Getting blinky to build with SES

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:

Parents
  • 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

  • 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

  • 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?

  • I just sent a support ticket to Segger about their website, hoping to find the 5.42a installer. But, just in case 5.42a is no longer available, does your team have an installer for that version?

  • Hi Bret,

    Bret Foreman said:
    Note that there are two similar links.

    I am not sure about that problem of accessing website, but what I can see is a single installer in two flavors (for 64b and 32b versions of windows).

    Bret Foreman said:
    It turns out they both download slightly different versions of SES 7.10.

    The size of 5.42b installer is around 555 KB, and the size of 7.10 installer is around 254 KB. 

    Bret Foreman said:
    Where did you get SES version 5.42a? Do you have an installer for it?

    We get from installers from Segger website, and for sure you must also do that. In case of any problem, you may contact Segger.

    Regards,

    Naeem

  • I got a reply from Segger and they sent me a link to download SES version 5.42a directly. Here's a screenshot of my about screen:

    I tried to build blinky with this version of SES and got the following error:

    Can you tell me how to clear this error?

  • It looks like the linker is trying to link in the thumb_crt0.o object from a previous build with SES 7. A full rebuild should do the trick in that case. If not, you can delete the 'Output' folder in your project directory before you try again.

    It appears to load the hex file, but the board won't advertise.

    The CPU is halted after programming and needs a reset to start execution again. Could this have been the problem? 

    The Programmer app has an "auto reset" option which you can enable to have it automatically reset the target after programming.

Reply
  • It looks like the linker is trying to link in the thumb_crt0.o object from a previous build with SES 7. A full rebuild should do the trick in that case. If not, you can delete the 'Output' folder in your project directory before you try again.

    It appears to load the hex file, but the board won't advertise.

    The CPU is halted after programming and needs a reset to start execution again. Could this have been the problem? 

    The Programmer app has an "auto reset" option which you can enable to have it automatically reset the target after programming.

Children
No Data
Related