public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* how to burn u-boot into flash
@ 2006-05-09 12:54 xuxian
  2006-05-09 13:10 ` Wolfgang Denk
  2006-05-11  1:55 ` Matthew Percival
  0 siblings, 2 replies; 7+ messages in thread
From: xuxian @ 2006-05-09 12:54 UTC (permalink / raw)
  To: linux-omap-open-source; +Cc: u-boot-users

Hi all,

	I have a custom board with omap5912, Samsung 32M SDRAM, and Intel
Flash(28F256J3C). The board was designed according to the OSK5912, so the
circuit is close to OSK. And the hardware seems work fine by using the test
program in CCS. Now, I want to burn the u-boot in flash. I try the following
three methods, but all die.

1. Use osk5912-uboot-1.1.1.out provided by the CD of OSK5912, but it can't
recognize the flash device on my board and I have no idea how to modify it
or create one adapt to my board.

2. I noticed that CCS can read and load .ELF file generated by compiling
u-boot. But after I load it to SDRAM and run it, there is nothing in
console. It seems the console dead when it connects the simulator, and the
u-boot in RAM so reset is useless. Is there some methods to add a flash
writer at the head of u-boot? And how can I do this?

3. Recently, I find a tool named FlashBurn DSK, it can burn the ASCII hex or
Motorola-S file to flash. But I only have .elf and .bin file which can't be
recognized by the conversion utility in CCS. I use several utilities such as
bin2hex, elf2hex, but all failed. Can anyone tell me how to convert .elf or
.bin file to ASCII hex or Motorola-S file?

I have had this problem for quite a while and still can't fine the solution.
I just want to burn the u-boot into flash. I have an OSK5912, a custom board
and a XDS560 simulator. Any help will be appreciated. Thank in advance.

Best Regard,
xuxian

^ permalink raw reply	[flat|nested] 7+ messages in thread
* RE: how to burn u-boot into flash
@ 2006-05-12  2:06 Ishigami, Tatsuya
  0 siblings, 0 replies; 7+ messages in thread
From: Ishigami, Tatsuya @ 2006-05-12  2:06 UTC (permalink / raw)
  To: Matthew Percival; +Cc: Linux OMAP Open Source

G'Day,

 Just a thought....

 There three programs worked for the OSK (2 x 28F128J3 flash),
while xuxian has a custom board (1 x 28F256J3).

 If this is the case, they need slightly different procedure to
program.

 # I don't know why these utilities rejected to load
the *.bin file, though.

 Regards,
 Ishigami

-----Original Message-----
From: Matthew Percival
Sent: Friday, May 12, 2006 8:11 AM
To: Linux OMAP Open Source
Subject: RE: how to burn u-boot into flash

G'Day,

> 	I have tried the third one and it tells me the u-boot.bin is not
a
> hex format file. The only thing different is my FlashBurn DSK is a
free one.
> Are you sure the non-free one can load u-boot.bin? I will consider
buying
> one.

	Hmm... I could swear I have just used u-boot.bin with all three
programs (I have used both the free and non-free with FlashBurn).  It
may be possible that there is something funny with your file.  A
known-good image can be found here, if you want to check that:
http://tree.celinuxforum.org/CelfPubWiki/OSK?action=AttachFile&do=get&ta
rget=osk-u-boot.bin
Alternatively, u-boot.srec (in the same directory as u-boot.bin) is a
Motorola S-Record format file, which may be of use to you.

	-- Matthew

_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2006-05-12  4:21 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-09 12:54 how to burn u-boot into flash xuxian
2006-05-09 13:10 ` Wolfgang Denk
2006-05-11  1:55 ` Matthew Percival
2006-05-11 14:24   ` xuxian
2006-05-11 23:11     ` Matthew Percival
2006-05-12  4:21       ` xuxian
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12  2:06 Ishigami, Tatsuya

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox