Reply
Thread Tools
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#1
When I run the unpack from the flasher3.0 I get this error. I am wondering if my flasher running on my machine could be causing me other problems as well, or is it not able to upack for other people also. I downloaded the image again and its the exact same size as the first and error in the same way, so its not my flash image.

Can anyone confirm this problem?????

flasher-3.0-static and ../flasher-3..0 same output
root@sauver:/mnt/sda1_removable/root/2007#


flasher-3.0-static -u -F ../RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM-2.bin

SW version in image: RX-34_2007SE_2.2006.51-6_PR_MR0
Image 'kernel', size 1313792 bytes
Version 2.6.18-200651osso2
Image 'initfs', size 1686528 bytes
Version 0.93-25
Image 'rootfs', size 80216064 bytes
Version RX-34_2007SE_2.2006.51-6_PR_MR0
Image '2nd', size 8064 bytes
Valid for RX-34: 1301, 1302
Version 1.1.3-2
Image 'xloader', size 9088 bytes
Valid for RX-34: 1301, 1302
Version 1.1.3-2
Image 'secondary', size 95616 bytes
Valid for RX-34: 1301, 1302
Version 1.1.3-2
Image '2nd', size 8064 bytes
Valid for RX-34: 1201, 1202, 1203
Version 1.1.3-2
Image 'xloader', size 9088 bytes
Valid for RX-34: 1201, 1202, 1203
Version 1.1.3-2
Image 'secondary', size 95616 bytes
Valid for RX-34: 1201, 1202, 1203
Version 1.1.3-2
Image '2nd', size 8064 bytes
Valid for RX-34: 1001, 1101
Version 1.1.3-2
Image 'xloader', size 9088 bytes
Valid for RX-34: 1001, 1101
Version 1.1.3-2
Image 'secondary', size 95616 bytes
Valid for RX-34: 1001, 1101
Version 1.1.3-2
Unpacking kernel image to file 'zImage'...
Unpacking initfs image to file 'initfs.jffs2'...
Unpacking rootfs image to file 'rootfs.jffs2'...
Unpacking 2nd image to file '2nd.bin-RX-34:1301,1302'...
2nd.bin-RX-34:1301,1302: Invalid argument
root@sauver:/mnt/sda1_removable/root/2007#
 
Posts: 94 | Thanked: 7 times | Joined on Oct 2006 @ Metro Detroit Michigan USA
#2
Does it have anything to do with the latest Linux kernel as described here? <http://maemo.org/maemowiki/Flasher_tool_usage?highlight=%28flasher%29#head-524da1a3404b8b55e32f9c661594607821308c9a>
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#3
I've just unpacked 51-6 without any problems on SuSe 10 Enterprise Linux - I tested static and non-static flasher-3.0.

What file system are you unpacking into? My guess is that the filesystem isn't allowing you to create a filename that contains commas or colons - zImage, initfs and rootfs all create single files, however 2nd.bin will unpack into multiple files with names such as "2nd.bin-RX-34:1001,1101"

Here's my output (snipped some for brevity):

Code:
nm-tyan:/tmp/n800/unpack # ../flasher-3.0-static -u -F ../RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM.bin
flasher v0.9.0 (Jan 19 2007)

SW version in image: RX-34_2007SE_2.2006.51-6_PR_MR0
Image 'kernel', size 1313792 bytes
        Version 2.6.18-200651osso2
Image 'initfs', size 1686528 bytes
        Version 0.93-25
...
Image 'secondary', size 95616 bytes
        Valid for RX-34: 1201, 1202, 1203
        Version 1.1.3-2
Image '2nd', size 8064 bytes
        Valid for RX-34: 1001, 1101
        Version 1.1.3-2
Image 'xloader', size 9088 bytes
        Valid for RX-34: 1001, 1101
        Version 1.1.3-2
Image 'secondary', size 95616 bytes
        Valid for RX-34: 1001, 1101
        Version 1.1.3-2
Unpacking kernel image to file 'zImage'...
Unpacking initfs image to file 'initfs.jffs2'...
Unpacking rootfs image to file 'rootfs.jffs2'...
Unpacking 2nd image to file '2nd.bin-RX-34:1301,1302'...
Unpacking xloader image to file 'xloader.bin-RX-34:1301,1302'...
Unpacking secondary image to file 'secondary.bin-RX-34:1301,1302'...
Unpacking 2nd image to file '2nd.bin-RX-34:1201,1202,1203'...
Unpacking xloader image to file 'xloader.bin-RX-34:1201,1202,1203'...
Unpacking secondary image to file 'secondary.bin-RX-34:1201,1202,1203'...
Unpacking 2nd image to file '2nd.bin-RX-34:1001,1101'...
Unpacking xloader image to file 'xloader.bin-RX-34:1001,1101'...
Unpacking secondary image to file 'secondary.bin-RX-34:1001,1101'...
nm-tyan:/tmp/n800/xx # ls -la
total 163375
drwxr-xr-x  2 root root      584 Jan 31 01:06 .
drwxr-xr-x  3 root root      168 Jan 31 01:05 ..
-rw-r--r--  1 root root     8064 Jan 31 01:06 2nd.bin-RX-34:1001,1101
-rw-r--r--  1 root root     8064 Jan 31 01:06 2nd.bin-RX-34:1201,1202,1203
-rw-r--r--  1 root root     8064 Jan 31 01:06 2nd.bin-RX-34:1301,1302
-rw-r--r--  1 root root  1686528 Jan 31 01:06 initfs.jffs2
-rw-r--r--  1 root root 80216064 Jan 31 01:06 rootfs.jffs2
-rw-r--r--  1 root root    95616 Jan 31 01:06 secondary.bin-RX-34:1001,1101
-rw-r--r--  1 root root    95616 Jan 31 01:06 secondary.bin-RX-34:1201,1202,1203
-rw-r--r--  1 root root    95616 Jan 31 01:06 secondary.bin-RX-34:1301,1302
-rw-r--r--  1 root root     9088 Jan 31 01:06 xloader.bin-RX-34:1001,1101
-rw-r--r--  1 root root     9088 Jan 31 01:06 xloader.bin-RX-34:1201,1202,1203
-rw-r--r--  1 root root     9088 Jan 31 01:06 xloader.bin-RX-34:1301,1302
-rw-r--r--  1 root root  1313792 Jan 31 01:06 zImage
 
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#4
You pointed out my problem, thanks.

I was running linux booted of USB, actually vfat partition. So like you said those files could not be created. I forget sometimes, its linux danmit. I always used it with 2005/6 OS with no issues.
 
Reply


 
Forum Jump


All times are GMT. The time now is 15:51.