We use ARM7 MCU of LPC2368 series for the application. While programming the ARM7 MCU using Flash Magic Tool version 5.89.2405, we get the error as "Operation Failed.(failed to autobaud - Step1)".
We use 11.0592MHz oscillator to drive the Controller. While programming it does not shows the Com port to which the device has been connected when checked through the device manger of the control panel. While using Keil MicroVision3 IDE for downloading the program to controller, it works fine. But, for Flash Magic Tool, it shows autobaud error. We checked all other hardware connections, it was found to be correct.
Please suggest the suitable solution for this autobaud error problem. And also suggest the baudrate and Com port at which the controller is to be programmed using Flash Magic Tool
Regards, Saikiran R. Embedded Software Engineer LCS Controls Pvt Ltd, Chennai, India
We are using JTAG interface for programming. We also made try with RS232 interface through Com port, It also shows the same error "Operation Failed.(failed to autobaud - Step1)". We also tried with lower baud rates. It shows the same error. May I know what u mean by IRC frequency, CRP and let me know about its significance. How to enable or disable CRP? We checked the Com port using Com debug tool, Com port seems to be working. But it shows the above error while programming using flash magic tool.
"We are using JTAG interface for programming. We also made try with RS232 interface through Com port, It also shows the same error 'Operation Failed.(failed to autobaud - Step1)'."
Failed to autobaud is something you can get when RS232 transfers, since RS232 is asynchronous, i.e. the receiver is internally clocking the time between when it will poll for the different bits. Not so with JTAG transfers.
When you use Flash Magic, the boot loader doesn't know what baudrate you have. And it doesn't know what crystal you have connected to the processor.
So initially, the boot loader in the processor uses the internal RC oscillator (IRC) for running the processor, and uses the auto-baud feature to try to measure the bit lengths to figure out what baudrate the PC sends the commands with. Some batches of LPC23xx chips fails this autobaud step unless you change down to very low baudrates. In my case, I have had some processors requiring 19200 baud and some have required 9600 baud. Maybe there are processors that requires even lower baudrate for the autobaud to work.
If the boot loader do manage to auto-baud, then Flash Magic can report the crystal oscillator frequency to the boot loader (that is one of the input fields when configuring Flash Magic), and the boot loader can then switch to the crystal for the rest of the transfer.
Next thing is that if you play with CRP, you can disable the JTAG interface or some/all of the boot loader functions. With some code read protect modes, the boot loader will never look for the /EINT0 signal to decide if it should enter boot loader mode or if it should directly start an previously loaded application. So having accidentally writen one of the magic values to the CRP memory address, you can get both JTAG and Flash Magic to fail. CRP is documented in the user manual for the processor, just as the different steps performed by the boot loader when interfacing with Flash Magic.
You claim to be an embedded software engineer. How can you calmly come to work when you don't know what these elementary terms mean? Did you check in your user manual? Did you google them?
Tapeer.
u need to remember even software engineers can start at the bottum.
it was not long ago when yew said u were an engineer and new arm but did not even no the abi existed.
Always yo're freind.
Zeusti.
(building supercomputer software for your mum)
Thanks for your kind reply Mr. Per Westermark, Mr.Andrew Neil, Mr. Tamir Michael and Mr. Zeusti
Regards, Saikiran R.
Saikiran,
i always try to provide good advice and help when i can.
it is very king of you to give thanks for the help you received.
(writing software mothers like to cook with)