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

Segger Studio version 5.42b and SDK 12.3

Hi, i have problem to import and configure the example with this sdk. I used the tutorial  ( https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/segger-embedded-studio-a-cross-platform-ide ), but dont work. How can i make the import? Thanks.

Parents Reply Children
  • matiasrode said:
    Thanks for the help.

     No problem at all, I am happy to help! 

    matiasrode said:
    First, the command "Import Section placement" don't appear.

    Please make sure to right click on the Project, not the solution. The Import section placement option should be at the bottom of the list of options that pops up when you do so.
    I just tried this in SES v.4.50 and I see it exactly as it looks in the tutorial.

    matiasrode said:
    When i build, a lot of errors show after i make all the configurations of the link i send here. The image show the errors

    The errors looks to be related to the unimported flash_placement.xml file. Please try again to import the Section placement like mentioned in the tutorial, and let me know if the same errors appears after the section placements is successfully imported.

    Best regards,
    Karl

  • Hello Karl. Ifollow the link that you send to me and where i change the linker to GNU, the command "Import section placement' don't appear. I save the flash_placement.xml in the directory of the example

    "C:\Users\andre\Downloads\nRF5_SDK_12.3.0_d7731ad\nRF5_SDK_12.3.0_d7731ad\examples\ble_peripheral\ble_app_template - Copia\pca10028\s130\arm5_no_packs"

    The images are here:

    GNU selection

    Import section don't appear

    Flash placemente local:

  • Hello again,

    I see the same behavior when I go through the tutorial using SES v5.50.
    I will confer with some colleagues about this on money, and see if any of them have heard of similar behavior in the past.

    In the meantime, could you try to include the file directly in the project options, by opening the project file in an editor and inserting linker_section_placement_file="flash_placement.xml" into the nRF51 build configuration?
    You can open the project in an editor by clicking on the Project -> Open in Editor or by opening the project file in an editor directly.

    I will get back to you when I have discussed this with some colleagues.

    Have a great weekend! :) 

    Best regards,
    Karl

  • Hello Karl, thanks for the great help again. 

    I make the change that you said to me. Now, the problem is that in the image:

    cc1: fatal error: cannot open 'C:/Users/andre/Downloads/nRF5_SDK_12.3.0_d7731ad_ses.support-master/nRF5_SDK_12.3.0_d7731ad_ses.support-master/examples_segger/ble_peripheral/ble_app_template/pca10028/s130/ses/Output/nrf51422_xxac/Obj/ble_app_template_pca10028_s130/hardfault_implementation.asm' for writing: No such file or directory

    The others errors dont show. 

    Again, thanks for the help.

    André.

  • Hello,

    matiasrode said:
    thanks for the great help again. 

    No problem at all André, I am happy to help! Slight smile

    matiasrode said:
    Now, the problem is that in the image:

    I notice in the hardfault_implementations.c in the project explorer that it seems to not be compiled, and it has the tag "modified options" - is this file excluded from the build, or did you make any changes in its options (apart from the system file addition as written in the guide)?

    matiasrode said:
    cc1: fatal error: cannot open 'C:/Users/andre/Downloads/nRF5_SDK_12.3.0_d7731ad_ses.support-master/nRF5_SDK_12.3.0_d7731ad_ses.support-master/examples_segger/ble_peripheral/ble_app_template/pca10028/s130/ses/Output/nrf51422_xxac/Obj/ble_app_template_pca10028_s130/hardfault_implementation.asm' for writing: No such file or directory

    This might be the result of the path length limit in Windows. Windows limits all paths to 260 characters, and I see that this path here now is a total of 262 - this might be why the compiler is unable to find the file.
    Could you move the SDK to the top directory of your C: drive, and see if this resolves the error?

    Best regards,
    Karl

Related