topic Re: bootloader or my own failure (?) can someone help ?? in Classic/Legacy CodeWarrior

bootloader or my own failure (?) can someone help ??

stefat — Sun, 04 Feb 2007 07:47:30 GMT

Hello,
I am using CW for DSC56800/E version 8.0 targeting an 56F801A60 cpu on the 56F800DEMO board.
Problem story as follows:
build and download bootloader ver 1.3
disinstall jumper JP1 to disconnect JTAG i/f. Run bootloader after reset: it works fine and I see its prompt(s) on serial i/f
download S-record text file of my generated application (build option in PE cpu bean 'Serial download support':yes; boot start delay:3) using hyperterminal. It works and at the end I see the bootloader prompt 'Application started'. My application runs. I am HAPPY.
I expect now on next hw reset (pushbutton on demo board) to see the prompt of bootloader in hyperteminal screen and after the programmed 3s my application running again: NOTHING HAPPENS and bootloader remains in control. I am then UNHAPPY now !
Checked my application memory (using CW debug): entry point of application is at 0x0086; at 0x0080 there is the jsr 0x0086; 0x0085 contains 0003 - boot start delay. See please attached memory dump.
Everything seems to me ok...but it is obviously not: is there something missing or what maybe wrong ??

Is there someone who can help ?

Thanks

Stefat

Re: bootloader or my own failure (?) can someone help ??

stefat — Mon, 05 Feb 2007 20:17:41 GMT

Hi guys (if any)

I found a BUG in bootloader ver 1.3. as received in the CW doc-s.

In file bootloader.c I changed the following row:

comInit(((TmpXdataVar ^ 0xfe00) & 0xff00) ? 0x00ff : TmpXdataVar & 0x00ff);
// CHANGED TO
comInit(((TmpXdataVar ^ 0xfe00) & 0xff00) ? TmpXdataVar & 0x00ff : 0x00ff);

and now the bootloader works fine and waits for the programmed delay at address 0x0085

regards

stefat

Re: bootloader or my own failure (?) can someone help ??

CrasyCat — Mon, 05 Feb 2007 21:40:57 GMT

Hello

I am afraid you need to submit a service request for that.

To log the issue with Freescale please go to following URL:
http://www.freescale.com/webapp/sps/site/homepage.jsp?nodeId=054670&tid=FSH
and click on "Submit a service request"

CrasyCat

Re: bootloader or my own failure (?) can someone help ??

stefat — Mon, 05 Feb 2007 22:09:42 GMT

thank you.

I anyway found the way to overcome the problem and I am asking using the service request for confirmation of that.

Regards

Stefat

Re: bootloader or my own failure (?) can someone help ??

DrJoe047 — Sat, 05 Apr 2008 03:36:30 GMT

I am having a somewhat similar experience.

I compiled the bootloader example (basically my only change to the project is to use PE to select my processor, specifically the 56F805) and downloaded it to the '805 using a jtag adaptor.(I am not using the EVM board but my own custom PCB) All is well.

Then I re-compile my application code (which runs just fine if I download it to the DSP using the jtag adaptor) only now with the bootloader support option checked in the PE processor bean.

I download the this file "internal_xROM-xRAM.elf.x.S" (generated by Codewarrior once I have all the right boxes checked according to the confusing and incomplete bootloader manual).

This is what I see

(c) 2004 Freescale Inc. S-Record loader. Version 1.3

Loaded 0x0066 Program and 0x0000 Data words.
Application started.
ø <<NOTE 2 non-printable chactaters.
(c) 2004 Freescale Inc. S-Record loader. Version 1.3

Notice that it says that the application is started, but then in prints 2 non-printable characters and then the bootloader prints its intro again. No joy.

Please help if you can.

I have 2 more questions while I at it.

My reason for trying this is that I want to be able to update my application in the field. I will have a slow and somewhat unreliable radio link. The radio is too slow and has too many hiccups and gaps in the data to go right to the bootloader, but, with patience I can get the entire file accross the radio link and I have an intermediate processor that can potentially send the data on to the bootloader. My problem is that the intermediate processor has two issues.

#1, it does not support XON/XOFF
#2, the best case data rate it will be able to manage sending the file to the bootloader is something like 1500 bytes per second.

Here are my quiestions:
#1 at this data rate, witll the bootloader even work or will I have to customize the bootloader somehow (hints as to what "somehow" would be are welcome).
#2, assuming that it will work, will the slow data rate effectly allow me to ignore the XON/XOFF signals? (I may be able to get the radio source to write some custom firmware that implements the XON/XOFF flow control, but I don't want to pay for something I don't need anyway).

Please help.

Joe J.
--
Joseph M. Johnson, Ph.D., P.E.
Chief Technologist, Co-Founder
Robotic Amusements, Inc