TI PRU Cape demos: tiobj2bin fails

I am trying to build (in Windows 7) the PRU_LED0 demo for the TI PRU Cape (for Beaglebone black) using CCSv6 and AM335X_Starterware_02_00_01_01.
The compilation works to give PRU_LED0.out but then when I use the tiob2bin.bat batch file to create the .bin file to load onto an SD card I get the following message:
Unexpected target: unknown at script/mkhex4bin.pl line 261.
error: -image requires ROMS directive

I have seen some other posts with this error message but none seem to help my issue (e.g. use legacy coff not eabi; use armofd.exe and armhex.exe etc.). I have tried using both the PRU cape suggested post build step in CCSv6
and also running the commands directly on the .out file.

Any help to proceed past this stumbling block gratefully received.
B

Try running hexpru with the following command options

-b
-image
ROMS {
                PAGE 0:
                text: o = 0x0, l = 0x1000, files={text.bin}
                PAGE 1:
                data: o = 0x0, l = 0x1000, files={data.bin}
}

Thanks for your rapid response Peter.
I understand now that trying to make a simple example from the PRU cape demo using only PRU_LED0 is flawed because I then only have a pru program without the infrastructure on the arm8 to run it.
My reason for trying to use just the LED0 example was that when following the PRU cape demo instructions I got the linking error:

fatal error #10183: --abi=eabi is incompatible with file “C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Audio/Debug/PRU_Audio_image.obj” (TIABI v0)
(Full listing below.)
My aim, of course, was to get a working rebuild so that I could begin developing my own tests.

You may be wondering whether I have actually run the provided PRU cape demo MLO and app.
I haven’t because when I bought the beaglebone black I didn’t realise I needed an FTDI serial cable AND a right angle header to be able to use the TI PRU cape and run the pru cape demo.
If I could rebuild the demo then I could modify the demo to automatically run one of the apps on bootup e.g. blinking LED0 so that I didn’t need the cable for testing :slight_smile:
Any further help appreciated.
Bryan