New HeapMem Instance disappear from HeapMem tree in SYS/BIOS

Mark Skidmore

I'm migrating from DSP/BIOS to SYS/BIOS and am using the *.cfg file in SYS/BIOS to create a HeapMem instance. When I right-click on HeapMem (in the Outline window), and choose New HeapMem..., CCSv5.1.1 will momentarily create a new heapmem which will display under the HeapMem tree briefly then disappear. Even on the HeapMem tab for the *.cfg file, after clicking on the Instance button (under the Variable Size Heap Management - Instance Settings heading) then clicking on the Add...button, the new heapmem will momentarily display in the Outline window under the HeapMem tree then disappear. Because the heapmem instance disappears, I can't configure it.

Why is the new heapmem instance disappearing from view?

over 13 years ago

0 Alan DeMars over 13 years ago

TI__Mastermind 30830 points

Which version of SYS/BIOS and XDC tools are you using?

I was able to add a new HeapMem instance using CCS 5.2, xds 3.23.02.47, and SYS/BIOS 6.33.05.46.

The xdc tools and sys/bios I'm using are available here:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/index.html)

CCS 5.2 is available here:

http://processors.wiki.ti.com/index.php/Download_CCS

Alan

0 Mark Skidmore over 13 years ago in reply to Alan DeMars

Intellectual 720 points

SYS/BIOS 6.33.04.39

XDC Tools 3.23.02.47

0 Alan DeMars over 13 years ago in reply to Mark Skidmore

TI__Mastermind 30830 points

I tried using the same XDC tools and SYS/BIOS version you are using and am still not able to reproduce your results.

Can you post a zip file of your project?

Or at least share the contents of the .cfg file?

Alan

0 Mark Skidmore over 13 years ago in reply to Alan DeMars

Intellectual 720 points

.cfg attached...if this isn't enough, let me know and I'll post the entire project.

0550.VibrationMonitor.cfg

0 Mark Skidmore over 13 years ago in reply to Mark Skidmore

Intellectual 720 points

Andy - thanks for looking at this...

I upgraded to:

CCS 5.2.0.00069 and SYS/BIOS 6.33.05.46 and I'm still getting the same problem. When I add a new HeapMem, either by right-clicking on HeapMem in the Outline window or by selecting the HeapMem tab in the *.cfg tab and clicking the Add... button, CCSv5.2 still won't display the new HeapMem.

My *.cfg file came from a migrated *.tcf file in CCSv4.2.4. My CCSv5.2.0 is running on Windows 7. Any luck with the previous *.cfg file?

0 Alan DeMars over 13 years ago in reply to Mark Skidmore

TI__Mastermind 30830 points

Mark,

I am actively working on this issue. Please bear with me.

A number of problems have been uncovered. I'll have a more complete answer shortly.

Alan

0 Alan DeMars over 13 years ago in reply to Alan DeMars

TI__Mastermind 30830 points

Mark,

Wow, dd you ever stumble on a can of worms...

I found these issues:

1) It appears that using the GUI configuration tool to add functionality to a converted legacy tcf file has not been tested internally.

For the moment, to get past the disappearing HeapMem instances you'll have to manually move all generated 'xdc.useModule()' entries from the top of the .cfg source file down past all of the legacy 'ti.bios.xxx' lines.

2) CLK module instance creation is broken.

Replace the CLK.xs file in your ti/bios directory with the attached version.

3) The DIO module can't handle named static chanParams.

Replace the DIO.xdt file in your ti/bios directory with the attached version.

4) The PWRM module is NOT supported.

Remove all references to PWRM (including PWRM_swi) from your config file.

5) BIOS 6 does not have a KNL_swi.

Remove references to KNL_swi from your config file.

I modified your config script per the above directions and have attached it to this post

The referenced CLK.xs and DIO.xdt files are attached to this post as a zip file.

Lastly, I filed SDOCM00092901 to address and track these issues.

We are planning a 6.33.06 point release in early July that will incorporate formal solutions to these problems.

Alan

8081.VibrationMonitor.cfg

4174.DIO_CLK.zip

0 Mark Skidmore over 13 years ago in reply to Alan DeMars

Intellectual 720 points

Alan,

That worked. The config came up with heapMem0 and heapMem1. I am able to remove then add them and configure them. Thanks!

Processors

Processors forum

New HeapMem Instance disappear from HeapMem tree in SYS/BIOS