• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 1407 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CODECOMPOSER: CCS10.10 and TI ARM 18.1.1.LTS and macOS Catalina, does not detect the compiler after copy

AllanD
Expert 1085 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CC1312R, TIDA-010024

Tool/software: Code Composer Studio

I just upgraded to macOS Catalina 10.15.6 due to requirements of Xcode to continue iPhone application development (yes, Apple developers get pushed update software frequently) and have been rebuilding the CC1312R development environment.

I am running into several issues with several TI installers from a year or two ago not working in Catalina, I think due to the removal of 32-bit support.

I have been able to resolve most issues by running the previous macOS Mojave 10.15.6 in a Parallels Desktop VM, do the installation, then copy the files over and install through the CCS menus.

However, ARM 18.1.1.LTS does not want to co-operate with this method, it is not being detected when I try to install it through the preferences, I will attach a screen shot of what I see.

I am after this old compiler for the reason that it was used during development of the TIDA-010024 reference project.

I don't mind moving to a different compiler toolchain but I have an unresolved build error that I think is related to changes in the newer toolchain TI 20.2.1.LTS that was auto selected.

If I could get some confirmation about what the best course of action would be, or if I am safe to move to the latest v18 of the compiler it would be helpful and appreciated.

The installer that I am using https://www.ti.com/tool/download/ARM-CGT-17/18.1.1.LTS

  • 0
    Expert 1085 points

    I attempted a new method to install through the updater, but it fails after CCS restart, attaching screen shots.

  • 0 in reply to AllanD
    TI__Guru**** 162825 points

    Allan,

    I believe the 18.1 compiler is an 32bit executable and not just the installer is 32bit.

    For me I can't select it in CCS.  I have it from when my machine was Mojave but now I can't use it.

    Using 18.12 would likely be the easiest thing to do.  We might be able to help with the error that you are getting with 20.2 if you want to use the latest tools.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1085 points

    Hi John,

    Thank you for your prompt reply and the confirmation with the 32-bit assumption.  While the number of developers on MacOS are a lot fewer than Windows, I am glad to know there are some at TI using the MacOS platform.

    From what I read 32-bit support has been completely removed out of macOS Catalina, I don't know if there is anyway to execute any 32-bit code apart from running a VM to do so.  I am not sure if it is just disabled or if the support has been completely removed.

    This is more of a coding question, but I will post it and maybe this is a known issue when upgrading from 18 to 20.

    I am still using SimpleLink 2.40.0.81 for the CC1312R (Rev E silicon) as it is not trivial (for me anyway) to move to the latest SimpeLink.

    I would like to move to SimpleLink 4.20, but, it still uses ICall among other changed things.  I am not sure of your experience with SimpleLink since this was initially posted as a compiler tools issue.

    This is the sample source from TIDA-010024 reference project that I am compiling, that should allow you to find it if you would like to try to compile it yourself.

    I could upload the project, but it is the same as you would download from TIDA-010024.

  • 0 in reply to JohnS
    Expert 1085 points

    Hi John,

    I made the following change, I think it will be okay, please confirm.  It does compile correctly with 20.2.1.LTS.

    Please reference the original source in the images above.

    Changed the following line from

    return ( (unsigned char*)ltoa( l, (char *)buf ) );

    to

    return ( (unsigned char*)ltoa( l, (char *)buf, (int)radix ) );

    I feel very nervous making changes to the stack as it may introduce unforeseen bugs later down the road.

  • 0 in reply to AllanD
    Expert 1085 points

    Hi John,

    I did install 18.12.6.LTS and it works correctly without the above change necessary.

    This is closer to the original compiler tools used with SimpleLink 2.40.0.81 and feel more confident as such.

    If you do believe I should use the later compiler please advise and I will make the change to the stack as referenced above.

    With your previous experience do you recommend to move to the 20 version with this project?

    It would be really nice if TIDA-010024 was ported to SimpleLink 4.20.xx but seems unlikely soon as it works fine with 2.40.0.81.

    It is not a trivial port, I have tried and it gets messy quickly with the changes (deprecation) to ICall and other things.

  • 0 in reply to AllanD
    TI__Guru**** 162825 points

    Ok I was wondering if that was the issue you were hitting with 20.2.  There was a runtime library change in it that results in the issue you are seeing.  Honestly it is probably best to go with the 18.12 compiler as it still actively supported (with maintenance releases) and is closer to what that SDK was released with.

    Sorry I don't know of any plans to update TIDA-010024.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1085 points

    Hi John,

    Thank you for the reply and confirmation.  I am sure I was not the first to run into that issue, the function prototype was changed.

    I think the restriction on 32-bit with macOS Catalina may cause trouble for a lot of hardware developers, I just ran into my first case of this.

    I will follow your suggestion on staying with 18.12 since I don't know what other bugs will be introduced into the stack components.

    I will go ahead and mark this resolved, thank you for the quick response and suggestions!