CCS: SYS/BIOS minimal example will not build

I was able to reproduce the problem and looking into it.

Todd

That's good to hear.
I'll look forward to what you find. Since this error is defined within a directive specific to some newer compiler versions, I have a suspicion this code wasn't tested after being added to the linker file.
Of course, my main concern has to do with this example not fitting into the memory footprint of the F28069. Hopefully that isnt anything near the problem, since this "Minimal" example is nothing more than the kernel itself with a small bit of code in main.c

Thanks
Robert

Hi Todd,

Any word on resolving this issue? If not, do you have any kind of temporary workaround I can use to "limp along" with some kind of build for doing some basic test development?

I'm kinda stuck in place without a starting point for doing a simple SYS/BIOS test project.

Thanks very much

Robert

Hi Todd,

Yes, this worked, thanks.

I thought this might be the fix, but not being familiar enough with the whole platform, even seemingly simple issues could be deceiving.

Now I can start making some headway on this!

Thanks again

Robert

BTW: I intend fairly quickly to migrate from the SYS/BIOS platform to the full TI-RTOS for C2000 platform. One hurdle in doing this is the lack of a nice simple, buildable example project such as the one we resolved here for SYS/BIOS. I realize there aren't any examples that came with the TI-RTOS C2000 standalone download, but if you happen to know if there is one around somewhere or in some level of beta release, I could certainly use it as the next aid in getting me to where I want to be for actual product development.

Thanks for getting back with the confirmation. We'll get this fixed in the next 6.50 release (May/June timeframe).

Regarding SYS/BIOS and TI-RTOS. We've had SYS/BIOS as a product for awhile. A few years ago we started TI-RTOS as a more complete RTOS (since SYS/BIOS is really a kernel). So TI-RTOS was the kernel (SYS/BIOS) + instrumentation + RTOS aware drivers + stacks + BSP. Over time, we rolled out TI-RTOS for TivaC, TI-RTOS for C2000, TI-RTOS for CC32xx, TI-RTOS for MSP43x, etc.

For the TI-RTOS for C2000, we supplied RTOS aware drivers for only the Arm M3 side of the Concerto devices. We also decided (right or wrong) to only supply Concerto examples in TI-RTOS for C2000. Part of the decision was because we did not have RTOS aware drivers for the C2000 DSPs. It's on the list of things to be done, but never makes it about the cut-off line when scheduling occurs.

If you are using the F28069, I'd stick with the SYS/BIOS product.

For completeness....going forward, the TI-RTOS MSP432, CC13xx, CC26xx, and CC32xx products will only have patch releases. The new development/features will be delivered in the SimpleLink SDKs (for MSP432, etc.).

Hi Todd,

So given what I have to work with, would it make sense to use any of the other completed TI-RTOS projects as a kind of template, just as far as how the file structure is architected for those other hardware platforms, and try to port the structure to an existing SYS/BIOS project such as I have now?

Also, I have the TI-RTOS installed on my CCSv7, which I suppose I can use to create a new TI -RTOS project with the kernel that is part of TI-RTOS C2000, instead of the ( assumed ) older SYS/BIOS kernel. If this would work, then doing the manual port as mentioned above, could I get to a minimal "TI-RTOS C2000 lite" project with just a lot of missing peripheral drivers that I could add myself, or more ideally, can be added when and if TI gets them done sometime in the near future?

Please advise on an alternative if the above is a non-starter.

Thanks again

Robert