|
ok I have given up on trying to debug with tasking (just found out we need to spend an additional 2000 (on top of the 3000 for the compiler) in order to be able to debug damm!!!!! Anyway, I am trying to get my head around the using the Suite56 tools (or any other free source level tools) in order to debug my target. What I have is the tools installed(I think), a wiggler, and my DS56303 target. Can anybody point me in a direction (preferably the right one), that would enable me to connect all these together, and be able to debug my system. I have tried many things but alas to no avail. Any a pointer to any useful documentation (other than the standard stuff that motorola have - none of which seems to point to this case). Cheers, Scott. |
|
|
Suite56, Wiggler, JTag, Documentation????
Started by ●October 15, 2003
Reply by ●October 15, 20032003-10-15
|
Moin, You seem to have everything you need to debug your DSP Code, in case your wiggler is the "Suite56 Parallel Command Converter", works fine here in the castle. Unfortunately your description of the problem lacks a certain accuracy, so I suggest to do the following: -connect Wiggler to your Hardware, make sure Hardware engineer connected pins properly. -start the "Command Converter Server", make sure it is configured properly, wiggler on LPT1 etc. -power up Hardware -start "GDS56300", it should find your hardware, just reset and trace DSP step by step and see how it executes the internal bootstrap code. This is a good way of telling if the DSP is alive at all, you can see if it chooses the right booting method and you don't have to load any code. ukkiwikid wrote: > ok I have given up on trying to debug with tasking (just found out we > need to spend an additional 2000 (on top of the 3000 for the > compiler) in order to be able to debug damm!!!!! The price seemed too high for me lately, especially because it includes just a single license for the compiler. Reading that you have to pay extra for some debugging facility is really poor style and I do not regret not having bought the compiler. Stefan > Anyway, I am trying to get my head around the using the Suite56 tools > (or any other free source level tools) in order to debug my target. > > What I have is the tools installed(I think), a wiggler, and my > DS56303 target. Can anybody point me in a direction (preferably the > right one), that would enable me to connect all these together, and > be able to debug my system. I have tried many things but alas to no > avail. > > Any a pointer to any useful documentation (other than the standard > stuff that motorola have - none of which seems to point to this case). > > Cheers, > > Scott. > |
Reply by ●October 15, 20032003-10-15
|
Is your target PCB custom, or a Motorola EVM? If it's custom, you have to get the wiring to the JTAG header just right and you need to OR both JTAG pin 9 and 56311 TRST/ with a power up reset. This point is somewhat obscure in the Mot literature. Another point: the internal boot ROM will only load code and data into P: space, so if you have X or Y data assignments in your source, they won't be handled correctly. If you're using an EVM, be sure that the JTAG/CC converter option header has (or does not have) a shunt in place. It should be set to disable the on board Command Converter and select the external wiggler attached to the JTAG port. There was a problem with the rev level of the Tools package whereby a DLL called (I think) windriver.dll was out of date with the one required by CCS or the Debugger. I finally got the tools to work with both the EVM56311 and a custom PCB that I designed and the system seems solid. Best, Chris On Wed, 15 Oct 2003 15:28:36 -0000, ukkiwikid wrote: ok I have given up on trying to debug with tasking (just found out we need to spend an additional 2000 (on top of the 3000 for the compiler) in order to be able to debug damm!!!!! Anyway, I am trying to get my head around the using the Suite56 tools (or any other free source level tools) in order to debug my target. What I have is the tools installed(I think), a wiggler, and my DS56303 target. Can anybody point me in a direction (preferably the right one), that would enable me to connect all these together, and be able to debug my system. I have tried many things but alas to no avail. Any a pointer to any useful documentation (other than the standard stuff that motorola have - none of which seems to point to this case). Cheers, Scott. ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cidU11 http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/PNArlB/TM ---------------------------------~ -> _____________________________________ Note: If you do a simple "reply" with your email client, only the author of this message will receive your answer. You need to do a "reply all" if you want your answer to be distributed to the entire group. _____________________________________ About this discussion group: To Join: To Post: To Leave: Archives: http://www.yahoogroups.com/group/motoroladsp More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/ ----------------------------------- Seven Woods Audio, Inc. Christopher Moore Concepts, Products, Circuits for Audio Analog/Digital http://www.SevenWoodsAudio.com |
|
|
Reply by ●October 16, 20032003-10-16
|
Yahooooo, I am connected and debugging. Thanks everybody However I cant get the source file loaded into the GDS56300. When I open the source window after loading the COFF file it has the following no_source_file pc=@0 pi:$6 <no_label> section:global Any thoughts? Cheers Scott. --- In , Christopher Moore <moore@s...> wrote: > Is your target PCB custom, or a Motorola EVM? If it's custom, you > have to get the wiring to the JTAG header just right and you need to > OR both JTAG pin 9 and 56311 TRST/ with a power up reset. This point > is somewhat obscure in the Mot literature. > > Another point: the internal boot ROM will only load code and data > into P: space, so if you have X or Y data assignments in your source, > they won't be handled correctly. > > If you're using an EVM, be sure that the JTAG/CC converter option > header has (or does not have) a shunt in place. It should be set to > disable the on board Command Converter and select the external > wiggler attached to the JTAG port. > > There was a problem with the rev level of the Tools package whereby a > DLL called (I think) windriver.dll was out of date with the one > required by CCS or the Debugger. > > I finally got the tools to work with both the EVM56311 and a custom > PCB that I designed and the system seems solid. > > Best, > > Chris > On Wed, 15 Oct 2003 15:28:36 -0000, ukkiwikid wrote: > ok I have given up on trying to debug with tasking (just found out we > need to spend an additional 2000 (on top of the 3000 for the > compiler) in order to be able to debug damm!!!!! > > Anyway, I am trying to get my head around the using the Suite56 tools > (or any other free source level tools) in order to debug my target. > > What I have is the tools installed(I think), a wiggler, and my > DS56303 target. Can anybody point me in a direction (preferably the > right one), that would enable me to connect all these together, and > be able to debug my system. I have tried many things but alas to no > avail. > > Any a pointer to any useful documentation (other than the standard > stuff that motorola have - none of which seems to point to this > case). > > Cheers, > > Scott. > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or > Lexmark > Printer at MyInks.com. Free s/h on orders $50 or more to the US > & Canada. > http://www.c1tracking.com/l.asp?cidU11 > http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/PNArlB/TM > -------------------------------- -~ > -> > > _____________________________________ > Note: If you do a simple "reply" with your email client, only the > author of this message will receive your answer. You need to do a > "reply all" if you want your answer to be distributed to the entire > group. > > _____________________________________ > About this discussion group: > > To Join: > > To Post: > > To Leave: > > Archives: http://www.yahoogroups.com/group/motoroladsp > > More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/ > > -------------------------------- --- > Seven Woods Audio, Inc. Christopher Moore > Concepts, Products, Circuits for Audio Analog/Digital > moore@S... > http://www.SevenWoodsAudio.com |
|
|
Reply by ●October 16, 20032003-10-16
|
Do you have the paths set properly in the debugger??? -- dB --- ukkiwikid <> wrote: > Yahooooo, I am connected and debugging. Thanks everybody However I > cant get the source file loaded into the GDS56300. > > When I open the source window after loading the COFF file it has the > following > no_source_file pc=@0 pi:$6 <no_label> section:global > > Any thoughts? > > Cheers > > Scott. > --- In , Christopher Moore <moore@s...> > wrote: > > Is your target PCB custom, or a Motorola EVM? If it's custom, you > > have to get the wiring to the JTAG header just right and you need > to > > OR both JTAG pin 9 and 56311 TRST/ with a power up reset. This > point > > is somewhat obscure in the Mot literature. > > > > Another point: the internal boot ROM will only load code and data > > into P: space, so if you have X or Y data assignments in your > source, > > they won't be handled correctly. > > > > If you're using an EVM, be sure that the JTAG/CC converter option > > header has (or does not have) a shunt in place. It should be set to > > > disable the on board Command Converter and select the external > > wiggler attached to the JTAG port. > > > > There was a problem with the rev level of the Tools package whereby > > a > > DLL called (I think) windriver.dll was out of date with the one > > required by CCS or the Debugger. > > > > I finally got the tools to work with both the EVM56311 and a custom > > > PCB that I designed and the system seems solid. > > > > Best, > > > > Chris > > > > > > On Wed, 15 Oct 2003 15:28:36 -0000, ukkiwikid wrote: > > ok I have given up on trying to debug with tasking (just found out > we > > need to spend an additional 2000 (on top of the 3000 for the > > compiler) in order to be able to debug damm!!!!! > > > > Anyway, I am trying to get my head around the using the Suite56 > tools > > (or any other free source level tools) in order to debug my target. > > > > What I have is the tools installed(I think), a wiggler, and my > > DS56303 target. Can anybody point me in a direction (preferably > the > > right one), that would enable me to connect all these together, and > > be able to debug my system. I have tried many things but alas to > no > > avail. > > > > Any a pointer to any useful documentation (other than the standard > > stuff that motorola have - none of which seems to point to this > > case). > > > > Cheers, > > > > Scott. > > > > > > ------------------------ Yahoo! Groups Sponsor > > ---------------------~--> > > Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or > > Lexmark > > Printer at MyInks.com. Free s/h on orders $50 or more to the US > > & Canada. > > http://www.c1tracking.com/l.asp?cidU11 > > http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/PNArlB/TM > > > -------------------------------- > -~ > > -> > > > > _____________________________________ > > Note: If you do a simple "reply" with your email client, only the > > author of this message will receive your answer. You need to do a > > "reply all" if you want your answer to be distributed to the entire > > > group. > > > > _____________________________________ > > About this discussion group: > > > > To Join: > > > > To Post: > > > > To Leave: > > > > Archives: http://www.yahoogroups.com/group/motoroladsp > > > > More Groups: http://www.dsprelated.com/groups.php3 > > > > > > ">http://docs.yahoo.com/info/terms/ > > > > > > > > > -------------------------------- > --- > > Seven Woods Audio, Inc. Christopher Moore > > Concepts, Products, Circuits for Audio Analog/Digital > > moore@S... > > http://www.SevenWoodsAudio.com __________________________________ |
|
|
Reply by ●October 16, 20032003-10-16
|
If the source is from a Tasking project, something special needs to be done in Tasking to generate the Motorola symbolic info in the .cld file so the Suite debugger can find and use the source. Don't ask what that is; you need to ask Tasking. (I've never personally used Tasking, but I know the option for Moto debugging exists) --david --- In , dbaudiopro <dbaudiopro@y...> wrote: > Do you have the paths set properly in the debugger??? > > -- > dB > > --- ukkiwikid <burke_scott@h...> wrote: > > Yahooooo, I am connected and debugging. Thanks everybody However I > > cant get the source file loaded into the GDS56300. > > > > When I open the source window after loading the COFF file it has the > > following > > no_source_file pc=@0 pi:$6 <no_label> section:global > > > > Any thoughts? > > > > Cheers > > > > Scott. > > > > > > --- In , Christopher Moore <moore@s...> > > wrote: > > > Is your target PCB custom, or a Motorola EVM? If it's custom, you > > > have to get the wiring to the JTAG header just right and you need > > to > > > OR both JTAG pin 9 and 56311 TRST/ with a power up reset. This > > point > > > is somewhat obscure in the Mot literature. > > > > > > Another point: the internal boot ROM will only load code and data > > > into P: space, so if you have X or Y data assignments in your > > source, > > > they won't be handled correctly. > > > > > > If you're using an EVM, be sure that the JTAG/CC converter option > > > header has (or does not have) a shunt in place. It should be set to > > > > > disable the on board Command Converter and select the external > > > wiggler attached to the JTAG port. > > > > > > There was a problem with the rev level of the Tools package whereby > > > > a > > > DLL called (I think) windriver.dll was out of date with the one > > > required by CCS or the Debugger. > > > > > > I finally got the tools to work with both the EVM56311 and a custom > > > > > PCB that I designed and the system seems solid. > > > > > > Best, > > > > > > Chris > > > > > > > > > On Wed, 15 Oct 2003 15:28:36 -0000, ukkiwikid wrote: > > > ok I have given up on trying to debug with tasking (just found out > > we > > > need to spend an additional 2000 (on top of the 3000 for the > > > compiler) in order to be able to debug damm!!!!! > > > > > > Anyway, I am trying to get my head around the using the Suite56 > > tools > > > (or any other free source level tools) in order to debug my target. > > > > > > What I have is the tools installed(I think), a wiggler, and my > > > DS56303 target. Can anybody point me in a direction (preferably > > the > > > right one), that would enable me to connect all these together, and > > > be able to debug my system. I have tried many things but alas to > > no > > > avail. > > > > > > Any a pointer to any useful documentation (other than the standard > > > stuff that motorola have - none of which seems to point to this > > > case). > > > > > > Cheers, > > > > > > Scott. > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > ---------------------~--> > > > Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or > > > Lexmark > > > Printer at MyInks.com. Free s/h on orders $50 or more to the US > > > & Canada. > > > http://www.c1tracking.com/l.asp?cidU11 > > > http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/PNArlB/TM > > > > > -------------------------------- > > -~ > > > -> > > > > > > _____________________________________ > > > Note: If you do a simple "reply" with your email client, only the > > > author of this message will receive your answer. You need to do a > > > "reply all" if you want your answer to be distributed to the entire > > > > > group. > > > > > > _____________________________________ > > > About this discussion group: > > > > > > To Join: > > > > > > To Post: > > > > > > To Leave: > > > > > > Archives: http://www.yahoogroups.com/group/motoroladsp > > > > > > More Groups: http://www.dsprelated.com/groups.php3 > > > > > > > > > ">http://docs.yahoo.com/info/terms/ > > > > > > > > > > > > > > -------------------------------- > > --- > > > Seven Woods Audio, Inc. Christopher Moore > > > Concepts, Products, Circuits for Audio Analog/Digital > > > moore@S... > > > http://www.SevenWoodsAudio.com > > > > __________________________________ > |
