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

Wrong message from Segger 5.50a Compiler (nRF Connect SDK v1.6.0-rc2)

Hello,

The errors and warnings are displayed in incomprensive form, what i have to set to read correnctly, whit row number and clairy text.

Thanks

Parents
  • Hello,

    The Toolchain Manager's NCS SDK v1.6.0-rc2 release candidate is currently unavailable due to an issue with SES. We are working on having this fixed and making it available again.
    Sorry for the inconvenience.

    Best regards,
    Karl

  • Hello,

    NCS SDK V1.6.0-rc2 was installed by nRF Connect desktop version.

    So to develop the work I have in progress, which version should I use so as not to lose the work already done?

    Thanks

    Fausto

  • Hello Fausto,

    I see now that I should have been more explicit in my previous answer, my apologies.

    Fb62 said:
    So to develop the work I have in progress, which version should I use so as not to lose the work already done?

    You may still move onto the newest NCS SDK release, which is v1.6.0, regardless of the Toolchain Manager - however you can therefore unfortunately not use the Toolchain Manager to set up the new NCS SDK release for the time being.
    I would think that the issue with SES might be present with the NCS SDK v1.6.0, so you might still have to update your NCS SDK with the SES fix when that becomes available.
    This should have no impact on your development, other that the current aforementioned SES issue.

    For the record, I edited my previous comment to explicitly mention that I was talking about the Toolchain Manager's NCS SDK v1.6.0-rc2 release candidate, not the NCS SDK's v1.6.0.

    Sorry for any confusion this might have caused.

    Best regards,
    Karl

Reply
  • Hello Fausto,

    I see now that I should have been more explicit in my previous answer, my apologies.

    Fb62 said:
    So to develop the work I have in progress, which version should I use so as not to lose the work already done?

    You may still move onto the newest NCS SDK release, which is v1.6.0, regardless of the Toolchain Manager - however you can therefore unfortunately not use the Toolchain Manager to set up the new NCS SDK release for the time being.
    I would think that the issue with SES might be present with the NCS SDK v1.6.0, so you might still have to update your NCS SDK with the SES fix when that becomes available.
    This should have no impact on your development, other that the current aforementioned SES issue.

    For the record, I edited my previous comment to explicitly mention that I was talking about the Toolchain Manager's NCS SDK v1.6.0-rc2 release candidate, not the NCS SDK's v1.6.0.

    Sorry for any confusion this might have caused.

    Best regards,
    Karl

Children
No Data
Related