Active Topics

 



Notices


Reply
Thread Tools
Posts: 2,130 | Thanked: 8,333 times | Joined on May 2010
#21
Originally Posted by marmistrz View Post
Code:
0xFFFF -e /path/to -t rootfs
wants to dump all images.
Ah.. I see in source code, this is not implemented.
 

The Following 5 Users Say Thank You to pali For This Useful Post:
Posts: 686 | Thanked: 1,934 times | Joined on Jan 2011 @ Germany
#22
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

Last edited by sulu; 2014-10-18 at 22:08.
 
Posts: 555 | Thanked: 916 times | Joined on Dec 2012
#23
You must also copy modules from kernel-cssu-modules_2.6.28-10cssu3_armel.deb package to maemo rootfs.
 

The Following User Says Thank You to elros34 For This Useful Post:
peterleinchen's Avatar
Posts: 3,176 | Thanked: 5,699 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#24
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.
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following User Says Thank You to peterleinchen For This Useful Post:
Estel's Avatar
Posts: 5,029 | Thanked: 8,584 times | Joined on Mar 2011
#25
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?
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!

Last edited by Estel; 2014-10-19 at 11:20.
 

The Following 2 Users Say Thank You to Estel For This Useful Post:
Posts: 2,130 | Thanked: 8,333 times | Joined on May 2010
#26
Originally Posted by Estel View Post
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...).
 

The Following 3 Users Say Thank You to pali For This Useful Post:
Posts: 686 | Thanked: 1,934 times | Joined on Jan 2011 @ Germany
#27
Originally Posted by elros34 View Post
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.


Originally Posted by peterleinchen View Post
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.

Originally Posted by peterleinchen View Post
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.


Originally Posted by peterleinchen View Post
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.


Originally Posted by Estel View Post
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/
 

The Following 2 Users Say Thank You to sulu For This Useful Post:
Posts: 2,130 | Thanked: 8,333 times | Joined on May 2010
#28
Originally Posted by sulu View Post
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.
 

The Following 4 Users Say Thank You to pali For This Useful Post:
Posts: 555 | Thanked: 916 times | Joined on Dec 2012
#29
You can use rescueos to copy modules or first try to flash kernel-power image.
 

The Following User Says Thank You to elros34 For This Useful Post:
Posts: 686 | Thanked: 1,934 times | Joined on Jan 2011 @ Germany
#30
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.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 20:52.