• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1437 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.

CCS6 Hex55 Ultility within the CCS6 environment.

Peter Crowhurst
Intellectual 270 points
Other Parts Discussed in Thread: TMS320VC5501, CCSTUDIO

Hi,

Using CCS6 and have new flash utility to program the hex file into my external flash - I would now like to add some configuration values to registers - such as 

-delay 0xF00

-reg_config 0x3401, 0x0034 /* GPIO 2, 4 and 5 are set high */
-reg_config 0x1C80, 0x0000 /* Set PLL to bypas mode */
-reg_config 0x1C80, 0x0008 /* PLL put into reset mode */
-reg_config 0x1C88, 0x0008 /* PLL multiply set to 8 reference 10MHz F=80MHz */
-delay 0xFF00
-reg_config 0x1C80, 0x0001 /* PLL enabled */
-reg_config 0x8400, 0x0002 /* Clock out sys clock 1 */
-reg_config 0x1C82, 0x000B /* CPU clock frequency point C PLL output */
-reg_config 0x1C8C, 0x8000 /* DIV1 set to divide by 1 */
-reg_config 0x1C8E, 0x8000 /* DIV2 set to divide by 1 */
-reg_config 0x1C90, 0x8000 /* DIV3 set to divide by 1 */
-reg_config 0x3401, 0x0000 /* GPIO 2, 4 and 5 are set low */
-delay 0xF00

to speed up the program load time on boot - this seemed to work with the old hex55 utility, but I cannot find a way to add the values in the new window for CCS6.

when I look at the pull down menu it appears a little vague as to how best use it.

Any help at all would be very much appreciated.

Kind regards,

  • 0
    TI__Guru**** 173310 points

    DEV1 said:
    when I look at the pull down menu it appears a little vague as to how best use it.

    I agree that the drop-down options for --reg_config does not appear correct. I will file a bug report to have this looked into.

    In the meantime, you can pass these options via a command file. Add all the options you have listed above to a text file, and then you can pass the file to the hex utility as shown below. The path to the file can be an absolute or relative path. In the example below, hex.cmd is in the main project folder, but since the build directory is typically one level down (in the build configuration directory such as \Debug or \Release), the relative path to hex.cmd is one level up.


    Note that if you place hex.cmd in your project folder, then you will need to also right-click on the file in the Project Explorer view and "Exclude from build", otherwise the linker will try to link with that file.

    One other note: there should not be a space after the comma in the reg config option. Please see this related post.

    Let us know if this solution helps.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    AartiG said:
    I agree that the drop-down options for --reg_config does not appear correct. I will file a bug report to have this looked into.

    Bug tracking # for this is SDSCM00052622.

  • 0 in reply to AartiG
    Intellectual 270 points
    Hi AartiG,

    Thank you for your reply - I did end up using my external command.cmd file, and made some small (almost imperceptible) changes, and it worked (such as removing ";" before the /* text here */. Strangely enough, these weren't in my original file, I only added them as they existed in one of the examples, and I wondered, just trying anything, if this was the issue. But no it wasn't. So, everything seems to compile now

    But I will ask the following question(s)

    1) I tried to not have the space, as suggested and this did not work. When I returned the space the software compiled OK - can you confirm this;
    2) In the older version of the hex55 utility, for the TMS320VC5501 part, I had to specify -v5510:2 in the command file for the 5501, this was reported as a bug, and the -v5510:2 silicon version was provided as a work around, has this been fixed?; If so what is the correct command for the TMS320VC5501?
    3) Can you confirm the range for the delay "-delay 0x0000" < "-delay 0xFFFF";

    Again thank you, it appears there were several things happening at once and it was very confusing, and time consuming.

    Best
  • 0 in reply to Peter Crowhurst
    TI__Guru**** 173310 points

    DEV1 said:
    1) I tried to not have the space, as suggested and this did not work. When I returned the space the software compiled OK - can you confirm this;

    I actually see the opposite.

    If there is a space in the reg_config option, such as: -reg_config 0x3401, 0x0034
    then I get the error:

    'Invoking: C5500 Hex Utility'
    "C:/CCStudio_v6.1.1.00022/ccsv6/tools/compiler/c5500_4.4.1/bin/hex55" -o "test_c5515.hex" "test_c5515.out" ../hex.cmd
    fatal error: missing value after comma in reg_config option

    If I remove the space, it builds ok.

    Can you confirm if you are using the same version of compiler tools (version 4.4.1)?

    DEV1 said:
    2) In the older version of the hex55 utility, for the TMS320VC5501 part, I had to specify -v5510:2 in the command file for the 5501, this was reported as a bug, and the -v5510:2 silicon version was provided as a work around, has this been fixed?; If so what is the correct command for the TMS320VC5501?

    I am not sure which bug you are referring to here. Perhaps if you can provide a reference post (if on the forums) or details on who provided the workaround, I can try to gather more details. Based on this post though, you can see the list of all the devices and revisions known to your compiler version by invoking the compiler on a command prompt using the -vlist option (and -v5501 appears to be one of them).


    DEV1 said:
    3) Can you confirm the range for the delay "-delay 0x0000" < "-delay 0xFFFF";

    I don't have the expertise to answer this. I would suggest asking in the C5000 device forum so the experts there can comment.