upgrading u-boot from linux for SH7785LCR board

upgrading u-boot from linux for SH7785LCR board

[Bill Traynor]

I've compiled and tested u-boot from git for the 7785lcr board.  I'd 
like to write the u-boot.bin to flash but do not have a JTAG to be able 
to recover if the write fails.

Given the MTD layout:
dev:    size   erasesize  name
mtd0: 00080000 00040000 "loader"
mtd1: 00080000 00040000 "bootenv"
mtd2: 00400000 00040000 "kernel"
mtd3: 03b00000 00040000 "data"

Is it reasonable to do the following:

flash_erase /dev/mtd[0]
dd if=/tmp/u-boot.bin of=/dev/mtd0 bs\x128k conv=sync

I'd rather not brick the board I have, so if someone who does have the 
capability to recover could test this method for me, it'd be appreciated.

Thanks
Bill

Re: upgrading u-boot from linux for SH7785LCR board

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 751 bytes --]

On Sunday, July 04, 2010 14:11:15 Bill Traynor wrote:
> I've compiled and tested u-boot from git for the 7785lcr board.  I'd
> like to write the u-boot.bin to flash but do not have a JTAG to be able
> to recover if the write fails.
> 
> Given the MTD layout:
> dev:    size   erasesize  name
> mtd0: 00080000 00040000 "loader"
> mtd1: 00080000 00040000 "bootenv"
> mtd2: 00400000 00040000 "kernel"
> mtd3: 03b00000 00040000 "data"
> 
> Is it reasonable to do the following:
> 
> flash_erase /dev/mtd[0]
> dd if=/tmp/u-boot.bin of=/dev/mtd0 bs=128k conv=sync

why dont you just use the mtdblock interface ?  it will take care of all the 
weird flash issues like erasing/etc...

all i do is:
cat u-boot.bin > /dev/mtdblock0
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: upgrading u-boot from linux for SH7785LCR board

[Nobuhiro Iwamatsu]

Hi, Bill.

Bill Traynor wrote:
> I've compiled and tested u-boot from git for the 7785lcr board.  I'd 
> like to write the u-boot.bin to flash but do not have a JTAG to be able 
> to recover if the write fails.
> 
> Given the MTD layout:
> dev:    size   erasesize  name
> mtd0: 00080000 00040000 "loader"
> mtd1: 00080000 00040000 "bootenv"
> mtd2: 00400000 00040000 "kernel"
> mtd3: 03b00000 00040000 "data"
> 
> Is it reasonable to do the following:
> 
> flash_erase /dev/mtd[0]
> dd if=/tmp/u-boot.bin of=/dev/mtd0 bs\x128k conv=sync

I think that you shoud use flashcp command if you use flash_erase.
This command is in mtd-utils ( same flash_erase).

Best regards,
   Nobuhiro

Re: upgrading u-boot from linux for SH7785LCR board

[Bill Traynor]

On 10-07-04 05:24 PM, Mike Frysinger wrote:
> On Sunday, July 04, 2010 14:11:15 Bill Traynor wrote:
>    
>> I've compiled and tested u-boot from git for the 7785lcr board.  I'd
>> like to write the u-boot.bin to flash but do not have a JTAG to be able
>> to recover if the write fails.
>>
>> Given the MTD layout:
>> dev:    size   erasesize  name
>> mtd0: 00080000 00040000 "loader"
>> mtd1: 00080000 00040000 "bootenv"
>> mtd2: 00400000 00040000 "kernel"
>> mtd3: 03b00000 00040000 "data"
>>
>> Is it reasonable to do the following:
>>
>> flash_erase /dev/mtd[0]
>> dd if=/tmp/u-boot.bin of=/dev/mtd0 bs\x128k conv=sync
>>      
> why dont you just use the mtdblock interface ?  it will take care of all the
> weird flash issues like erasing/etc...
>
> all i do is:
> cat u-boot.bin>  /dev/mtdblock0
>    
Thanks, that worked perfectly.

> -mike
>    

Re: upgrading u-boot from linux for SH7785LCR board

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 426 bytes --]

On Sunday, July 04, 2010 23:29:28 Bill Traynor wrote:
> On 10-07-04 05:24 PM, Mike Frysinger wrote:
> > all i do is:
> > cat u-boot.bin>  /dev/mtdblock0
> 
> Thanks, that worked perfectly.

for safety sake, you might want to dd it back out and cmp the result.  so 
something like:
	dd if=/dev/mtdblock0 of=u-boot.bin.new \
		ibs=$(wc -c u-boot.bin | awk '{print $1}') count=1
	cmp u-boot.bin u-boot.bin.new
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]