No CIO when using SYS/BIOS SysStd tools

Hi Gilbert;

    Just trying the example programs from the SYS/BIOS install V2.1.1.2 (as listed on the install dir). I thought that the RTOS and SYS/BIOS were the same, but I see a dir here marked 'bios 6_45_00_19' does that sound right? Don't know were to find the GNU version. I found a file marked something like GNU build 8.5.0.201409172108.

Thanks again for your help,

Aaron

SYSBIOS is the kernel we use for our RTOS. The bios_6_45_00_19 does sound like something I'd expect, but it is an older version of SYSBIOS than what we are using for the latest version of TIRTOS.

In CCS, if you go to View -> Resource Explorer (Examples), you should see something similar to the screenshot below:

If you do not see anything related to TIRTOS, you either don't have TIRTOS installed or CCS can't find it.

In the former case, you can go to View -> CCS App Center, and go through the CCS Add-ons to find the appropriate TIRTOS installation for you.

In the latter case, you should make sure that your TIRTOS installation is in the same directory as your ccv6 directory (default should be C:\ti).

If you do see your the correct TIRTOS for your platform, you can go through some of the examples provided there as they have been configured to work for that platform. The "hello world" example is listed under the Kernel Examples, where you can find a few others such as the Memory and Clock examples.

There is a nice FAQ on the SYSBIOS wiki that you can look at which should solve your problem: 

http://processors.wiki.ti.com/index.php/SYS/BIOS_with_GCC_(CortexA)#Why_is_System_printf.28.29.2Fprintf.28.29_not_working_.3F

It basically boils down to:

1. make sure you are using the semihosting module: var SemiHostSupport = xdc.useModule('ti.sysbios.rts.gnu.SemiHostSupport');
2. Change the "nosys" library to "rdimon"
3. Make sure semihosting is enabled in the program/memory load options

There is also a semihosting example in the resource explorer that you can look at.

Hi Gilbert;

   Well, honestly I thought you had it nailed. But I went and checked out the Property page for the program and found that everything was already set up exactly as the example showed except for the xdc source. I set that up but the version I have is newer than the example, I have 3.31.2.38_core while the example shows 3.25.1.64_eng. Not sure if that makes a difference. I build with only 1 warning, My Linearo is newer than what the example expects. The rest is exactly as expected. semihosting engaged, the var in the .CFG file quotes exactly right.

Anything else I may be missing?

Aaron

Hi Gilbert;

   Well, I played around with the various libraries to see what would build and what wouldn't. Turns out that if I leave it on <automatic> it picks libc.a. That is the only one that works. Otherwise the build has errors. So I thought that maybe the problem is with the libraries that the build chose to use. I noted that in the Project properties-->GNU Linker-> libraries listings under Library search path, the paths all point to some offshoot of starterware. Didn't look right. What do you think? Shouldn't the SYS/BIOS use .....\fpu stuff?

Aaron

The CIO should work with our examples. Can you zip up your project and post it so we can look over it?

If you want to use the UART to print out to a console app, you have the option of using SysCallback to your cfg file like so:

var SysCallback = xdc.useModule('xdc.runtime.SysCallback');
SysCallback.putchFxn = "&yourCustomUartPrintf_putch"; // your implementation
SysCallback.flushFxn = "&yourCustomUartPrintf_flush"; // your implementation
System.SupportProxy = SysCallback;

This will allow you to still make calls with System_printf(), but it will print our over UART once you implement the two functions.

As for getting a HOST USB to serial driver, that is a better question for the device forums.

Gilbert

4812.example_utils.zip

Hi Gilbert;

   Well, definitely stranger and stranger. I created a new directory, copied the files over from the old one. Did a binary edit on the new copy to change the project name. re-imported from the new directory with the updated name and voila. I got the stuff working. You're right about the nosys library. But I couldn't get rid of it. Every time I deleted it, it came right back. Never did get CONSOLEUtilities working though. Maybe later.

   So I'm going to change the subject and ask you how to find the "fully qualified name" of my idle thread fxn()? No clear examples in the help.

Hi Gilbert;

    Finally had a chance to check out the Idle function in the idle.c module. Not breaking there at all. I double checked the .CFG file and do have the idle operation engaged. Idle_run() is not executing. How do I find the problem?

Hi Gilbert;

   Good news I did get the idle loop processing. It was just the buggy UI to configure the .CFG file again. I note that many of my problems have this as the root cause. I manually edited the file to set the enabletaskidle flag to true and it worked fine.

    Back on the CIO problem with the CONSOLEUtils. I did some further digging. If I simply use the putchar() call directly in line with my code, I can get the char on the stdout console output. Turns out that the starterware library that comes prebuilt with the CSS is built without the 'SEMIHOSTING' compiler flag set. So they are compiled without the semihosting stdout support. I need to re-build the 'utils' lib to make it work properly. There is a proj file at the head directory of the utils tree. Can't get it to load. Can you point me at the procedure to rebuild the supplied libraries?

Thanks again,

Aaron