maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   0xFFFF - Open Free Fiasco Firmware Flasher (https://talk.maemo.org/showthread.php?t=87996)

pali 2012-11-24 15:19

0xFFFF - Open Free Fiasco Firmware Flasher, version 0.8
 
EDIT 2018-07-08: Version 0.8 was released
EDIT 2016-12-25: Version 0.7 was released
EDIT 2014-11-18: Security update 0.6.1 was released
EDIT 2014-05-12: Final 0.6 was released

I'm releasing 0xFFFF flasher. It is open source alternative to Nokia proprietary flasher-3.5.

0xFFFF supports:
* generating and unpacking FIASCO images
* flash any image via NOLO protocol
* load+boot kernel & initfs without flashing
* read device and version information from NOLO
* dumping images to directory (or one fiasco image) on device (need deb package mtd-utils)

Missing features:
* flash mmc image image Mk II protocol
* flashing on device
...

Note that this is new rewritten beta version of 0xFFFF for Nokia N900. Flashing can damage or brick your device! You have been warned. Only for developers & testers!

Download:

Binary armel DEB package:
http://repository.maemo.org/extras-d....8-1_armel.deb
(also available in Application Manager with Extras-Devel or Extras-Testing enabled)

Source code tarball:
https://github.com/pali/0xFFFF/relea...FFF-0.8.tar.gz

Source code git repository:
https://github.com/pali/0xFFFF

Examples:

Via USB:

Load kernel & initfs and boot it:
$ 0xFFFF -m initfs -m kernel -l -b

Flash kernel:
$ 0xFFFF -m kernel -f

Flash FIASCO image:
$ 0xFFFF -M image.fiasco -f

Flash only kernel from FIASCO image:
$ 0xFFFF -M image.fiasco -t kernel -f

Reboot:
$ 0xFFFF -r

Identify device:
$ 0xFFFF -I

On device (need nanddump from mtd-utils):

Dump all images to current directory:
$ 0xFFFF -e

Dump all images to one fiasco file:
$ 0xFFFF -E dump.fiasco

FIASCO packaging:

Show FIASCO archive:
$ 0xFFFF -M image.fiasco -i

Unpack fiasco image to current directory:
$ 0xFFFF -M image.fiasco -u

Generate new fiasco image from files xloader.bin, nolo.bin, zImage, rootfs and append device&version information (xloader for RX-51 hw revision: 2101 and 2102, version 1.0)
$ 0xFFFF -m RX-51:2101,2102:1.0:xloader:xloader.bin -m RX-51:2101,2102:1.0:secondary:nolo.bin -m 2.6.28:kernel:zImage -m rootfs -g image.fiasco

For all options see help:
$ 0xFFFF -h

0xFFFF can detect more image types from file header. If autodetection not working, see syntax of param -m ([[[dev:[hw:]]ver:]type:]file[%lay])

Sourav.dubey 2012-11-24 15:24

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Superb app
been waiting for it
thanks

davdav 2012-11-24 15:55

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Thanks :)

12345

ade 2012-11-24 20:16

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by pali (Post 1297894)
Source code with i386, x86_64 and arm binaries are here: 0xFFFF-0.6-beta1.tar.gz

Apparently the binaries are not included.

No big deal of course, I can compile it myself...


Edit: Sorry, I missed them, they are in the src directory.

nbedford 2012-11-24 20:39

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Can support N9 or just N900?

pali 2012-11-24 21:00

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by ade (Post 1297959)
Apparently the binaries are not included.

No big deal of course, I can compile it myself...

Check sha1sum of tarball: b57d517f2d08cca1758e56827356ff61726835ca

There are static linked binaries:

$ file 0xFFFF/src/0xFFFF-*
0xFFFF/src/0xFFFF-arm: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, for GNU/Linux 2.6.8, stripped
0xFFFF/src/0xFFFF-i386: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.6.24, BuildID[sha1]=0x95b814970da75646fcc042771ae0af158d6322ef, stripped
0xFFFF/src/0xFFFF-x86_64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.24, BuildID[sha1]=0x88be01a22db723230ade45f6811bf055644372ac, stripped

pali 2012-11-24 21:01

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by nbedford (Post 1297964)
Can support N9 or just N900?

Only N900 and older tablets. But patches for N9/950 are welcome...

joshgillies 2012-12-01 06:15

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Great thanks! As is currently stands is this capable of being a drop in replacement to flasher for most things? (eg http://wiki.maemo.org/Updating_the_f...MC_in_the_N900).

Also is there a source repository hosted anywhere currently?

Thanks for this! :)

pali 2012-12-01 11:26

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Flashing eMMC is done via Mk II protocol which is not implemented yet. But some info about Mk II protocol is in "doc/mkii" file.

And for source code git repository: In will be in future...

juiceme 2012-12-20 06:42

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Is the flashing procedure very different between N900 and N9(50) devices?

As is well known the Harmattan flasher 3.12.1 cannot be used to flash an older PR release on a device that is flashed with a newer PR. Is that limitation built into the flasher executable or is it enforced in the NOLO part of the system on the device somehow?

What about the bytestream transfer between the PC and the device when flashing, is that encrypted and authenticated? I guess it would be possible to build quite secure authentication mechanisms between the flasher and NOLO but has Nokia bothered to do that?

pali 2012-12-20 09:11

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by juiceme (Post 1306249)
As is well known the Harmattan flasher 3.12.1 cannot be used to flash an older PR release on a device that is flashed with a newer PR. Is that limitation built into the flasher executable or is it enforced in the NOLO part of the system on the device somehow?

Implemented in X-Loader & NOLO :-(

TMavica 2012-12-20 09:19

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
looking forward to N9 version

juiceme 2012-12-21 12:13

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by pali (Post 1306292)
Implemented in X-Loader & NOLO :-(

Okay. In that case it is fairly difficult to reverse-engineer it. Bummer.

What about documentation, is there some comprehensive explanation about the workings of the whole flashing chain in Harmattan?

What is the function of the different parts of the flashing process, for example what is the APE algorithm that is needed, for example when flashing only the kernel image? I tried googling for that but no success really?

pali 2013-01-24 01:02

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Here is public git repository for 0xFFFF: https://gitorious.org/0xffff/0xffff

pali 2014-05-10 21:10

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Final version 0.6 was released, see first post!

pali 2014-06-18 10:30

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
I pushed package to extras-devel & extras-testing, so limited operations can be also done on device.

http://maemo.org/packages/view/0xffff/

marmistrz 2014-07-16 12:27

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Code:

Error: Dump image via USB is not supported
So how else can it be dumped

pali 2014-07-16 12:50

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Only on device.

marmistrz 2014-07-16 16:56

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Code:

0xFFFF -e /path/to -t rootfs
wants to dump all images.

elros34 2014-09-26 20:56

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
I discovered that it is easy to create rootfs backup with this tool so If anyone is interested:
First use 0xFFFF -e to dump all images. It will partially fail because of not enough memory to dump emmc but kernel and rootfs will be dumped. Then create fiasco image from dumped files:
0xFFFF -m 2.6.28:kernel:kernel-RX-51_2.6.28-20103103\+0m5 - m rootfs:rootfs-RX-51_RX-51_2009SE_21.2011.38-1_PR_MR0 -g fiasco.image.

pali 2014-09-26 21:05

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by marmistrz (Post 1433026)
Code:

0xFFFF -e /path/to -t rootfs
wants to dump all images.

Ah.. I see in source code, this is not implemented.

sulu 2014-10-18 21:59

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
I bricked my testing N900 running CSSU thumb by installing U-Boot without creating bootmenu entries. U-Boot came up fine but of course couldn't boot anything.

At that point 0xFFFF gave me that output for the device:
Code:

# ./0xFFFF/src/0xFFFF-i386 -I
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: 2.6.28-20103103+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

I figured I might just have to extract the current CSSU thumb kernel from its debian package [1] and flash it like this:
Code:

# ./0xFFFF/src/0xFFFF-i386 -m zImage-2.6.28.10-cssu3 -f
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: 2.6.28-20103103+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

Load image:
File: zImage-2.6.28.10-cssu3
    Image type: kernel
    Image size: 1785856 bytes
Sending image header...
Sending image...
  100% [#################################################################]
Done
Flashing image...
Done

Apparently It's not that simple since Maemo doesn't boot and of course not even U-Boot does anymore.
0xFFFF now says this:
Code:

# ./0xFFFF/src/0xFFFF-i386 -I
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: RX-51 (0x421:0x106) in Cold flashing mode
USB device product string: Nokia USB ROM
USB device serial number string: (not detected)
Detected USB device: (not detected) 

Waiting for ASIC ID...
Detected OMAP3430 chip
Device: (not detected)
HW revision: (not detected)
NOLO version: (not detected)
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: (not detected)
Content eMMC version: (not detected)
Root device: (not detected)
USB host mode: (not detected)
R&D mode: (not detected)
Sending OMAP memory boot message...

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

Before I do any more stupid things I'd like to ask for advice. There's no data on the device that's worth saving but I'd prefer to only flash what's necessary.
Since I've never flashed an N900 before I neither have any experience with this, nor do I have any images. I obviously have 0xFFFF and I got the maemo-flasher debian package from here [2] (afaik it's the same for N810 and N900, please correct me if I'm wrong).

So can someone please tell me what files I need to obtain and what to do with them (if it differs from the standard procedure)?
The image links in the wiki are dead, so seem the links panjgoori put up here [3].



[1] http://maemo.merlin1991.at/cssu/comm...k/kernel-cssu/
[2] http://www.jedge.com/n810/flasher/
[3] http://talk.maemo.org/showthread.php?t=88795&page=2#13

elros34 2014-10-19 08:03

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
You must also copy modules from kernel-cssu-modules_2.6.28-10cssu3_armel.deb package to maemo rootfs.

peterleinchen 2014-10-19 10:54

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Afair u-boot had (has?) the stock kernel attached.
So you should have only selected run attached kernel!?

Now you have cssu kernel and possibly no modules, as said. I would go and flash the u-boot kernel (package u-boot-flasher) if its size is around 2MB. Then you should be able to run attached kernel.
Furthermore ther is u-boot console giving you the possibility to "run noloboot" which should also work. More info in u-boot thread.

If all fails, just extract stock kernel and load/flash this one to device, as you have done with cssu. This should boot.

Estel 2014-10-19 11:17

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Why no modules? He clearly stated, that he had been running CSSU thumn before flashed u-boot to kernel area.

I have no idea what is going wrong, sulu - flashing zImage, as you did (if it was the SAME kernel and version, that you used before u-boot) should be enough to boot without problems. Maybe you were running older version?

/Estel

// Edit

Also, I don't get the thing about "cold flashing mode" from your logs. Why the hell 0xFFFF brings it up on it's own? Maybe flashing kernel's zImage went wrong, somehow?

pali 2014-10-19 11:46

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by Estel (Post 1443437)
Also, I don't get the thing about "cold flashing mode" from your logs. Why the hell 0xFFFF brings it up on it's own? Maybe flashing kernel's zImage went wrong, somehow?

Because 0xFFFF is faster than nokia flasher. When you start n900 it first enter to cold flash mode, then wait very very small interval and then boot nolo which enter into normal flash mode. And 0xFFFF detected that cold flash mode and just told n900 to continue booting nolo (Sending OMAP memory boot message...).

sulu 2014-10-19 13:14

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by elros34 (Post 1443428)
You must also copy modules from kernel-cssu-modules_2.6.28-10cssu3_armel.deb package to maemo rootfs.

How would I do that? I see no way to flash these modules and I don't know how to mount any of the partitions on the dead device manually.


Quote:

Originally Posted by peterleinchen (Post 1443434)
Afair u-boot had (has?) the stock kernel attached.
So you should have only selected run attached kernel!?

I tried that but it didn't boot the kernel.
I'm not sure what exactly happened but it was either a bunch of messages saying the FS couldn't be mounted (this definitely happened when trying to boot from eMMC and µSD) or plain nothing.

Quote:

Originally Posted by peterleinchen (Post 1443434)
Now you have cssu kernel and possibly no modules, as said. I would go and flash the u-boot kernel (package u-boot-flasher) if its size is around 2MB. Then you should be able to run attached kernel.

Ok, so I got the extras-testing package [1], extracted u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco (1.8MB) and tried to flash it:
Code:

# ./0xFFFF/src/0xFFFF-i386 -m u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Warning: Removing unknown image (specified by file u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco)

But something must have happened because 0xFFFF now says this:
Code:

# ./0xFFFF/src/0xFFFF-i386 -I
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

When I start the device now the white LED goes on and I get the Nokia logo with backlight, but nothing more. Before trying to reflash u-boot I only got the Nokia logo wthout backlight or LED.


Quote:

Originally Posted by peterleinchen (Post 1443434)
If all fails, just extract stock kernel and load/flash this one to device, as you have done with cssu. This should boot.

Are you sure? I'd guess it panics as soon as any of the thumb binaries gets executed.


Quote:

Originally Posted by Estel (Post 1443437)
Maybe you were running older version?

Probably. I did the last update about two weeks ago.


[1] http://repository.maemo.org/extras-t...free/u/u-boot/

pali 2014-10-19 13:27

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by sulu (Post 1443445)
Ok, so I got the extras-testing package [1], extracted u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco (1.8MB) and tried to flash it:
Code:

# ./0xFFFF/src/0xFFFF-i386 -m u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Warning: Removing unknown image (specified by file u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco)


To flash fiasco image (not raw image), you need to specify it with big -M param, not small -m.

fiasco image is just archive (with attributes) which can contains more raw images.

elros34 2014-10-19 13:54

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
You can use rescueos to copy modules or first try to flash kernel-power image.

sulu 2014-10-19 15:08

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Flashing u-boot was successful - sort of:
Code:

# ./0xFFFF/src/0xFFFF-i386 -M u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

Load image:
    Image type: kernel
    Image size: 2008960 bytes
    Image version: u-boot-2013.04-1
Sending image header...
Sending image...
  100% [#################################################################]
Done
Flashing image...
Done
*** glibc detected *** ./0xFFFF/src/0xFFFF-i386: double free or corruption (fasttop): 0x0a0f22c0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x70c41)[0xf75c1c41]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x724a8)[0xf75c34a8]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(cfree+0x6d)[0xf75c65ed]
./0xFFFF/src/0xFFFF-i386[0x8053791]
./0xFFFF/src/0xFFFF-i386[0x80555cd]
./0xFFFF/src/0xFFFF-i386[0x804dcb4]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xf7567e66]
./0xFFFF/src/0xFFFF-i386[0x80495a1]
======= Memory map: ========
08048000-08069000 r-xp 00000000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
08069000-0806a000 r--p 00020000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
0806a000-0806b000 rw-p 00021000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
0806b000-0846b000 rw-p 00000000 00:00 0
0a0f2000-0a113000 rw-p 00000000 00:00 0                                  [heap]
f7400000-f7421000 rw-p 00000000 00:00 0
f7421000-f7500000 ---p 00000000 00:00 0
f754f000-f7551000 rw-p 00000000 00:00 0
f7551000-f76ae000 r-xp 00000000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76ae000-f76b0000 r--p 0015d000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76b0000-f76b1000 rw-p 0015f000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76b1000-f76b4000 rw-p 00000000 00:00 0
f76b4000-f76bb000 r-xp 00000000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bb000-f76bc000 r--p 00006000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bc000-f76bd000 rw-p 00007000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bd000-f76be000 rw-p 00000000 00:00 0
f76c1000-f76dd000 r-xp 00000000 08:21 927047                            /lib/i386-linux-gnu/libgcc_s.so.1
f76dd000-f76de000 rw-p 0001b000 08:21 927047                            /lib/i386-linux-gnu/libgcc_s.so.1
f76de000-f76e1000 rw-p 00000000 00:00 0
f76e1000-f76e2000 r-xp 00000000 00:00 0                                  [vdso]
f76e2000-f76fe000 r-xp 00000000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
f76fe000-f76ff000 r--p 0001b000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
f76ff000-f7700000 rw-p 0001c000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
ffdf2000-ffe16000 rw-p 00000000 00:00 0                                  [stack]
Abgebrochen

and:
Code:

# ./0xFFFF/src/0xFFFF-i386 -I
0xFFFF v0.6  // Open Free Fiasco Firmware Flasher

Not a local device

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: u-boot-2013.04-1
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

This is on Debian Wheezy/amd64 with multiarch. The amd64 version of 0xFFFF didn't work because it requires glibc 2.14 but Wheezy only has 2.13. I'm not sure if the crash has any effact as the flash operation seems already finished.

U-boot now comes up fine but when trying to boot the attached kernel I get these messages (transcribed from a photo):
Code:

mmc1(part 0) Is current device
readImg bootmenu.scr
** Unable to read file bootmenu.scr **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
gpio: pin 71 (gpio 71) value is 1
Booting attached kernel image ...
## Booting kernel from legacy Image at 8fe40800 ...
  Image Name:  zImage-2.6.28-omap1
  Image Type:  ARM Linux Kernel Image (uncompressed)
  Data Size:    1746688 Bytes =1.7 MiB
  Load Address: 80008000
  Entry Point:  80008000
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
OK

Starting kernel ...

At this point the screen goes black (backlight stays on) and the white LED goes off. Apparently nothing else happens for the next 5 minutes.


@elros34:
I'd prefer to have u-boot on this device so I'd like to follow this path first.

elros34 2014-10-19 15:29

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by sulu (Post 1443454)
I'd prefer to have u-boot on this device so I'd like to follow this path first.

If you think that running thumb system on stock (attached) kernel is right way then I wish you luck :P

pali 2014-10-19 16:10

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by pali (Post 1440728)
Quote:

Originally Posted by marmistrz (Post 1433026)
Code:

0xFFFF -e /path/to -t rootfs
wants to dump all images.

Ah.. I see in source code, this is not implemented.

Implemented: https://gitorious.org/0xffff/0xffff/...def3ab346520bd

pali 2014-10-19 16:13

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by sulu (Post 1443454)
Code:

...
Done
Flashing image...
Done
*** glibc detected *** ./0xFFFF/src/0xFFFF-i386: double free or corruption (fasttop): 0x0a0f22c0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x70c41)[0xf75c1c41]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x724a8)[0xf75c34a8]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(cfree+0x6d)[0xf75c65ed]
./0xFFFF/src/0xFFFF-i386[0x8053791]
./0xFFFF/src/0xFFFF-i386[0x80555cd]
./0xFFFF/src/0xFFFF-i386[0x804dcb4]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xf7567e66]
./0xFFFF/src/0xFFFF-i386[0x80495a1]
======= Memory map: ========
08048000-08069000 r-xp 00000000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
08069000-0806a000 r--p 00020000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
0806a000-0806b000 rw-p 00021000 08:11 64028687                          /dsk/data2/n900/flasher/0xFFFF/src/0xFFFF-i386
0806b000-0846b000 rw-p 00000000 00:00 0
0a0f2000-0a113000 rw-p 00000000 00:00 0                                  [heap]
f7400000-f7421000 rw-p 00000000 00:00 0
f7421000-f7500000 ---p 00000000 00:00 0
f754f000-f7551000 rw-p 00000000 00:00 0
f7551000-f76ae000 r-xp 00000000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76ae000-f76b0000 r--p 0015d000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76b0000-f76b1000 rw-p 0015f000 08:21 915527                            /lib/i386-linux-gnu/i686/cmov/libc-2.13.so
f76b1000-f76b4000 rw-p 00000000 00:00 0
f76b4000-f76bb000 r-xp 00000000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bb000-f76bc000 r--p 00006000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bc000-f76bd000 rw-p 00007000 08:21 927183                            /lib/i386-linux-gnu/libusb-0.1.so.4.4.4
f76bd000-f76be000 rw-p 00000000 00:00 0
f76c1000-f76dd000 r-xp 00000000 08:21 927047                            /lib/i386-linux-gnu/libgcc_s.so.1
f76dd000-f76de000 rw-p 0001b000 08:21 927047                            /lib/i386-linux-gnu/libgcc_s.so.1
f76de000-f76e1000 rw-p 00000000 00:00 0
f76e1000-f76e2000 r-xp 00000000 00:00 0                                  [vdso]
f76e2000-f76fe000 r-xp 00000000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
f76fe000-f76ff000 r--p 0001b000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
f76ff000-f7700000 rw-p 0001c000 08:21 915514                            /lib/i386-linux-gnu/ld-2.13.so
ffdf2000-ffe16000 rw-p 00000000 00:00 0                                  [stack]
Abgebrochen


This is not good :-( But flash should be successfull.

pali 2014-10-19 16:16

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by sulu (Post 1443454)
This is on Debian Wheezy/amd64 with multiarch. The amd64 version of 0xFFFF didn't work because it requires glibc 2.14 but Wheezy only has 2.13. I'm not sure if the crash has any effact as the flash operation seems already finished.

Try to recompile version from git: https://gitorious.org/0xffff/0xffff
Debian has 0xFFFF in sid: https://packages.debian.org/sid/0xffff

sulu 2014-10-19 22:04

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
I rebuilt the 0xFFFF Jessie/amd64 package but the result was the same. Flashing went fine but the same memory corruption occured afterwards.

I then flashed the combined image I found here [1] and the device came up fine. Reinstalled CSSU thumb, u-boot and bootimg packages and everything is ok.
I think my initial fault was that I only installed u-boot but not the bootimg package.


[1] http://gsmphonetricks.blogspot.de/20...212011381.html


edit:
After successfully flashing the combined image 0xFFFF repeated this in an infinite loop (had to kill it via ctrl+c):
Code:

Waiting for USB device... 
Found USB device: SU-18/RX-44/RX-48/RX-51 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUM364446
Detected USB device: RX-51           

Initializing NOLO...
Device: RX-51
HW revision: 2101
NOLO version: 1.4.14
Kernel version: 2.6.28-20103103+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1_PR_MR0
Content eMMC version: RX-51_2009SE_1.2009.41-1.DACH
Root device: flash
USB host mode: disabled
R&D mode: disabled

Load image:
    Image type: cmt-mcusw
    Image size: 5966464 bytes
    Image version: rx51_ICPR82_10w08
Sending image header...
Sending image...
  100% [#################################################################]
Done
Flashing image...
ERROR: SST1 CH0: transmit timed out
ERROR: Error processing request, stalling
ERROR: EP0 STALL sent
ERROR: Premature end of control transfer
Error: Flashing failed


irulestar 2014-10-20 11:51

The Greatest Flasher :D

Estel 2014-10-20 16:14

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by sulu (Post 1443454)
Flashing u-boot was successful - sort of:[code]# ./0xFFFF/src/0xFFFF-i386 -M u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f

Methinks that if you would flash the cssu-thumb kernel instead of u-boot+vanilla kernel at this point, you would have perfectly booting device, in the state from before installing u-boot. Now, you could have go with installing u-boot and it's bootmenu tools.

But I haven't flashed in ages, so forgive, if I messed something. Also, it's of no importance, as you have already reflashed, right?

sulu 2014-10-20 20:30

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
Quote:

Originally Posted by Estel (Post 1443559)
Methinks that if you would flash the cssu-thumb kernel instead of u-boot+vanilla kernel at this point, you would have perfectly booting device, in the state from before installing u-boot.

That was the first thing I've tried, but apparently I either did it wrong or it simply doesn't work.

peterleinchen 2014-10-20 21:16

Re: 0xFFFF - Open Free Fiasco Firmware Flasher
 
But it should have! :confused:
So apparently something else has been messed up.

irulestar 2014-10-23 02:59

[ASK]
I got trouble with My Other N9
On Ubiboot MODE :(
Its totally dead. I try to re-Flash. But My PC won't detect my N9 :(
I try flasher -i and (PC Wont dettect but LED still Breathing) :(
And i try Phoenix too, its not detect :(

So!? Can I fix it using this Flasher!?
And HOW to do it!?
Please HELP n Advice :(


All times are GMT. The time now is 10:18.

vBulletin® Version 3.8.8