• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 384 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.

Boot differences between DSP BIOS 5 and SYS BIOS?

CalvinC
Intellectual 990 points
Other Parts Discussed in Thread: SYSBIOS

I've been porting a working DSP BIOS project for C6486/C6472 to SYS BIOS. Core 0 runs one image (control path) and the other 5 cores run 5 instances of the main application (all identical except for memory map). I've ported the main app to SYS BIOS and all appears to run when I download the code using the emulator. The Core 0 app is still runinng DSP BIOS but there is no code shared between them. However, when I combine the two apps into a single image so the whole C6472 can be loaded over SRIO, only the Core 0 app runs - no signs of life from the SYS BIOS cores and when I stop them with the emulator they appear to be off in the weeds executing from memory I do not ever reference (0x0010xxxx).

What is different between DSP BIOS and SYS BIOS that might affect booting? Again, the code works just fine when everyone is on DSP BIOS (so all the core reset registers are being correctly written). Does SYS BIOS have hidden startup code that is only runs when the emulator is used?

Thanks,

Calvin Conrey

  • 0
    TI__Mastermind 18320 points

    Calvin,

    I was confused by your message.  You say "Core 0 app is still runinng DSP BIOS" -- so you are running a different version of BIOS on core 0 then what is running on the other cores?  Do I have that right?  If so, why are you doing that?

    Dave

  • 0 in reply to David Friedland
    Intellectual 990 points

    Yes, we are running two different versions: Core0 runs DSP BIOS 5.4 and Core1-5 runs SYS BIOS 6.3. We are taking a working DSP BIOS 5.4 project (all cores running 5.4) and incrementally migrating it to SYS BIOS 6.3 so we can use CCS 4.2 RTDX for real "real time" debugging (not just stop mode). Since Core0 is using the NDK 2.0 my understanding it that it will require additional updates to migrate to SYS BIOS so we started with the code that is strictly internally developed. All HW (timers) configuration is done by Core0 so the SYS BIOS cores should not conflict with Core0. As I mentioned above, it all works when I load with the emulator just not when I boot/load from SRIO.

    Calvin

  • 0 in reply to CalvinC
    TI__Mastermind 32475 points

    Calvin,

    There's no special code in SYSBIOS for booting one way or another.  They should both be the same.  I would recommend looking at what is the difference between loading from emulator versus using SRIO to boot?  Is there some gel files running when you load from the emulator that perhaps inits external memory or something like that?  Is there any communication between the cores and if so, are you using you're own code for that?

    Are you able to gather any additional information on "out in the weeds"?  Are all the other cores in this same state? Was there an exception that was generated?

    Judah