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 config problems with CCS 5.1

Other Parts Discussed in Thread: SYSBIOS

CCS 5.1.0.09000

 

problem 1: added a new section name but was unable to permanently enter a Memory Segment for it - further values for address alignment and maybe even fill were "forgotten".

problem 2: Memory Segments get listed with address and length. these values will be displayed as signed integers on the first click. after a few clicks on other segments these values will change to a hexadecimal display.

problem 3: list box where Memory Segments are listed is not wide enough and does not expose a horizontal scroll bar.

 

  • Hi Alexander --

    I will file bugs for item 2 and 3 above.  

    I'm having problems reproducing item 1.   How are you adding the memory segment name?   You should add the name by typing text into the 'Memory Segment' box within the UI.  Are you typing "DDR" (without quotes) into the Memory Segment box?  Or are you clicking on the DDR in the "Listed for reference" area and expecting that to fill in the Memory Segment.   I'd like to reproduce this and get a bug filed.

    -Karl-

  • thanks for caring about item 2&3.

    in item 1 after creating and renaming a new segment i entered the text manually into the text box on the right. then i clicked a bit forth and back - suddenly the values 2 to 4 have changed back to some defaults.

  • Hi Alexander --

    I still cannot reproduce this.  Is it possible for you to give me exact sequence to create #1?   Is it easy for you to reproduce or is it intermittent?

    Thanks,
    -Karl-

  • I am having the same issue only with me it seems to happen once I save the Project.

    While the section is still there all of its paramaters are set to undefined.

    I am tryiing to move the defaults sections from the DDR memory to the internal shared memory and dont seem to be able to do that.

  • It loos like an update to xdctools seemed to have fixed the issue for me.

    xdctools 3.23.00.32 doesn't have the issue.

    Also noticed that there are some ARM library issues that got fixed by also upgrading SYSBIOS to 6.33.00.18 and IPC 1.24.00.16.