• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 700 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.

CODECOMPOSER: CCS3.x to CCS12 migration - BIOS issue

Adrien Thurin
Intellectual 496 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSBIOS, UNIFLASH, SYSCONFIG

Hi,

As a follow-up to this question, I have issues with the linking of the project.

>> Compilation failure
makefile:202: recipe for target 'Monodouble.out' failed
4F0}: cannot stat 'C:\Users\A0564~1.THU\AppData\Local\Temp\76A143F2-0B79-4E2C-AEF7-20D4C9A494F0': No such file or directory
error #10008-D: cannot find file "biosi.a28l"
gmake[1]: *** [Monodouble.out] Error 1
gmake: *** [all] Error 2
makefile:198: recipe for target 'all' failed

It seems that there is a file that should be generated in a temporary folder, and isn't. Or at least, that's my understanding of the issue.

The project is configured with DSP/BIOS 5.42.2.10.

Thanks in advance, 

Best regards,

Adrien

  • 0
    TI__Guru* 83935 points

    Hello Adrien

    What device are you developing for?

    Unfortunately we no longer support SYSBIOS/ DSP BIOS etc and there are no expertise in the team to field this query. We had asked internally but did not find any good guidance.

    The only collateral/content i can point you to is the following appnote

    https://www.ti.com/lit/an/spracr4a/spracr4a.pdf

    This is also a bit dated, but may have other tips and tricks

  • 0 in reply to Mukul Bhatnagar
    Intellectual 496 points

    Hello,

    I am using an F2810.

    My client is using this old (and expensive) part, and is afraid that their las computer with CCS3.3 might "give up", and they might not be able to manufacture their products. Migrating the toolchain to CCS12.5 was a first step in assuring manufacturability of their product. A second step would be to migrate the code to a new target, better and cheaper.

    The only thing I could do is try to migrate DSP/BIOS to SYS/BIOS and see what happens, but I am not sure I want to go down this rabbit trail.

    I will also check if Uniflash can solve the "programming in case of old computer failure" issue, even though it might not be fully satisfactory for the client...

  • 0 in reply to Adrien Thurin
    TI__Guru* 83935 points

    Hello Adrien

    I am going to redirect this post to our sister product line applications who manages F2810 support, will see if they have additional guidance on this.

    Regards

    Mukul 

  • 0 in reply to Mukul Bhatnagar
    Intellectual 496 points

    Hello Mukul,

    Thanks. Let me know if there are some updates from them.

    Best regards,

    Adrien

  • 0 in reply to Adrien Thurin
    TI__Guru 53765 points

    Hi Adrien,

    Unfortunately, I can't offer much insight into how the DSP/BIOS build works and what may be causing this error either. I'm a bit more familiar with SYS/BIOS, but like Mukul said, we really aren't supporting either version of BIOS anymore. We're primarily recommending folks using BIOS to migrate to FreeRTOS (there's a C28x port of it in C2000Ware) if they can.

    Whitney

  • 0 in reply to Whitney Dewey
    Intellectual 496 points

    Hi Whitney,

    Thanks for your feedback.

    As I explained to Mukul, migration to FreeRTOS will probably be a second stage project, along with target migration. It doesn't make much sense, to migrate to FreeRTOS on an old part that doesn't support sysconfig at this stage. 

    Thanks a lot for your help. 

  • 0 in reply to Adrien Thurin
    TI__Guru 53765 points

    According to the DSP/BIOS release notes, the last version of CCS it was tested with was v5. I'm not sure at what point BIOS support broke. It might be possible to find an older combination of CCS and compiler tools versions that are old enough to be compatible with BIOS, but new enough to work on a modern Windows 10 machine (or whatever OS you're working with)?

    Whitney

  • 0 in reply to Whitney Dewey
    Intellectual 496 points

    Thanks I will try this if my client considers using Uniflash option doesn't work or is not an acceptable outcome for my client.