![]() |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
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 Code:
# ./0xFFFF/src/0xFFFF-i386 -m zImage-2.6.28.10-cssu3 -f 0xFFFF now says this: Code:
# ./0xFFFF/src/0xFFFF-i386 -I 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 |
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.
|
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. |
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? |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
Quote:
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:
Code:
# ./0xFFFF/src/0xFFFF-i386 -m u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f Code:
# ./0xFFFF/src/0xFFFF-i386 -I Quote:
Quote:
[1] http://repository.maemo.org/extras-t...free/u/u-boot/ |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
fiasco image is just archive (with attributes) which can contains more raw images. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
You can use rescueos to copy modules or first try to flash kernel-power image.
|
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 Code:
# ./0xFFFF/src/0xFFFF-i386 -I 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 @elros34: I'd prefer to have u-boot on this device so I'd like to follow this path first. |
All times are GMT. The time now is 21:12. |
vBulletin® Version 3.8.8