Reply by Kyungtae Lee January 25, 20052005-01-25

Hi,

I resolved my problem at last. ^^ Thanks for your last interest.

My problem was that I didn't put the main clock, BCLKR between DSP reset and
the first data transmission. When I put some clocks before transmitting the
first frame sync(BFSR), my DSP booted well. Anyway, if you encounter the
similar problem at standard serial boot, try to put some main clocks before
data transmission.

Thanks,
KT Lee. ----- Original Message -----
From: "Kyungtae Lee" <>
To: <>; "Dileepan C" <>
Sent: Monday, January 24, 2005 11:06 PM
Subject: Re: [c54x] Standard Serial Boot

Hi,

Yes, I have used the option -v548. As I know on, the -memwidth value is 16
be default. And I'm sure because I saw the memwidth was 16 in the .map file
which was generated by hex500.exe.

The way I think I can sure that DSP boots well is to see the CLKOUT pin by
oscilloscope. Initially, the DSP runs at the half clock frequency of CLKIN
feeded by an oscillator, but it will run at the specified clock frequency
set by my code after successful boot. Right?

One thing, is there any way I can check the boot process step by step? For
example, the way I can confirm that the data is transfered after the host
transmits the one word via serial port interface, with CCS and so on..

Thanks,
KT ----- Original Message -----
From: "Dileepan C" <>
To: "Kyungtae Lee" <>; <>
Sent: Monday, January 24, 2005 9:54 PM
Subject: Re: [c54x] Standard Serial Boot
hi,

1) have you used the option -v548 while assembling the
code? if not, put it and create the out file and then
generate the hex file.

2) use option -memwidth 16 also.

3) what is your clocksource for the mcbsp of the dsp?
is that generating the clocks/signals correctly? and
what exactly is your application supposed to do in
case if it boots correctly? i mean, how are you making
sure that dsp boots/not booting etc?

regards,
Dileepan.

--- Kyungtae Lee <> wrote:

> Dear Dileepan,
>
> At first, thanks for your reply.
>
> About XF pin, the culprit may be a BIO pin. Because
> it is low, the boot mode
> went to the IO boot and return to the intial state
> of boot loader for
> invalid keyword. Anyway, the XF pin goes to low and
> boot mode seems to be
> Standard serial port boot mode now.
>
> But I cannot succeed to boot the DSP yet. Although I
> checked the BCLKR, BFSR
> and BDR and they look correct, the DSP didn't
> generate the CLKOUT which was
> supposed to be made by my code. So, I hope to ask
> some questions about it.
>
> Below is my .cmd file for hex500.exe.
> -----
> OnePhone_DSP_1chip.out
>
> -e _c_int00
> -a
> -map hex.map
> -boot
> -bootorg SERIAL
> -romwidth 16
> -o OnePhone_DSP_1chip.hex
> -----
> After making a hex file, I edited it properly and
> made an array include the
> hexa info. The contents of the array are same as
> described in the TI
> documents. That is, 0x10aa, four dummy words, entry
> point, etc.
>
> Is there any suspicious part in my .cmd file?
>
> Thank you in advance.
>
> Best Regards,
> KT Lee. >
> ----- Original Message -----
> From: "Dileepan C" <>
> To: "kt_rhee" <>;
> <>
> Sent: Monday, January 24, 2005 5:59 PM
> Subject: Re: [c54x] Standard Serial Boot > Please check the following:
>
> 1) ensure that you have built the boottable
> correctly.
> ensure that you have used the correct options.
>
> 2) ensure that MP/MC pin is provided with a logic 0.
>
> 3)yes, XF pin should go low at the start of the
> bootloading and will remain low during the entire
> duration of boot process.
>
> 4) ensure that the external clock you are providing
> is
> not exceeding half the CPU clock.also a minimum
> delay
> of 40 CPU clocks should be provided between the
> transmission of each word.
>
> 5) ensure that dsp is getting sufficient power.
>
> regards,
> Dileepan.
> --- kt_rhee <> wrote:
>
> >
> >
> >
> > Hello all,
> >
> > I'm trying to boot the DSP with standard serial
> boot
> > mode via McBSP0
> > (16bit). According to the TI document,
> > spra618b(Title
> > is "TMS320VC5402 and TMS320U5402 Bootloader."), I
> > expected the XF
> > pin go to the low after checking HPI boot mode,
> > serial EEPROM boot
> > mode and parallel boot mode to indicate the DSP's
> > ready to receive
> > data by serial port. But it didn't. So, DSP didn't
> > boot well.
> >
> > Of course, /INT2 and /INT3 is not active to
> prevent
> > from going to
> > the HPI boot mode and serial EEPROM boot mode.
> > Furthermore, the
> > contents of FFFFh of I/O and data space cannot be
> > the valid word for
> > the parallel boot mode. So, I'm confused with it.
> >
> > Is there anybody experience the serial boot via
> > McBSP? Does not XF
> > pin go to low? Or does it go to low for just a
> > moment and return to
> > high?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> __________________________________ >

__________________________________



Reply by Kyungtae Lee January 24, 20052005-01-24

Hi,

Yes, I have used the option -v548. As I know on, the -memwidth value is 16
be default. And I'm sure because I saw the memwidth was 16 in the .map file
which was generated by hex500.exe.

The way I think I can sure that DSP boots well is to see the CLKOUT pin by
oscilloscope. Initially, the DSP runs at the half clock frequency of CLKIN
feeded by an oscillator, but it will run at the specified clock frequency
set by my code after successful boot. Right?

One thing, is there any way I can check the boot process step by step? For
example, the way I can confirm that the data is transfered after the host
transmits the one word via serial port interface, with CCS and so on..

Thanks,
KT ----- Original Message -----
From: "Dileepan C" <>
To: "Kyungtae Lee" <>; <>
Sent: Monday, January 24, 2005 9:54 PM
Subject: Re: [c54x] Standard Serial Boot
hi,

1) have you used the option -v548 while assembling the
code? if not, put it and create the out file and then
generate the hex file.

2) use option -memwidth 16 also.

3) what is your clocksource for the mcbsp of the dsp?
is that generating the clocks/signals correctly? and
what exactly is your application supposed to do in
case if it boots correctly? i mean, how are you making
sure that dsp boots/not booting etc?

regards,
Dileepan.

--- Kyungtae Lee <> wrote:

> Dear Dileepan,
>
> At first, thanks for your reply.
>
> About XF pin, the culprit may be a BIO pin. Because
> it is low, the boot mode
> went to the IO boot and return to the intial state
> of boot loader for
> invalid keyword. Anyway, the XF pin goes to low and
> boot mode seems to be
> Standard serial port boot mode now.
>
> But I cannot succeed to boot the DSP yet. Although I
> checked the BCLKR, BFSR
> and BDR and they look correct, the DSP didn't
> generate the CLKOUT which was
> supposed to be made by my code. So, I hope to ask
> some questions about it.
>
> Below is my .cmd file for hex500.exe.
> -----
> OnePhone_DSP_1chip.out
>
> -e _c_int00
> -a
> -map hex.map
> -boot
> -bootorg SERIAL
> -romwidth 16
> -o OnePhone_DSP_1chip.hex
> -----
> After making a hex file, I edited it properly and
> made an array include the
> hexa info. The contents of the array are same as
> described in the TI
> documents. That is, 0x10aa, four dummy words, entry
> point, etc.
>
> Is there any suspicious part in my .cmd file?
>
> Thank you in advance.
>
> Best Regards,
> KT Lee. >
> ----- Original Message -----
> From: "Dileepan C" <>
> To: "kt_rhee" <>;
> <>
> Sent: Monday, January 24, 2005 5:59 PM
> Subject: Re: [c54x] Standard Serial Boot > Please check the following:
>
> 1) ensure that you have built the boottable
> correctly.
> ensure that you have used the correct options.
>
> 2) ensure that MP/MC pin is provided with a logic 0.
>
> 3)yes, XF pin should go low at the start of the
> bootloading and will remain low during the entire
> duration of boot process.
>
> 4) ensure that the external clock you are providing
> is
> not exceeding half the CPU clock.also a minimum
> delay
> of 40 CPU clocks should be provided between the
> transmission of each word.
>
> 5) ensure that dsp is getting sufficient power.
>
> regards,
> Dileepan.
> --- kt_rhee <> wrote:
>
> >
> >
> >
> > Hello all,
> >
> > I'm trying to boot the DSP with standard serial
> boot
> > mode via McBSP0
> > (16bit). According to the TI document,
> > spra618b(Title
> > is "TMS320VC5402 and TMS320U5402 Bootloader."), I
> > expected the XF
> > pin go to the low after checking HPI boot mode,
> > serial EEPROM boot
> > mode and parallel boot mode to indicate the DSP's
> > ready to receive
> > data by serial port. But it didn't. So, DSP didn't
> > boot well.
> >
> > Of course, /INT2 and /INT3 is not active to
> prevent
> > from going to
> > the HPI boot mode and serial EEPROM boot mode.
> > Furthermore, the
> > contents of FFFFh of I/O and data space cannot be
> > the valid word for
> > the parallel boot mode. So, I'm confused with it.
> >
> > Is there anybody experience the serial boot via
> > McBSP? Does not XF
> > pin go to low? Or does it go to low for just a
> > moment and return to
> > high?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> __________________________________ >

__________________________________



Reply by Dileepan C January 24, 20052005-01-24
hi,

1) have you used the option -v548 while assembling the
code? if not, put it and create the out file and then
generate the hex file.

2) use option -memwidth 16 also.

3) what is your clocksource for the mcbsp of the dsp?
is that generating the clocks/signals correctly? and
what exactly is your application supposed to do in
case if it boots correctly? i mean, how are you making
sure that dsp boots/not booting etc?

regards,
Dileepan.

--- Kyungtae Lee <> wrote:

> Dear Dileepan,
>
> At first, thanks for your reply.
>
> About XF pin, the culprit may be a BIO pin. Because
> it is low, the boot mode
> went to the IO boot and return to the intial state
> of boot loader for
> invalid keyword. Anyway, the XF pin goes to low and
> boot mode seems to be
> Standard serial port boot mode now.
>
> But I cannot succeed to boot the DSP yet. Although I
> checked the BCLKR, BFSR
> and BDR and they look correct, the DSP didn't
> generate the CLKOUT which was
> supposed to be made by my code. So, I hope to ask
> some questions about it.
>
> Below is my .cmd file for hex500.exe.
> -----
> OnePhone_DSP_1chip.out
>
> -e _c_int00
> -a
> -map hex.map
> -boot
> -bootorg SERIAL
> -romwidth 16
> -o OnePhone_DSP_1chip.hex
> -----
> After making a hex file, I edited it properly and
> made an array include the
> hexa info. The contents of the array are same as
> described in the TI
> documents. That is, 0x10aa, four dummy words, entry
> point, etc.
>
> Is there any suspicious part in my .cmd file?
>
> Thank you in advance.
>
> Best Regards,
> KT Lee. >
> ----- Original Message -----
> From: "Dileepan C" <>
> To: "kt_rhee" <>;
> <>
> Sent: Monday, January 24, 2005 5:59 PM
> Subject: Re: [c54x] Standard Serial Boot > Please check the following:
>
> 1) ensure that you have built the boottable
> correctly.
> ensure that you have used the correct options.
>
> 2) ensure that MP/MC pin is provided with a logic 0.
>
> 3)yes, XF pin should go low at the start of the
> bootloading and will remain low during the entire
> duration of boot process.
>
> 4) ensure that the external clock you are providing
> is
> not exceeding half the CPU clock.also a minimum
> delay
> of 40 CPU clocks should be provided between the
> transmission of each word.
>
> 5) ensure that dsp is getting sufficient power.
>
> regards,
> Dileepan.
> --- kt_rhee <> wrote:
>
> >
> >
> >
> > Hello all,
> >
> > I'm trying to boot the DSP with standard serial
> boot
> > mode via McBSP0
> > (16bit). According to the TI document,
> > spra618b(Title
> > is "TMS320VC5402 and TMS320U5402 Bootloader."), I
> > expected the XF
> > pin go to the low after checking HPI boot mode,
> > serial EEPROM boot
> > mode and parallel boot mode to indicate the DSP's
> > ready to receive
> > data by serial port. But it didn't. So, DSP didn't
> > boot well.
> >
> > Of course, /INT2 and /INT3 is not active to
> prevent
> > from going to
> > the HPI boot mode and serial EEPROM boot mode.
> > Furthermore, the
> > contents of FFFFh of I/O and data space cannot be
> > the valid word for
> > the parallel boot mode. So, I'm confused with it.
> >
> > Is there anybody experience the serial boot via
> > McBSP? Does not XF
> > pin go to low? Or does it go to low for just a
> > moment and return to
> > high?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> __________________________________ >

__________________________________



Reply by Kyungtae Lee January 24, 20052005-01-24

Dear Dileepan,

At first, thanks for your reply.

About XF pin, the culprit may be a BIO pin. Because it is low, the boot mode
went to the IO boot and return to the intial state of boot loader for
invalid keyword. Anyway, the XF pin goes to low and boot mode seems to be
Standard serial port boot mode now.

But I cannot succeed to boot the DSP yet. Although I checked the BCLKR, BFSR
and BDR and they look correct, the DSP didn't generate the CLKOUT which was
supposed to be made by my code. So, I hope to ask some questions about it.

Below is my .cmd file for hex500.exe.
-----
OnePhone_DSP_1chip.out

-e _c_int00
-a
-map hex.map
-boot
-bootorg SERIAL
-romwidth 16
-o OnePhone_DSP_1chip.hex
-----
After making a hex file, I edited it properly and made an array include the
hexa info. The contents of the array are same as described in the TI
documents. That is, 0x10aa, four dummy words, entry point, etc.

Is there any suspicious part in my .cmd file?

Thank you in advance.

Best Regards,
KT Lee.
----- Original Message -----
From: "Dileepan C" <>
To: "kt_rhee" <>; <>
Sent: Monday, January 24, 2005 5:59 PM
Subject: Re: [c54x] Standard Serial Boot Please check the following:

1) ensure that you have built the boottable correctly.
ensure that you have used the correct options.

2) ensure that MP/MC pin is provided with a logic 0.

3)yes, XF pin should go low at the start of the
bootloading and will remain low during the entire
duration of boot process.

4) ensure that the external clock you are providing is
not exceeding half the CPU clock.also a minimum delay
of 40 CPU clocks should be provided between the
transmission of each word.

5) ensure that dsp is getting sufficient power.

regards,
Dileepan.
--- kt_rhee <> wrote:

> Hello all,
>
> I'm trying to boot the DSP with standard serial boot
> mode via McBSP0
> (16bit). According to the TI document,
> spra618b(Title
> is "TMS320VC5402 and TMS320U5402 Bootloader."), I
> expected the XF
> pin go to the low after checking HPI boot mode,
> serial EEPROM boot
> mode and parallel boot mode to indicate the DSP's
> ready to receive
> data by serial port. But it didn't. So, DSP didn't
> boot well.
>
> Of course, /INT2 and /INT3 is not active to prevent
> from going to
> the HPI boot mode and serial EEPROM boot mode.
> Furthermore, the
> contents of FFFFh of I/O and data space cannot be
> the valid word for
> the parallel boot mode. So, I'm confused with it.
>
> Is there anybody experience the serial boot via
> McBSP? Does not XF
> pin go to low? Or does it go to low for just a
> moment and return to
> high? >

__________________________________


Reply by Dileepan C January 24, 20052005-01-24
Please check the following:

1) ensure that you have built the boottable correctly.
ensure that you have used the correct options.

2) ensure that MP/MC pin is provided with a logic 0.

3)yes, XF pin should go low at the start of the
bootloading and will remain low during the entire
duration of boot process.

4) ensure that the external clock you are providing is
not exceeding half the CPU clock.also a minimum delay
of 40 CPU clocks should be provided between the
transmission of each word.

5) ensure that dsp is getting sufficient power.

regards,
Dileepan.
--- kt_rhee <> wrote:

> Hello all,
>
> I'm trying to boot the DSP with standard serial boot
> mode via McBSP0
> (16bit). According to the TI document,
> spra618b(Title
> is "TMS320VC5402 and TMS320U5402 Bootloader."), I
> expected the XF
> pin go to the low after checking HPI boot mode,
> serial EEPROM boot
> mode and parallel boot mode to indicate the DSP's
> ready to receive
> data by serial port. But it didn't. So, DSP didn't
> boot well.
>
> Of course, /INT2 and /INT3 is not active to prevent
> from going to
> the HPI boot mode and serial EEPROM boot mode.
> Furthermore, the
> contents of FFFFh of I/O and data space cannot be
> the valid word for
> the parallel boot mode. So, I'm confused with it.
>
> Is there anybody experience the serial boot via
> McBSP? Does not XF
> pin go to low? Or does it go to low for just a
> moment and return to
> high? >

__________________________________



Reply by kt_rhee January 23, 20052005-01-23


Hello all,

I'm trying to boot the DSP with standard serial boot mode via McBSP0
(16bit). According to the TI document, spra618b(Title
is "TMS320VC5402 and TMS320U5402 Bootloader."), I expected the XF
pin go to the low after checking HPI boot mode, serial EEPROM boot
mode and parallel boot mode to indicate the DSP's ready to receive
data by serial port. But it didn't. So, DSP didn't boot well.

Of course, /INT2 and /INT3 is not active to prevent from going to
the HPI boot mode and serial EEPROM boot mode. Furthermore, the
contents of FFFFh of I/O and data space cannot be the valid word for
the parallel boot mode. So, I'm confused with it.

Is there anybody experience the serial boot via McBSP? Does not XF
pin go to low? Or does it go to low for just a moment and return to
high?