• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 714 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.

AWR6843: SYS/BIOS support for AWR6843 and IWR6843

Bert
Prodigy 130 points
Part Number: AWR6843
Other Parts Discussed in Thread: MMWAVEICBOOST, , IWR6843, , SYSBIOS

There's many instances of this question our there, and I have scanned various threads, but I still can't quite connect the dots.

In front of me I have the MMWAVEICBOOST connected to my AWR6843ISK. I can pull down the following project of interest, and build without issue:

https://dev.ti.com/tirex/explore/node?node=AK2Pfzv8YhOKYSVHLm9wQw__VLyFKFf__LATEST

However, when digging into the settings, I see that project is for the IWR6843, not the AWR6843:

So the fact that I can build that demo is good, but we now want to create our own project. For the new project, both CAN interfaces are required. However, in the following post it mentions that the AWR allows both CAN interfaces, but the IWR does not:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/931016/ccs-iwr6843-iwr6843-vs-awr6843-version-question

So I figured I would tackle that issue when we get to it, and to first just create a blank project, specifically for the AWR6843.

I am able to create the project, but upon building, I get an error indicating the AWR6843 device is not supported.

The AWR68XX device is not currently supported.
The following devices are supported in the ti.catalog.arm.cortexr5 catalog:
	AM65X  RM57D8XX  SIMFLEMING  SIMMAXWELL  
subdir_rules.mk:12: recipe for target 'build-577601409-inproc' failed
js: "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/Settings.xs", line 744: Error: Unsupported device!

I then opened up my version of sys_bios C:\ti\bios_6_73_01_01\packages\ti\sysbios\family\arm and verify that AWR is not one of the options

/* Cortex-R5 devices */
deviceTable["ti.catalog.arm.cortexr5"]["RM57D8.*"] = deviceTable["ti.catalog.arm.cortexr5"]["RM57D8XX"];
deviceTable["ti.catalog.arm.cortexr5"]["RM57L8.*"] = deviceTable["ti.catalog.arm.cortexr5"]["RM57D8XX"];
deviceTable["ti.catalog.arm.cortexr4"]["AWR1.*"]   = deviceTable["ti.catalog.arm.cortexr4"]["AWR14XX"];
deviceTable["ti.catalog.arm.cortexr4"]["IWR1.*"]   = deviceTable["ti.catalog.arm.cortexr4"]["AWR14XX"];
deviceTable["ti.catalog.arm.cortexr4"]["IWR6.*"]   = deviceTable["ti.catalog.arm.cortexr4"]["AWR14XX"];

So now I'm stumped. Version wise, I am using the latest Code Composer (11.0.0.00012), and my project has the following:

Technically 6.73.1.01 is not the latest bios, but when going to the latest, AWR6843 is not mentioned as a supported device, but the IWR6843 is.

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sysbios/6_83_00_18/exports/bios_6_83_00_18/docs/cdoc/ti/sysbios/family/doc-files/devices.html

Is there something I am missing?

  • 0
    TI__Mastermind 23725 points

    Hello

    Please share the setiing for CCS and core you have selected.

    Ensure that these match the device core vs device selected.

    Thank you,

    vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 130 points

    Thanks . It's strange because, if I just create a barebones SYS/BIOS project, I get the same results. I have attached the MSS/DSS projects for reference, they are small, and just the initial projects.

    In terms of steps, I created these by doing the following:


    1.) Create a new CCS project, Selecting SYS/BIOS 'Typical' as the Template, and setting the target to AWR6843



    2.) In the 'Products' tab, the Target, and Platform fields are empty. The Platform field has an indicator for a drop-down, but it's empty. To manually fill these fields in, I grabbed the two fields from the out-of-box demo, and changes IWR to AWR.


    3.) Perform the same steps for the C67XX project. In this case, the 'Target' field was already filled in, so I only had to update the Platform field. That too had an empty drop-down, so I manually filled in based on the out-of-box demo.

    At this point, the projects get created, but when building, both fail with the same error:

    The AWR68XX device is not currently supported.
The following devices are supported in the ti.catalog.arm.cortexr5 catalog:
	AM65X  RM57D8XX  SIMFLEMING  SIMMAXWELL  
subdir_rules.mk:12: recipe for target 'build-1178647759-inproc' failed
js: "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/Settings.xs", line 744: Error: Unsupported device!
    "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/Settings.xs", line 912
    "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/Settings.xs", line 254
    "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/Settings.xs", line 124
    "C:/Users/user/workspace_v11/Bert_MSS_Delete/app.cfg", line 12
    "./package/cfg/app_per4ft.cfg", line 204
gmake.exe: *** [package.mak:202: package/cfg/app_per4ft.xdl] Error 1
js: "C:/ti/ccs1100/xdctools_3_62_01_16_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-1178647759-inproc] Error 1
gmake: *** No rule to make target 'build-1178647759', needed by 'configPkg/compiler.opt'.
gmake: *** No rule to make target 'build-1178647759', needed by 'configPkg/linker.cmd'.
gmake: Target 'all' not remade because of errors.


    Let me know if anything jumps out.

    Thanks!

    Example_For_TI.zip

  • +1 in reply to Bert
    TI__Genius 17265 points

    Hi,

    Having the project set to IWR instead of AWR in CCS should not have any effect on the project performance. IWR6843 and AWR6843 are made from the same silicon, but since IWR was created first, the AWR equivalent was not always called out as supported. I will look into whether we can correct this inconsistency on our end, but could you try running your project with it set as IWR for the time being? Please let me know if you run into any issues.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 130 points

     yes I can confirm, changing from AWR to IWR resolves the issue.

    You may have already answered this question but, can you confirm that temporarily changing from AWR to IWR will still allow for two CAN interfaces?

    https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/931016/ccs-iwr6843-iwr6843-vs-awr6843-version-question

    "The AWR6843 is automotive qualified and has 2 CAN interface, the IWR6843 is for industrial and other uses cases so
    it isn't automotive qualified and only 1 CAN interface is available."

    I can probably cobble something together to test myself, but was just curious if you knew off the top of your head.

    Thanks for the support!

  • +1 in reply to Bert
    TI__Genius 17265 points

    Hi,

    First, I want to clear up a common misconception, both IWR6843 and AWR6843 have 2 CAN interfaces, but they do differ in type.
    IWR6843: 1 MCAN controller (CANFD IP from Bosch) + 1 DCAN Controller (Classical CAN ip from Bosch)
    AWR6843: 2 MCAN controller (CANFD IP from Bosch)

    For this reason, it should be fine for both devices. You will just be calling the CANFD driver for both interfaces on the AWR version. If you encounter any issues with this, feel free to make a new post and tag me in it so that I can help clear things up.

    Best Regards,
    Alec