[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Bootblocktool and Rescue partition



Hi again,

OK, It seems to be something wrong with the partition table.
I tested to use the devboard_lx_R2-0-0 ptablespec, and everything worked
well, both the bootblocktool and flashit/flashitall functionality.

But, I want to modify the ptable because i am using 4M flash. (And needs
it...)

Please help.


Here is my ptablespec:
	[ptable]
	# name size     rw-options  type      name
	rescue 0x10000  ro          rescue    rescue.img
	flash1 0x2F0000 ro          kernel    flash1.img
	flash2 0x100000 rw          jffs      flash2.img

and the etrax100boot arguments:

	[henrikl@xxxxxxx./flashit -p
	Command:
	etrax100boot --setreg b0000000 000095f8 --setreg b0000004 00000104
--setreg b000000c 1a200040 --setreg b0000008 00005611 
	--setreg b0000030 00001df0 --setreg b0000038 00001ef3 --bootfile
DBG2 --file fimage c0004000 --flash c0014000 10000 3f0000 --jump 0
	[henrikl@xxxxxxx./flashitall -p
	Command:
	etrax100boot --setreg b0000000 000095f8 --setreg b0000004 00000104
--setreg b000000c 1a200040 --setreg b0000008 00005611 
	--setreg b0000030 00001df0 --setreg b0000038 00001ef3 --bootfile
DBG2 --file fimage c0004000 --flash c0004000 0 400000 --jump 0


...and another ptablespec that doesn´t work with bootblocktool/flashitall
either:

[ptable]
# name size     rw-options  type      name
rescue 0x10000  ro          rescue    rescue.img
flash1 0x350000 ro          kernel    flash1.img
flash2 0xA0000  rw          jffs      flash2.img


// Henrik Löfgren





-----Original Message-----
From: Jonas Holmberg [mailto:jonas.holmberg@xxxxxxx.com]
Sent: den 25 oktober 2001 10:44
To: 'Henrik Löfgren'
Cc: dev-etrax
Subject: RE: Bootblocktool and Rescue partition


> Bootblocktool:
> I have tried to use the bootblocktool to save some parameters, ie SERNO,
HWREV ...
> One parameter can be saved but when i save more than that the board will
not restart!!!
> What is wrong?
> 
> I have used the example from /apps/bootblocktool/README
> "bootblocktool -a HWID 1234 BRAND Axis SERNO 00408C123456"
> (See debug printouts at the end of this message)

This works fine for me (using devboard_lx-R2_0_0):

[root@AxisProduct /]54# bootblocktool -l
[root@AxisProduct /]54# bootblocktool -a HWID 1234 BRAND Axis SERNO
00408C123456
[root@AxisProduct /]54# bootblocktool -l
HWID=1234
BRAND=Axis
SERNO=00408C123456
[root@AxisProduct /]54#

Are you using the same flash-partitions as devboard_lx-R2_0_0?

> Rescue partition:
> Your documentation says:
> "flashit: writes all of the fimage except the rescue partition to flash."
> "flashitall: writes the entire fimage to flash."
> 
> The flashit seems to overwrite the parameters written by bootblocktool.

It shouldn't.

> Shouldn't they only be overwritten by flashitall? 

Yes.

> When i have a new board with empty flashes i use "flashit". But how does
the rescue code gets into the flash??
> 
> The card doesn't start after a flashitall. How should flashitall be used?

Something must be wrong with the arguments to etrax100boot.
Have you modified ptablespec?
What arguments do you get when you run "./flashit -p" and "./flashitall -p"?
Using the ptablespec and kernelconfig for devboard_lx-R2_0_0 I get the
following:

[jonashg@xxxxxxx./flashit -p
Command:
etrax100boot --setreg b0000000 000095f8 --setreg b0000004 00000104 --setreg
b000000c 1a200040 --setreg b0000008 00005611 --setreg b0000030 00001df0
--setreg b0000038 00001ef3 --bootfile DBG2 --file fimage c0004000 --flash
c0014000 10000 1f0000 --jump 0
[jonashg@xxxxxxx./flashitall -p
Command:
etrax100boot --setreg b0000000 000095f8 --setreg b0000004 00000104 --setreg
b000000c 1a200040 --setreg b0000008 00005611 --setreg b0000030 00001df0
--setreg b0000038 00001ef3 --bootfile DBG2 --file fimage c0004000 --flash
c0004000 0 200000 --jump 0

Best regards
/Jonas

winmail.dat