no recovery menu

[Philip Man]

I have hooked up my K3 with rs232, and can see the boot information. When I see "enter to interrupt", I should see recovery menu, but it writes non readable characters to the screen.
I think my Kindle os is screwed.

Is there a way to flash the firmware via the serial port?

[knc1]

Originally Posted by Philip Man

I have hooked up my K3 with rs232, and can see the boot information. When I see "enter to interrupt", I should see recovery menu, but it writes non readable characters to the screen.
I think my Kindle os is screwed.

Is there a way to flash the firmware via the serial port?

Not if the serial port is screwed up (the "writes non readable characters" part).

Have you tried Kubrick?
With what results?

Kubrick is the tool for replacing the firmware on the K3.

[Philip Man]

I have tried Kubrick, but cannot get into 'usb downloader mode'.
It gave me error contact Amazon support once, then since bricked.

It was flakey after 3.4.2 update, tried Kubrick, got error, now bricked.

[coplate]

you do see the "enter to interrupt" prompt, but you cannot read the rest of it.

Would you be able to capture the raw output and upload it as a file here, I'm always curios to look at this kind of thing.

[Philip Man]

U-Boot 1.3.0-rc3-lab126 (Sep 15 2010 - 19:24:53)

CPU: Freescale i.MX35 at 532 MHz
Board: MX35 Luigi [ POR]
WDOG_WCR = 0xff31
WDOG_WMCR = 0x0
Board Id: SP1B000000000000
S/N: B008A0A00472195A
DRAM: 256 MB
Using default environment

In: serial
Out: serial
Err: serial
No ethernet found.
i.MX35 CPU board version 2.0
Net: No ethernet found.
Hit any key to stop autoboot: 0
## Booting image at 87f40400 ...
Image Name: Linux-2.6.26-rt-lab126
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2167548 Bytes = 2.1 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux............................................. .................................................. ........................... done, booting the kernel.
boot: C def:bcut:batterycut=1,version=s172597:
2.6.26-rt-lab126 #5 Sat Sep 1 14:28:26 PDT 2012 armv6l
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/mxc_keyb.ko (22508 bytes)
Press [ENTER] for recovery menu... 0 /INFO:Partition table verified for /dev/mmcblk0
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/100167 size=3282272256 bytes
flag type first last lba first lba size
Partition p1:
0x00 0x0b 16 <large> 16 6410672
CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
argc == 9
argv[0]: "kinit"
argv[1]: "console=ttymxc0,115200"
argv[2]: "mem=256M"
argv[3]: "panic=10"
argv[4]: "root=/dev/mmcblk0p1"
argv[5]: "ro"
argv[6]: "ip=none"
argv[7]: "quiet"
argv[8]: "lpj=2555904"
Running ipconfig
argc == 4
argv[0]: "IP-Config"
argv[1]: "-i"
argv[2]: "Linux kinit"
argv[3]: "ip=none"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
Checking for init: /sbin/init
Checking for init: /bin/init
Checking for init: /etc/init
Checking for init: /sbin/init.sysvinit
INIT: version 2.86 booting
system: I rcS:def:starting /etc/rcS.d/S02kdb
system: I S02kdb:def:Setting boot device to mmcblk0
kdb set: 'system/driver/filesystem/DEV_ROOT'
system: I rcS:def:starting /etc/rcS.d/S03udev
system: I S03udev:def:setting up virtual fs for hotplug event handling
system: I S03udev:def:starting the hotplug events dispatcher
system: I S03udev:def:synthesizing initial hotplug events
lipc-send-event[380]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[380]: C def:dbusi::Failed to init dbus
lipc-send-event[380]: E defpen::Failed to open LIPC
lipc-send-event[380]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
lipc-send-event[477]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[477]: C def:dbusi::Failed to init dbus
lipc-send-event[477]: E defpen::Failed to open LIPC
lipc-send-event[477]: E def:fail:source=com.lab126.hal, event=audioHS:Sending event failed
system: I rcS:def:starting /etc/rcS.d/S04rootfsresize
system: I S04rootfsresize:def:No rootfs on /dev/mmcblk0p1 resizing needed
system: I rcS:def:starting /etc/rcS.d/S10filesystems
system: I rcS:def:starting /etc/rcS.d/S10hostname
system: I rcS:def:starting /etc/rcS.d/S10network
system: I S10filesystems:def:mounting filesystems
system: I S10hostname:def:setting device hostname
system: I S10network:def:initializing network configuration
iptables-restore: line 1 failed
system: I S10network:def:Installed Firewall
system: I rcS:def:starting /etc/rcS.d/S11chpriority
system: I rcS:def:starting /etc/rcS.d/S11video
Unknown HZ value! (91) Assume 100.
system: W S11chpriority:def:Cannot set priority for IRQ-7
system: I S11video:def:initializing eInk HAL for system use
system: I S11video:def:eink_debug=0
system: I S11video:def:Controller set to broads
system: I rcS:def:starting /etc/rcS.d/S20syslog-ng
system: I S20syslog-ng:def:starting syslog-ng
system: I rcS:def:starting /etc/rcS.d/S21init_time
system: I S21init_time:initboot:time=16040:boot time after init in milliseconds
system: I rcS:def:starting /etc/rcS.d/S45modules
system: I S45modules:def:loading module mwan

[Philip Man]

Tried both Enter keys on keyboard and numpad when it ask. Seems to continue with the boot, and not show Recovery Menu.

uboot is ok, I think it times out.

[knc1]

Originally Posted by Philip Man

Tried both Enter keys on keyboard and numpad when it ask. Seems to continue with the boot, and not show Recovery Menu.

You are asleep on the keyboard.
You (any human) is not fast enough to **wait** for the message.
The timer has already expired by the time you can see the message.

The trick to it is to start holding down the key **before** you see the message.
Don't release the key until after the message passes you by.

[coplate]

Also make sure your ground is connected properly, I was not able to write to my kindle without that, although I could get data.

[Philip Man]

Got the recovery menu. My level shifter was too low on the 1.8V side.

[coplate]

Originally Posted by Philip Man

Got the recovery menu. My level shifter was too low on the 1.8V side.

What device are you using for this? A separate level shifter form your UART, or something with it built in?

The gold standard device recommended here "jim.sh micro.ftx" is out of stock on amazon, unless I want the 5-pack, so I was curious.

[knc1]

Originally Posted by coplate

What device are you using for this? A separate level shifter form your UART, or something with it built in?

The gold standard device recommended here "jim.sh micro.ftx" is out of stock on amazon, unless I want the 5-pack, so I was curious.

Search among the posts made by geekmaster -
he is the one that posted how to build a level shifter to/from 1v8.

[Philip Man]

http://farm8.staticflickr.com/7011/6...e07dff44_z.jpg

Used this to shift from 1.8v to TTL.

[knc1]

Originally Posted by knc1

Search among the posts made by geekmaster -
he is the one that posted how to build a level shifter to/from 1v8.

Originally Posted by Philip Man

http://farm8.staticflickr.com/7011/6...e07dff44_z.jpg

Used this to shift from 1.8v to TTL.

That is an extract from the posts geekmaster made here.
There is reading that goes along with the picture.