• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 101 subscribers
  • Views 1135 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.

Reg:SYS/BIOS project creation suing CCS5.2 for TMS320F28335

villuribhanu
Intellectual 310 points

Other Parts Discussed in Thread: SYSBIOS

Hi,

I am new to SYS/BIOS project. In my project I am going to use Mailbox, tasks, semophores, Memories,Buffers, Timers, SWI,HWI etc.

I want to declare all suing configuration file that is static. I want to use HWIINT14. By using the following parameters I am creating the HWI

Handle: HWIINT

ISR Function: Function1()

Interrupt No: 14

Additional Settings:

Agruments Passed to ISR:  0

Interrupt Priority: 18

Event ID:1

Enable at start up: Enable

Masking option: Self

After entering above details and saving the project I am getting "Hwi 14 already in use (by &ti_sysbios_family_c28_TimestampProvider_rolloverFunc__E). app.cfg /sample ti.sysbios.family.c28.Hwi.Instance#1 XDCTools Configuration Marker"

Can any one usggest any application notes for creating SYS/BIOS project.

Thanks & Regards,

Bhanu Prakash Villuri

 

 

 

 

  • 0
    TI__Mastermind 20480 points

    Hi,

    What device are you using? Perhaps I can point you to some more specific device information.

    You can create new SYS/BIOS example projects in CCS. They demonstrate some simple use-cases with SYS/BIOS. This wiki shows on how you can get started and this page also contains several different links to training material.

    The error you're seeing is generated because SYS/BIOS installs a HWI at interrupt vector 14 for its system ticks. You select a different timer to drive the clock module by specifying a different timerId in your .cfg file:

    var Clock = xdc.useModule('ti.sysbios.knl.Clock');
    Clock.timerId = 1;

  • 0 in reply to Tom Kopriva
    Intellectual 310 points

    Thanks for your reply. I am using TMS32028335. Still I am getting same error.

  • 0 in reply to villuribhanu
    TI__Mastermind 20480 points

    Which version of SYS/BIOS and XDCtools are you using?

  • 0 in reply to Tom Kopriva
    Intellectual 310 points

    I am using following versions.

    XDC tools version: 3.23.3.53

    SYS/BIOS version: 6.33.4.39

    Actually I am migrating a project from CCS3.3 to CCS5. I opened the configuration file in CCS3.3 and just replicated the same in CCS5.

    While adding HWI it is throwing the error.

    After configuring the bios settings and I ported my old code and mapped accordingly.

    If I build the code it is saying "You exceeded the error limit"

    Regards,

    Bhanu

     

  • 0 in reply to villuribhanu
    TI__Mastermind 20480 points

    Sorry for the late reply.

    Can you post your .cfg file?

    You're having a conflict with your timers.

    The Timestamp module is trying to use a timer (by creating a Hwi with interrupt 14) which was already created either statically with some other Hwi.create in your .cfg file or by some other module (perhaps the clock module).

    If you are using the clock module, try adding:

    var TimestampProvider = xdc.useModule('ti.sysbios.family.c28.TimestampProvider');
    TimestampProvider.useClockTimer = true;

    into your .cfg file. This will tell the Timestamp module to use the same Timer as what the clock module is already using.

  • 0 in reply to Tom Kopriva
    Prodigy 170 points

    Hello Tom,

    I am new to SYSBIOS, i created a new project with sysbios  examples, selected the c28x examples i am getting few errors, I am using a concerto f28m35h52c1. I have not made any changes in the project yet. 


    **** Build of configuration Debug for project systcsDSP ****

    D:\Program Files\ti\ccsv5\utils\bin\gmake -k all
    'Building file: ../swi.cfg'
    'Invoking: XDCtools'
    "D:/Program Files/ti/xdctools_3_24_05_48/xs" --xdcpath="D:/Program Files/ti/bios_6_33_05_46/packages;D:/Program Files/ti/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.C28_float -p ti.platforms.concertoC28:F28M35H52C1 -r release -c "D:/Program Files/ti/ccsv5/tools/compiler/c2000_6.1.1" --compileOptions "-g --optimize_with_debug" "../swi.cfg"
    making package.mak (because of package.bld) ...
    C:/Users/Admin/AppData/Local/Temp/make7940-1.sh: D:/PROGRA~1/ti/xdctools_3_24_05_48/xs: not found
    making package.mak (because of package.bld) ...
    C:/Users/Admin/AppData/Local/Temp/make4836-1.sh: D:/PROGRA~1/ti/xdctools_3_24_05_48/xs: not found
    gmake.exe: *** No rule to make target `.configuro'. Stop.
    js: "D:/Program Files/ti/xdctools_3_24_05_48/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

    Thank you 

    Ragesh S. Kutty

  • 0 in reply to Ragesh Sivankutty
    TI__Mastermind 37985 points

    Ragesh,
    you should not install XDCtools on a path with spaces. Install it in C:/ti or D:/ti and try again. Also, your problem is not related to the original topic of this thread. Please start a new thread in such cases.

  • 0 in reply to Sasha Slijepcevic
    Expert 1505 points

    I saw the exact same issue using the GUI and HWI for 28335 I had to delete everything or restart. In frustration I switched to dynamic HWI creation

    I also was never able to see the actual HWI from the hardware untill I used dynamic HWI creation but can NOT guarantee the GUI was the issue

    The GUI strangeness was enough for me to not trust xdctools and static BIOS object creation. I saw this today wondeing whether this helps

    NOTE: When using SYS/BIOS, you may run into some heap memory issues with your PC host. Also, when using the GUI, some strange behavior has been identified when clicking on items in the Outline View of your .CFG file. Most of these issues are solved by editing your eclipse.ini file with the following settings:

    -Xms512m

    -Xmx512m

    -XX:MaxPermSize=128m

    The original settings (40, 256, 96) are based on a minimum PC memory configuration. Most modern PCs have more memory. When using SYS/BIOS, the author has found that if these settings are left unchanged, some unreliable situations occur. However, after using the settings above, all the issues disappeared. Your mileage may vary.