Page 1 of 2 1 2
Reply
Thread Tools
arachnist is offline arachnist
2009-10-23 , 12:32
Posts: 25 | Thanked: 12 times | Joined on Mar 2008 @ Warsaw, Poland
#1
Does the N900 provide a JTAG or a serial console over USB?
It'd be very helpful for fixing stuff if one screws-up with partitioning the mtd device or uploading the ubifs.
I would like to avoid pulling to pieces my N900 once it finally arrives, just to get myself a "seatbelt" for "just in case i screw-up".
 
Alex Atkin UK is offline Alex Atkin UK
2009-10-23 , 22:19
Posts: 716 | Thanked: 303 times | Joined on Sep 2009 @ Sheffield, UK
#2
From what iI have read I believe the idea is you will not be messing with the boot loader so it should never be entirely bricked.

Presumably the boot loader has a recovery mode over USB?
 
arachnist is offline arachnist
2009-10-24 , 01:37
Posts: 25 | Thanked: 12 times | Joined on Mar 2008 @ Warsaw, Poland
#3
With jtag over usb available, it should be possible to even wipe the device entierly (including the uboot bootloader, which is most probably used) and still recover from it, provided one had kernel and os image.

I think that this what the flasher uses, though without an actual device (thanks for the delays...) it won't be possible to check.
 
sarahn is offline sarahn
2009-10-24 , 03:58
Posts: 243 | Thanked: 172 times | Joined on Sep 2007 @ silicon valley
#4
I guess you might be able to pile a whole bunch of stuff into initramfs. If that works let me know.
 
zimon is offline zimon
2010-11-17 , 17:37
Posts: 1,341 | Thanked: 708 times | Joined on Feb 2010
#5
Has anyone tried to clear mtd2?
 
rambo is offline rambo
2010-11-18 , 13:52
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#6
Doing it over the USB might be kinda hard (it would have to be a feature of the bootloader and I'm not sure JTAG could be done in such way), but do take a look at http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports
 
fnordianslip's Avatar
fnordianslip is offline fnordianslip
2010-11-18 , 14:05
Posts: 670 | Thanked: 359 times | Joined on May 2007
#7
The sheevaplug offers these options via built in JTAG and Serial interface hardware conected to its USB Peripheral interface. It's a nice approach, but the N900 doesn't do that.
__________________
Class .. : Lame hacker & beardy boffin
Humour . : [#######---] Alignment: Apathetic anarchist
Patience : [####------] Weapon(s): My cat, my code.
Agro ... : |#---------] Relic(s) : N900, MacBookPro, NSLU2, N800, SheevaPlug, Eee-901, Core2-Quad, PS3
"In theory, theory and practice are the same. In practice, they're not."
--
Beware of extras-devel.
 
rlinfati is offline rlinfati
2010-11-18 , 14:13
Posts: 177 | Thanked: 199 times | Joined on Nov 2007 @ Concepcion, Chile
#8
https://wiki.maemo.org/Updating_the_.../Cold_Flashing

Cold flashing (N900)

If the bootloader is deleted/destroyed with dd, then it is possible to recover it with a cold flash.....
__________________
User:rlinfati
 

The Following User Says Thank You to rlinfati For This Useful Post:
zimon is offline zimon
2010-11-19 , 15:46
Posts: 1,341 | Thanked: 708 times | Joined on Feb 2010
#9
Originally Posted by rlinfati View Post
https://wiki.maemo.org/Updating_the_.../Cold_Flashing

Cold flashing (N900)

If the bootloader is deleted/destroyed with dd, then it is possible to recover it with a cold flash.....
Will that work, if you wipe out all mtd devices to zeros with dd?


# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00020000 "bootloader"
mtd1: 00060000 00020000 "config"
mtd2: 00040000 00020000 "log"
mtd3: 00200000 00020000 "kernel"
mtd4: 00200000 00020000 "initfs"
mtd5: 0fb40000 00020000 "rootfs"

I still have this problem. Flashing both rootfs and eMMC with PR1.3 images didn't fix the problem, so something still hides inside the phone which makes it buggy with this one operator's SIM-card.
 
egoshin is offline egoshin
2010-11-19 , 19:28
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#10
Originally Posted by zimon View Post
Will that work, if you wipe out all mtd devices to zeros with dd?


# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00020000 "bootloader"
mtd1: 00060000 00020000 "config"
mtd2: 00040000 00020000 "log"
mtd3: 00200000 00020000 "kernel"
mtd4: 00200000 00020000 "initfs"
mtd5: 0fb40000 00020000 "rootfs"

I still have this problem. Flashing both rootfs and eMMC with PR1.3 images didn't fix the problem, so something still hides inside the phone which makes it buggy with this one operator's SIM-card.
You can't solve that problem with reflashing. It is operators.
 
Reply
Page 1 of 2 1 2

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 07:24.

Contact Us - Home - Archive - Top