• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 351 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.

help with run c program on c6455 dsk

elaph ali
Prodigy 60 points

hi ;
i have wrote a simple program in c and write the cmd file
the c file is
#include<stdio.h>
void main()
{
int i;
for(i=0;i<10;i++)
{
printf("I=%d",i);
}
}
the cmd file is
MEMORY
{
IRAM: O=0X00000000 L=0X00080000
}
SECTIONS
{
.cinit > IRAM

.text > IRAM

.stack > IRAM

.bss > IRAM

.const > IRAM

.data > IRAM

. far > IRAM

.switch > IRAM

.sysmem> IRAM

.tables > IRAM

.cio > IRAM
}
when build the program the is no error and when load it no error but when run there is no value appear on the screen and
in the section messages the is the following message

loader : one or more sections of your program falls into memory region that is not writable .these regions not actually be written to the target . check your linker configuration and /or memory map

Trouble writing register : error 0x00000006/-1176 error during : memory , registor , the IM memory request is not servied by the HW memory system. this could be caused by the memory address specified does not exist in the spcified memory cache level . sequence ID : 6 error code : -1176 error class 0x00000006
i am using the ccs v3.3
my regards

  • 0
    TI__Guru* 84110 points

    The DSK6455 comes with example projects. Several of them use printf. You need to start with a known good example and get it to run, then start modifying from there. The working examples are provided to give you a good starting place.

    The error message says that some sections of your program are in bad memory space (not writable). The recommendation is to check your linker cmd file and your linker map file.

    Regards,
    RandyP

     

    If you need more help, please reply back. If this answers the question, please click  Verify Answer  , below.

  • 0 in reply to RandyP
    Prodigy 60 points

    hello i have been try the examples of  that come with the DSK but the same error happen there is nothing on the screen appear and the same message appear too

  • 0 in reply to elaph ali
    TI__Guru* 84110 points

    The sequence of events is not clear here. The error message you have shown above is a "loader" message so it would appear after you try to load the program. Since the program is not properly loaded, it is reasonable to expect the program to not properly run. In fact, if you get a loader error, there is no reason to try to run the program since it was not loaded.

    If you open the led.pjt project from the "examples\led" folder, then build and load that project, you should not get this error message.

    Please try this and let us know how it works for you. If it does not work, please report the exact and detailed steps that you took to get to the load step, and again what the error message is.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Prodigy 60 points

    hi ;

    i do what you tell me  about the leg.pjt it works with no message of loader and iits works very good but the problem with the program i write and that happen when load a programs written by me

    the procedure i do when work

    is adding files the build when no error and warnings  and remarks appear i load the output program using

    file-------->load program------>file.out(open)

    the loader message appear

    you can see the programs and linker files i have write them in my Question

    my regards

     

     

  • 0 in reply to elaph ali
    TI__Guru* 84110 points

    Since you have a working example, please compare the files you have written to the files that work. Any differences need to be explained as to why you have made those changes. This is why we give you working examples.

    The best procedure is to copy the entire working project folder, such as the led project, edit the new pjt file to make sure the paths are correct, then build and run it to make sure it still works like you found earlier. Then start making the changes to bring in your own files, but do it slowly. For example, copy in your linker cmd file and see how well it works. Then copy in your source files, replacing the others as needed. With each change, see if you have reached this error message or not. Eventually, you will find which file or which changes causes the error and then you will be able to figure out what the problem is.

    Does this seem to be a useful approach for you?

    Please let us know what you find out. The more information you can provide, the easier it will be to find your solution.

    Regards,
    RandyP