• Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 977 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.

SYS BIOS 6 using HWI

Didier Lafond
Prodigy 210 points

Other Parts Discussed in Thread: CODECOMPOSER, SYSBIOS

Hello,

I am just beginning with Sys/Bios

I use L138 evaluation board from Logic PD, with C6748 processeur, CodeComposer 4.2

I added a new HWI from ti_sysbios_family_c64p_Hw0

It generated following source in app.cfg :

var ti_sysbios_family_c64p_Hwi0Params = new ti_sysbios_family_c64p_Hwi.Params();
ti_sysbios_family_c64p_Hwi0Params.instance.name = "ti_sysbios_family_c64p_Hwi0";
Program.global.ti_sysbios_family_c64p_Hwi0 = ti_sysbios_family_c64p_Hwi.create(5, "&isrAudio", ti_sysbios_family_c64p_Hwi0Params);

and I got these errors after build :

configuring app.x674 from package/cfg/app_p674.cfg ...
cl674 package/cfg/app_p674.c ...
"package/cfg/app_p674.c", line 15647: error: declaration is incompatible with "void *ti_sysbios_family_c64p_Hwi0" (declared at line 1191)
1 error detected in the compilation of "package/cfg/app_p674.c".

I am not sure if I do the right things ...

Thank you for your help

 

 

  • TI__Mastermind 30830 points

    Didier,

    Unfortunately, you picked a global variable name for your Hwi object handle (ti_sysbios_family_c64p_Hwi0) that is already defined by SYS/BIOS.

    Can you try changing it to simpy "Hwi0" and see if the problem clears up?

    Alan DeMars

  • in reply to Alan DeMars
    Prodigy 210 points

    Hello,

    thank you for your answer

    in fact, it works well if I use Hwi from 'Scheduling' (in 'available product ' window) : module ti.sysbios.hal.HWi

    The other module from 'Target specific support, C64p' is ti.sysbios.family.c64p.Hwi

    my interrupt routine seems to work well with module ti.sysbios.hal.HWi, but

    why Hwi appears twice in 'available product' ?

    is there a reason to choose one or other ?

     

     

  • in reply to Didier Lafond
    TI__Mastermind 30830 points

    Didier,

    Which versions of XDCTools and SYS/BIOS are you using? I'm still trying to understand where the auto-generated "ti_sysbios_family_c64p_Hwi0" symbol came from. Newer versions of our products don't seem to have this "feature".

    The Hwi module under "Scheduling" is a generic Hwi module that is target/device independent. The "Scheduling" Hwi module is used primarily in applications (and within SYS/BIOS itself) that must be built to run on multiple targets and/or devices.

    The "Target specific support" Hwi module provides a super set of the APIs and services provided by the "Scheduling" Hwi module. Additional device/target specific APIs are provided for those applications that are more tightly coupled to the device they will run on.

    Alan

  • in reply to Alan DeMars
    Prodigy 210 points

    Hello,

    I use IPC 1.23.4.36

    SYS/BIOS 6.32.4.49

    XDCTools 3.22.3.41

    these are last updates from TI site

    Following lines appears in source :

    var ti_sysbios_family_c64p_Hwi = xdc.useModule('ti.sysbios.family.c64p.Hwi');
    var ti_sysbios_family_c64p_Hwi0Params = new ti_sysbios_family_c64p_Hwi.Params();
    ti_sysbios_family_c64p_Hwi0Params.instance.name = "ti_sysbios_family_c64p_Hwi0";
    Program.global.ti_sysbios_family_c64p_Hwi0 = ti_sysbios_family_c64p_Hwi.create(null, null, ti_sysbios_family_c64p_Hwi0Params);

    if I select 'use Hwi' from 'targer speccific support', C64p, and create a new Hwi

    Didier

     

  • in reply to Didier Lafond
    TI__Mastermind 30830 points

    I filed a bug to track this issue: SDOCM00085250.

    For the moment you can work around this issue by manually adding the following to your config script BEFORE using xgconf to add the Hwi object:

       var c64pHwi = xdc.useModule('ti.sysbios.family.c64p.Hwi');

     

    Alan

  • in reply to Alan DeMars
    Prodigy 210 points

    Hello,

    I tried this, but it did not work

    In fact, error appends if I use both 1 HWI from 'scheduling' and 1 HWI from 'target specific support'

    I create a project from SYSBIOS6, 'Hello' example :

    - from 'available product' : use HWI from 'target specific support' and use HWI from 'scheduling'

    - then create two new HWI

    If I keep default names for Hwi : 'hwi0' and 'ti_sysbios_family_c64p_Hwi0', I get error

    If I change name 'ti_sysbios_family_c64p_Hwi0' to anything else, it compiles OK.

    So, for me, I just have to change name to solve this problem.

    Didier