hi all:
I meet a strange problem on 510usb emulator.
Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb
emulator.(4) program are all located in internal RAM
I write a test project in ASM. After the compiling and linking, the
output file can be downloaded to DSP(C6727B), and it runs well.
But when I write a test project in C, after the compiling and linking,
the output file can't be downloaded to DSP completely, and it can't
run! Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the
other code are missing!! They are not downloaded to the corresponding address in
DSP.
I can't understand it. I checked the project in C carefully,
especiall all the build options, and I think I don't make a mistake.
I am doubt that whether the driver of 510 emulator is not correct? or
there are some mistakes I make which I don't know?
Are there someone meet the same problem? Or someone can give me some
suggestion to solve it? THANKS!
luckeybird
---------------------------------
ŻϷ껪ӮȡҺʾ
Problems on 510usb emulator
Started by ●December 10, 2007
Reply by ●December 10, 20072007-12-10
bHVja2V5YmlyZCwKCk9uIERlYyAxMCwgMjAwNyA5OjEyIEFNLCBsdWNrIDxsdWNrZXliaXJk
QHlhaG9vLmNvbS5jbj4gd3JvdGU6Cgo+IGhpIGFsbDoKPiAgICAgIEkgbWVldCBhIHN0cmFu
Z2UgcHJvYmxlbSBvbiA1MTB1c2IgZW11bGF0b3IuCj4gICAgICBFbnZpcm9ubWVudDogKDEp
RFNQIEM2NzI3QiwgKDIpQ0NTIHYzLjMgLCAoMyllbXVsYXRvcjogNTEwdXNiIGVtdWxhdG9y
Lig0KSBwcm9ncmFtIGFyZSBhbGwgbG9jYXRlZCBpbiBpbnRlcm5hbCBSQU0KPiAgICAgIEkg
d3JpdGUgYSB0ZXN0IHByb2plY3QgaW4gQVNNLiBBZnRlciB0aGUgY29tcGlsaW5nIGFuZCBs
aW5raW5nLCB0aGUgb3V0cHV0IGZpbGUgY2FuIGJlIGRvd25sb2FkZWQgdG8gRFNQKEM2NzI3
QiksIGFuZCBpdCBydW5zIHdlbGwuCj4gICAgICBCdXQgd2hlbiBJIHdyaXRlIGEgdGVzdCBw
cm9qZWN0IGluIEMsIGFmdGVyIHRoZSBjb21waWxpbmcgYW5kIGxpbmtpbmcsIHRoZSBvdXRw
dXQgZmlsZSBjYW4ndCBiZSBkb3dubG9hZGVkIHRvIERTUCBjb21wbGV0ZWx5LCBhbmQgaXQg
Y2FuJ3QgcnVuISBUeXBpY2FsbHksIG9ubHkgdGhlIGZpcnN0IDQtYnl0ZXMgY2FuIGJlIGRv
d25sb2FkZWQgdG8gRFNQIGJ5IEpUQUcsIGFuZCB0aGUgb3RoZXIgY29kZSBhcmUgbWlzc2lu
ZyEhIFRoZXkgYXJlIG5vdCBkb3dubG9hZGVkIHRvIHRoZSBjb3JyZXNwb25kaW5nIGFkZHJl
c3MgaW4gRFNQLgo+ICAgICAgSSBjYW4ndCB1bmRlcnN0YW5kIGl0LiBJIGNoZWNrZWQgdGhl
IHByb2plY3QgaW4gQyBjYXJlZnVsbHksIGVzcGVjaWFsbCBhbGwgdGhlIGJ1aWxkIG9wdGlv
bnMsIGFuZCBJIHRoaW5rIEkgZG9uJ3QgbWFrZSBhIG1pc3Rha2UuCj4gICAgICBJIGFtIGRv
dWJ0IHRoYXQgd2hldGhlciB0aGUgZHJpdmVyIG9mIDUxMCBlbXVsYXRvciBpcyBub3QgY29y
cmVjdD8KClRoZSBYRFM1MTAgaGFzIG5vIGlkZWEgYWJvdXQgaG93IHRoZSAnLm91dCcgZmls
ZSB3YXMgZ2VuZXJhdGVkLiBZb3VyCnByb2JhYmx5IGhhdmUgYSBwcm9ibGVtIHdpdGggeW91
ciBDIHByb2plY3QgbGlua2VyIGNvbW1hbmQgZmlsZS4gSWYKeW91IGRvIG5vdHNlZSB0aGUg
cHJvYmxlbSwgeW91IGNhbiBydW4gJ29mZDZ4IHlvdXJPdXRGaWxlTmFtZScgZnJvbSBhCkRP
UyBwcm9tcHQgaW4gdGhlIGRpcmVjdG9yeSB0aGF0IGNvbnRhaW5zIHRoZSBvdXQgZmlsZS4g
W3lvdSB3aWxsIG5lZWQKYSBwYXRoIHRvICdDOlw8Q0NTdHVkaW9fSW5zdGFsbF9EaXI+XEM2
MDAwXGNndG9vbHNcYmluJ10uIFRoaXMgd2lsbAphbmFseXplIHlvdXIgJy5vdXQnIGZpbGUu
CgptaWtlZHVubgo+IG9yIHRoZXJlIGFyZSBzb21lIG1pc3Rha2VzIEkgbWFrZSB3aGljaCBJ
IGRvbid0IGtub3c/Cj4gICAgICBBcmUgdGhlcmUgc29tZW9uZSBtZWV0IHRoZSBzYW1lIHBy
b2JsZW0/IE9yIHNvbWVvbmUgY2FuIGdpdmUgbWUgc29tZSBzdWdnZXN0aW9uIHRvIHNvbHZl
IGl0PyBUSEFOS1MhCj4KPiBsdWNrZXliaXJkCj4KPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXwq9+Mjr0cW7otPOz7e8zsTqu6qjrNOuyKHSur6nz9TKvsb3o6EgCgoKCi0t
IAp3d3cuZHNwcmVsYXRlZC5jb20vYmxvZ3MtMS9uZi9NaWtlX0R1bm4ucGhwCgoKTkVXISAg
WW91IGNhbiBub3cgcG9zdCBhIG1lc3NhZ2Ugb3IgYWNjZXNzIGFuZCBzZWFyY2ggdGhlIGFy
Y2hpdmVzIG9mIHRoaXMgZ3JvdXAgb24gRFNQUmVsYXRlZC5jb206Cmh0dHA6Ly93d3cuZHNw
cmVsYXRlZC5jb20vZ3JvdXBzL2M2eC8xLnBocAoKX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwpOb3RlOiBJZiB5b3UgZG8gYSBzaW1wbGUgInJlcGx5IiB3aXRoIHlv
dXIgZW1haWwgY2xpZW50LCBvbmx5IHRoZSBhdXRob3Igb2YgdGhpcyBtZXNzYWdlIHdpbGwg
cmVjZWl2ZSB5b3VyIGFuc3dlci4gIFlvdSBuZWVkIHRvIGRvIGEgInJlcGx5IGFsbCIgaWYg
eW91IHdhbnQgeW91ciBhbnN3ZXIgdG8gYmUgZGlzdHJpYnV0ZWQgdG8gdGhlIGVudGlyZSBn
cm91cC4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQWJvdXQgdGhp
cyBkaXNjdXNzaW9uIGdyb3VwOgoKQXJjaGl2ZXM6ICBodHRwOi8vd3d3LmRzcHJlbGF0ZWQu
Y29tL2dyb3Vwcy9jNngvMS5waHAKClRvIFBvc3Q6ICBTZW5kIGFuIGVtYWlsIHRvIGM2eEB5
YWhvb2dyb3Vwcy5jb20KCk90aGVyIERTUCBSZWxhdGVkIEdyb3VwczogaHR0cDovL3d3dy5k
c3ByZWxhdGVkLmNvbS9ncm91cHMucGhwIApZYWhvbyEgR3JvdXBzIExpbmtzCgo8Kj4gVG8g
dmlzaXQgeW91ciBncm91cCBvbiB0aGUgd2ViLCBnbyB0bzoKICAgIGh0dHA6Ly9ncm91cHMu
eWFob28uY29tL2dyb3VwL2M2eC8KCjwqPiBZb3VyIGVtYWlsIHNldHRpbmdzOgogICAgSW5k
aXZpZHVhbCBFbWFpbCB8IFRyYWRpdGlvbmFsCgo8Kj4gVG8gY2hhbmdlIHNldHRpbmdzIG9u
bGluZSBnbyB0bzoKICAgIGh0dHA6Ly9ncm91cHMueWFob28uY29tL2dyb3VwL2M2eC9qb2lu
CiAgICAoWWFob28hIElEIHJlcXVpcmVkKQoKPCo+IFRvIGNoYW5nZSBzZXR0aW5ncyB2aWEg
ZW1haWw6CiAgICBtYWlsdG86YzZ4LWRpZ2VzdEB5YWhvb2dyb3Vwcy5jb20gCiAgICBtYWls
dG86YzZ4LWZ1bGxmZWF0dXJlZEB5YWhvb2dyb3Vwcy5jb20KCjwqPiBUbyB1bnN1YnNjcmli
ZSBmcm9tIHRoaXMgZ3JvdXAsIHNlbmQgYW4gZW1haWwgdG86CiAgICBjNngtdW5zdWJzY3Jp
YmVAeWFob29ncm91cHMuY29tCgo8Kj4gWW91ciB1c2Ugb2YgWWFob28hIEdyb3VwcyBpcyBz
dWJqZWN0IHRvOgogICAgaHR0cDovL2RvY3MueWFob28uY29tL2luZm8vdGVybXMvCiAK
QHlhaG9vLmNvbS5jbj4gd3JvdGU6Cgo+IGhpIGFsbDoKPiAgICAgIEkgbWVldCBhIHN0cmFu
Z2UgcHJvYmxlbSBvbiA1MTB1c2IgZW11bGF0b3IuCj4gICAgICBFbnZpcm9ubWVudDogKDEp
RFNQIEM2NzI3QiwgKDIpQ0NTIHYzLjMgLCAoMyllbXVsYXRvcjogNTEwdXNiIGVtdWxhdG9y
Lig0KSBwcm9ncmFtIGFyZSBhbGwgbG9jYXRlZCBpbiBpbnRlcm5hbCBSQU0KPiAgICAgIEkg
d3JpdGUgYSB0ZXN0IHByb2plY3QgaW4gQVNNLiBBZnRlciB0aGUgY29tcGlsaW5nIGFuZCBs
aW5raW5nLCB0aGUgb3V0cHV0IGZpbGUgY2FuIGJlIGRvd25sb2FkZWQgdG8gRFNQKEM2NzI3
QiksIGFuZCBpdCBydW5zIHdlbGwuCj4gICAgICBCdXQgd2hlbiBJIHdyaXRlIGEgdGVzdCBw
cm9qZWN0IGluIEMsIGFmdGVyIHRoZSBjb21waWxpbmcgYW5kIGxpbmtpbmcsIHRoZSBvdXRw
dXQgZmlsZSBjYW4ndCBiZSBkb3dubG9hZGVkIHRvIERTUCBjb21wbGV0ZWx5LCBhbmQgaXQg
Y2FuJ3QgcnVuISBUeXBpY2FsbHksIG9ubHkgdGhlIGZpcnN0IDQtYnl0ZXMgY2FuIGJlIGRv
d25sb2FkZWQgdG8gRFNQIGJ5IEpUQUcsIGFuZCB0aGUgb3RoZXIgY29kZSBhcmUgbWlzc2lu
ZyEhIFRoZXkgYXJlIG5vdCBkb3dubG9hZGVkIHRvIHRoZSBjb3JyZXNwb25kaW5nIGFkZHJl
c3MgaW4gRFNQLgo+ICAgICAgSSBjYW4ndCB1bmRlcnN0YW5kIGl0LiBJIGNoZWNrZWQgdGhl
IHByb2plY3QgaW4gQyBjYXJlZnVsbHksIGVzcGVjaWFsbCBhbGwgdGhlIGJ1aWxkIG9wdGlv
bnMsIGFuZCBJIHRoaW5rIEkgZG9uJ3QgbWFrZSBhIG1pc3Rha2UuCj4gICAgICBJIGFtIGRv
dWJ0IHRoYXQgd2hldGhlciB0aGUgZHJpdmVyIG9mIDUxMCBlbXVsYXRvciBpcyBub3QgY29y
cmVjdD8KClRoZSBYRFM1MTAgaGFzIG5vIGlkZWEgYWJvdXQgaG93IHRoZSAnLm91dCcgZmls
ZSB3YXMgZ2VuZXJhdGVkLiBZb3VyCnByb2JhYmx5IGhhdmUgYSBwcm9ibGVtIHdpdGggeW91
ciBDIHByb2plY3QgbGlua2VyIGNvbW1hbmQgZmlsZS4gSWYKeW91IGRvIG5vdHNlZSB0aGUg
cHJvYmxlbSwgeW91IGNhbiBydW4gJ29mZDZ4IHlvdXJPdXRGaWxlTmFtZScgZnJvbSBhCkRP
UyBwcm9tcHQgaW4gdGhlIGRpcmVjdG9yeSB0aGF0IGNvbnRhaW5zIHRoZSBvdXQgZmlsZS4g
W3lvdSB3aWxsIG5lZWQKYSBwYXRoIHRvICdDOlw8Q0NTdHVkaW9fSW5zdGFsbF9EaXI+XEM2
MDAwXGNndG9vbHNcYmluJ10uIFRoaXMgd2lsbAphbmFseXplIHlvdXIgJy5vdXQnIGZpbGUu
CgptaWtlZHVubgo+IG9yIHRoZXJlIGFyZSBzb21lIG1pc3Rha2VzIEkgbWFrZSB3aGljaCBJ
IGRvbid0IGtub3c/Cj4gICAgICBBcmUgdGhlcmUgc29tZW9uZSBtZWV0IHRoZSBzYW1lIHBy
b2JsZW0/IE9yIHNvbWVvbmUgY2FuIGdpdmUgbWUgc29tZSBzdWdnZXN0aW9uIHRvIHNvbHZl
IGl0PyBUSEFOS1MhCj4KPiBsdWNrZXliaXJkCj4KPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXwq9+Mjr0cW7otPOz7e8zsTqu6qjrNOuyKHSur6nz9TKvsb3o6EgCgoKCi0t
IAp3d3cuZHNwcmVsYXRlZC5jb20vYmxvZ3MtMS9uZi9NaWtlX0R1bm4ucGhwCgoKTkVXISAg
WW91IGNhbiBub3cgcG9zdCBhIG1lc3NhZ2Ugb3IgYWNjZXNzIGFuZCBzZWFyY2ggdGhlIGFy
Y2hpdmVzIG9mIHRoaXMgZ3JvdXAgb24gRFNQUmVsYXRlZC5jb206Cmh0dHA6Ly93d3cuZHNw
cmVsYXRlZC5jb20vZ3JvdXBzL2M2eC8xLnBocAoKX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwpOb3RlOiBJZiB5b3UgZG8gYSBzaW1wbGUgInJlcGx5IiB3aXRoIHlv
dXIgZW1haWwgY2xpZW50LCBvbmx5IHRoZSBhdXRob3Igb2YgdGhpcyBtZXNzYWdlIHdpbGwg
cmVjZWl2ZSB5b3VyIGFuc3dlci4gIFlvdSBuZWVkIHRvIGRvIGEgInJlcGx5IGFsbCIgaWYg
eW91IHdhbnQgeW91ciBhbnN3ZXIgdG8gYmUgZGlzdHJpYnV0ZWQgdG8gdGhlIGVudGlyZSBn
cm91cC4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQWJvdXQgdGhp
cyBkaXNjdXNzaW9uIGdyb3VwOgoKQXJjaGl2ZXM6ICBodHRwOi8vd3d3LmRzcHJlbGF0ZWQu
Y29tL2dyb3Vwcy9jNngvMS5waHAKClRvIFBvc3Q6ICBTZW5kIGFuIGVtYWlsIHRvIGM2eEB5
YWhvb2dyb3Vwcy5jb20KCk90aGVyIERTUCBSZWxhdGVkIEdyb3VwczogaHR0cDovL3d3dy5k
c3ByZWxhdGVkLmNvbS9ncm91cHMucGhwIApZYWhvbyEgR3JvdXBzIExpbmtzCgo8Kj4gVG8g
dmlzaXQgeW91ciBncm91cCBvbiB0aGUgd2ViLCBnbyB0bzoKICAgIGh0dHA6Ly9ncm91cHMu
eWFob28uY29tL2dyb3VwL2M2eC8KCjwqPiBZb3VyIGVtYWlsIHNldHRpbmdzOgogICAgSW5k
aXZpZHVhbCBFbWFpbCB8IFRyYWRpdGlvbmFsCgo8Kj4gVG8gY2hhbmdlIHNldHRpbmdzIG9u
bGluZSBnbyB0bzoKICAgIGh0dHA6Ly9ncm91cHMueWFob28uY29tL2dyb3VwL2M2eC9qb2lu
CiAgICAoWWFob28hIElEIHJlcXVpcmVkKQoKPCo+IFRvIGNoYW5nZSBzZXR0aW5ncyB2aWEg
ZW1haWw6CiAgICBtYWlsdG86YzZ4LWRpZ2VzdEB5YWhvb2dyb3Vwcy5jb20gCiAgICBtYWls
dG86YzZ4LWZ1bGxmZWF0dXJlZEB5YWhvb2dyb3Vwcy5jb20KCjwqPiBUbyB1bnN1YnNjcmli
ZSBmcm9tIHRoaXMgZ3JvdXAsIHNlbmQgYW4gZW1haWwgdG86CiAgICBjNngtdW5zdWJzY3Jp
YmVAeWFob29ncm91cHMuY29tCgo8Kj4gWW91ciB1c2Ugb2YgWWFob28hIEdyb3VwcyBpcyBz
dWJqZWN0IHRvOgogICAgaHR0cDovL2RvY3MueWFob28uY29tL2luZm8vdGVybXMvCiAK
Reply by ●December 11, 20072007-12-11
luckeybird,
On 12/10/07, luck wrote:
>
> mikedunn:
> Thanks for your suggestion!
> I use the ofd6x to analysis .out file. It displays all the section
> information and symble table,some like the information gived by .map file.
> But I can't find a obviously mistake.
> I compare the two analysis results of ASM and C project. I think the
> results are similar and right, or maybe I don't know which is wrong.
>
>
Have you verified that all addresses are fir internal memory??
0x10000000 - 0x1003FFFF.
mikedunn
luckeybird
>
> Michael Dunn > д
> luckeybird,
>
> On Dec 10, 2007 9:12 AM, luck >
> wrote:
>
> > hi all:
> > I meet a strange problem on 510usb emulator.
> > Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb
> emulator.(4) program are all located in internal RAM
> > I write a test project in ASM. After the compiling and linking, the
> output file can be downloaded to DSP(C6727B), and it runs well.
> > But when I write a test project in C, after the compiling and linking,
> the output file can't be downloaded to DSP completely, and it can't run!
> Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the
> other code are missing!! They are not downloaded to the corresponding
> address in DSP.
> > I can't understand it. I checked the project in C carefully, especiall
> all the build options, and I think I don't make a mistake.
> > I am doubt that whether the driver of 510 emulator is not correct?
>
> The XDS510 has no idea about how the '.out' file was generated. Your
> probably have a problem with your C project linker command file. If
> you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
> DOS prompt in the directory that contains the out file. [you will need
> a path to 'C:\\C6000\cgtools\bin']. This will
> analyze your '.out' file.
>
> mikedunn
> > or there are some mistakes I make which I don't know?
> > Are there someone meet the same problem? Or someone can give me some
> suggestion to solve it? THANKS!
> >
> > luckeybird
>
> --
> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>
>
>
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
On 12/10/07, luck wrote:
>
> mikedunn:
> Thanks for your suggestion!
> I use the ofd6x to analysis .out file. It displays all the section
> information and symble table,some like the information gived by .map file.
> But I can't find a obviously mistake.
> I compare the two analysis results of ASM and C project. I think the
> results are similar and right, or maybe I don't know which is wrong.
>
>
Have you verified that all addresses are fir internal memory??
0x10000000 - 0x1003FFFF.
mikedunn
luckeybird
>
> Michael Dunn > д
> luckeybird,
>
> On Dec 10, 2007 9:12 AM, luck >
> wrote:
>
> > hi all:
> > I meet a strange problem on 510usb emulator.
> > Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb
> emulator.(4) program are all located in internal RAM
> > I write a test project in ASM. After the compiling and linking, the
> output file can be downloaded to DSP(C6727B), and it runs well.
> > But when I write a test project in C, after the compiling and linking,
> the output file can't be downloaded to DSP completely, and it can't run!
> Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the
> other code are missing!! They are not downloaded to the corresponding
> address in DSP.
> > I can't understand it. I checked the project in C carefully, especiall
> all the build options, and I think I don't make a mistake.
> > I am doubt that whether the driver of 510 emulator is not correct?
>
> The XDS510 has no idea about how the '.out' file was generated. Your
> probably have a problem with your C project linker command file. If
> you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
> DOS prompt in the directory that contains the out file. [you will need
> a path to 'C:\\C6000\cgtools\bin']. This will
> analyze your '.out' file.
>
> mikedunn
> > or there are some mistakes I make which I don't know?
> > Are there someone meet the same problem? Or someone can give me some
> suggestion to solve it? THANKS!
> >
> > luckeybird
>
> --
> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>
>
>
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Reply by ●December 12, 20072007-12-12
Michael Dunn:
Thanks for your help!
Problems have been solved. There is a bug in CCS3.3 . The emulator provider helps me to replace some files and then all works well now.
Thanks!
luckeybird
Michael Dunn д
luckeybird,
On 12/10/07, luck wrote: mikedunn:
Thanks for your suggestion!
I use the ofd6x to analysis .out file. It displays all the section information and symble table,some like the information gived by .map file. But I can't find a obviously mistake.
I compare the two analysis results of ASM and C project. I think the results are similar and right, or maybe I don't know which is wrong.
Have you verified that all addresses are fir internal memory??
0x10000000 - 0x1003FFFF.
mikedunn
luckeybird
Michael Dunn д
luckeybird,
On Dec 10, 2007 9:12 AM, luck wrote:
> hi all:
> I meet a strange problem on 510usb emulator.
> Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb emulator.(4) program are all located in internal RAM
> I write a test project in ASM. After the compiling and linking, the output file can be downloaded to DSP(C6727B), and it runs well.
> But when I write a test project in C, after the compiling and linking, the output file can't be downloaded to DSP completely, and it can't run! Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the other code are missing!! They are not downloaded to the corresponding address in DSP.
> I can't understand it. I checked the project in C carefully, especiall all the build options, and I think I don't make a mistake.
> I am doubt that whether the driver of 510 emulator is not correct?
The XDS510 has no idea about how the '.out' file was generated. Your
probably have a problem with your C project linker command file. If
you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
DOS prompt in the directory that contains the out file. [you will need
a path to 'C:\\C6000\cgtools\bin']. This will
analyze your '.out' file.
mikedunn
> or there are some mistakes I make which I don't know?
> Are there someone meet the same problem? Or someone can give me some suggestion to solve it? THANKS!
>
> luckeybird
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Thanks for your help!
Problems have been solved. There is a bug in CCS3.3 . The emulator provider helps me to replace some files and then all works well now.
Thanks!
luckeybird
Michael Dunn д
luckeybird,
On 12/10/07, luck wrote: mikedunn:
Thanks for your suggestion!
I use the ofd6x to analysis .out file. It displays all the section information and symble table,some like the information gived by .map file. But I can't find a obviously mistake.
I compare the two analysis results of ASM and C project. I think the results are similar and right, or maybe I don't know which is wrong.
Have you verified that all addresses are fir internal memory??
0x10000000 - 0x1003FFFF.
mikedunn
luckeybird
Michael Dunn д
luckeybird,
On Dec 10, 2007 9:12 AM, luck wrote:
> hi all:
> I meet a strange problem on 510usb emulator.
> Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb emulator.(4) program are all located in internal RAM
> I write a test project in ASM. After the compiling and linking, the output file can be downloaded to DSP(C6727B), and it runs well.
> But when I write a test project in C, after the compiling and linking, the output file can't be downloaded to DSP completely, and it can't run! Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the other code are missing!! They are not downloaded to the corresponding address in DSP.
> I can't understand it. I checked the project in C carefully, especiall all the build options, and I think I don't make a mistake.
> I am doubt that whether the driver of 510 emulator is not correct?
The XDS510 has no idea about how the '.out' file was generated. Your
probably have a problem with your C project linker command file. If
you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
DOS prompt in the directory that contains the out file. [you will need
a path to 'C:\\C6000\cgtools\bin']. This will
analyze your '.out' file.
mikedunn
> or there are some mistakes I make which I don't know?
> Are there someone meet the same problem? Or someone can give me some suggestion to solve it? THANKS!
>
> luckeybird
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Reply by ●December 12, 20072007-12-12
mikedunn:
Thanks for your suggestion!
I use the ofd6x to analysis .out file. It displays all the section information and symble table,some like the information gived by .map file. But I can't find a obviously mistake.
I compare the two analysis results of ASM and C project. I think the results are similar and right, or maybe I don't know which is wrong.
luckeybird
Michael Dunn д
luckeybird,
On Dec 10, 2007 9:12 AM, luck wrote:
> hi all:
> I meet a strange problem on 510usb emulator.
> Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb emulator.(4) program are all located in internal RAM
> I write a test project in ASM. After the compiling and linking, the output file can be downloaded to DSP(C6727B), and it runs well.
> But when I write a test project in C, after the compiling and linking, the output file can't be downloaded to DSP completely, and it can't run! Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the other code are missing!! They are not downloaded to the corresponding address in DSP.
> I can't understand it. I checked the project in C carefully, especiall all the build options, and I think I don't make a mistake.
> I am doubt that whether the driver of 510 emulator is not correct?
The XDS510 has no idea about how the '.out' file was generated. Your
probably have a problem with your C project linker command file. If
you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
DOS prompt in the directory that contains the out file. [you will need
a path to 'C:\\C6000\cgtools\bin']. This will
analyze your '.out' file.
mikedunn
> or there are some mistakes I make which I don't know?
> Are there someone meet the same problem? Or someone can give me some suggestion to solve it? THANKS!
>
> luckeybird
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Thanks for your suggestion!
I use the ofd6x to analysis .out file. It displays all the section information and symble table,some like the information gived by .map file. But I can't find a obviously mistake.
I compare the two analysis results of ASM and C project. I think the results are similar and right, or maybe I don't know which is wrong.
luckeybird
Michael Dunn д
luckeybird,
On Dec 10, 2007 9:12 AM, luck wrote:
> hi all:
> I meet a strange problem on 510usb emulator.
> Environment: (1)DSP C6727B, (2)CCS v3.3 , (3)emulator: 510usb emulator.(4) program are all located in internal RAM
> I write a test project in ASM. After the compiling and linking, the output file can be downloaded to DSP(C6727B), and it runs well.
> But when I write a test project in C, after the compiling and linking, the output file can't be downloaded to DSP completely, and it can't run! Typically, only the first 4-bytes can be downloaded to DSP by JTAG, and the other code are missing!! They are not downloaded to the corresponding address in DSP.
> I can't understand it. I checked the project in C carefully, especiall all the build options, and I think I don't make a mistake.
> I am doubt that whether the driver of 510 emulator is not correct?
The XDS510 has no idea about how the '.out' file was generated. Your
probably have a problem with your C project linker command file. If
you do notsee the problem, you can run 'ofd6x yourOutFileName' from a
DOS prompt in the directory that contains the out file. [you will need
a path to 'C:\\C6000\cgtools\bin']. This will
analyze your '.out' file.
mikedunn
> or there are some mistakes I make which I don't know?
> Are there someone meet the same problem? Or someone can give me some suggestion to solve it? THANKS!
>
> luckeybird
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
