is there any tool for burning omap730 image under linux?

is there any tool for burning omap730 image under linux?

[jiangqingdong]

is there any tool for burning omap730 image under linux?

thanks

Re: is there any tool for burning omap730 image under linux?

[Pharaoh .]

On 4/25/07, jiangqingdong@konka.com <jiangqingdong@konka.com> wrote:
> is there any tool for burning omap730 image under linux?
>
> thanks
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>

What do you mean by burning omap 730 image? Are you talking about
burning Linux image or flashing the bootloader?

For burning the linux image I think you can use kermit, and for
flashing the u-boot etc I dont think there is any utility, if you have
to flash u-boot to a virgin board.

-Pharaoh.

Re: is there any tool for burning omap730 image under linux?

[Steve Poulsen]

Since you ask how to burn under linux, I assume you already have a 
flashed u-boot and are able to boot Linux. 

Make sure you have MTD support in your kernel.  If configured properly, 
you should be able to simply copy a binary image to the proper device 
file.  One issue in doing this comes up if you flash supports protected 
sectors.  You will get errors about trying to write to protected flash.  
I wrote a simple application using mtd ioctl's to unprotect, program, 
then protect.  Before you can even use such an application, you need to 
get the /dev/mtd* files created and working.  Check the /proc folder.  I 
recall there is a /proc/mtd (or something like that) if MTD is in your 
kernel.  It shows you how your flash is divided.  NOTE, I may remember 
it wrong and it is not /proc but actually a sysfs file.  Another 
solution may be to unprotect using u-boot, boot the kernel, then copy to 
the proper /dev/mtd* file.  I would avoid /dev/mtd0 and /dev/mtd1 until 
you are confident in the procedure.   These are typically u-boot and 
u-boot config.   /dev/mtd2 should be the kernel part of the flash and 
/dev/mtd3 is the flashed file system.  Another thing to consider is that 
you could have MTD configured different than u-boot expects and 
everything will still work....until you go to copy using /dev/mtd* that 
is *watch out*.

If your question is more basic than this, I suggest the OSK newbie 
guide.  That will get your application programmed outside of Linux.  To 
program the first u-boot, I like to use the toolchain to make a u-boot 
that can be loaded by the emulator through CCS. 

Steve

jiangqingdong@konka.com wrote:
> is there any tool for burning omap730 image under linux?
>
> thanks
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>