Topic: Help reviving a Chumby One from deep coma
Hi All,
My trusty Chumby One is brain-dead now, the only thing it prints on the Debugging UART3.3V interface is this:
Loading SD image...
Reading 0x00000800 bytes from offset 0x0000b800 to destination 0x45a00000
Skipping 2944 chunks
Reading 0x00034800 bytes from offset 0x0000f800 to destination 0x40808000
Skipping 3968 chunks
So, in my mind semms that it is not totaly dead, just in deep coma, it prints these 5 lines and then a various number of lines afterwards.
So, it does not print what it used to print, which are these lines:
Jumping to address 0x40808000:
0x00000000 0f 00 a0 e1 08 00 40 e2 02 0a 40 e2 08 10 9f e5 |......@...@.....|
0x00000010 00 00 81 e5 02 00 00 eb 2a 05 00 eb 20 20 00 00 |........*... ..|
0x00000020 11 b1 11 c1 14 00 9f e5 14 10 9f e5 00 20 a0 e3 |............. ..|
0x00000030 04 20 80 e4 01 00 50 e1 fc ff ff 3a 0e f0 a0 e1 |. ....P....:....|
0x00000040 20 18 02 00 80 18 02 00 0e f0 a0 e1 0e f0 a0 e1 | ...............|
0x00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
0x00000060 04 b0 2d e5 00 b0 8d e2 14 d0 4d e2 64 30 9f e5 |..-.......M.d0..|
0x00000070 00 30 93 e5 10 30 0b e5 58 20 9f e5 00 30 a0 e3 |.0...0..X ...0..|
0x00000080 00 30 82 e5 50 30 9f e5 08 30 0b e5 4c 20 9f e5 |.0..P0...0..L ..|
0x00000090 08 30 1b e5 3f 30 03 e2 00 30 82 e5 40 20 9f e5 |.0..?0...0..@ ..|
0x000000a0 08 30 1b e5 23 33 a0 e1 00 30 82 e5 70 30 a0 e3 |.0..#3...0..p0..|
0x000000b0 0c 30 0b e5 2c 20 9f e5 0c 30 1b e5 00 30 82 e5 |.0.., ...0...0..|
0x000000c0 10 20 9f e5 10 30 1b e5 00 30 82 e5 00 d0 8b e2 |. ...0...0......|
0x000000d0 00 08 bd e8 1e ff 2f e1 30 00 07 80 41 03 00 00 |....../.0...A...|
0x000000e0 28 00 07 80 24 00 07 80 2c 00 07 80 00 48 2d e9 |(...$...,....H-.|
0x000000f0 04 b0 8d e2 08 d0 4d e2 90 20 9f e5 05 36 a0 e3 |......M.. ...6..|
0x00000100 00 30 82 e5 88 20 9f e5 0a 36 a0 e3 00 30 82 e5 |.0... ...6...0..|
0x00000110 80 20 9f e5 00 30 a0 e3 00 30 82 e5 78 20 9f e5 |. ...0...0..x ..|
0x00000120 00 30 a0 e3 00 30 82 e5 cc ff ff eb 6c 30 9f e5 |.0...0......l0..|
0x00000130 00 30 93 e5 08 30 0b e5 08 30 1b e5 10 30 c3 e3 |.0...0...0...0..|
0x00000140 08 30 0b e5 54 20 9f e5 08 30 1b e5 00 30 82 e5 |.0..T ...0...0..|
0x00000150 4c 30 9f e5 08 30 0b e5 38 20 9f e5 08 30 1b e5 |L0...0..8 ...0..|
0x00000160 00 30 82 e5 34 30 9f e5 00 30 93 e5 08 30 0b e5 |.0..40...0...0..|
0x00000170 08 30 1b e5 10 30 c3 e3 08 30 0b e5 1c 20 9f e5 |.0...0...0... ..|
0x00000180 08 30 1b e5 00 30 82 e5 04 d0 4b e2 00 88 bd e8 |.0...0....K.....|
0x00000190 38 81 01 80 34 81 01 80 30 00 07 80 38 00 07 80 |8...4...0...8...|
0x000001a0 2c 00 07 80 01 03 00 00 04 b0 2d e5 00 b0 8d e2 |,.........-.....|
0x000001b0 18 30 9f e5 00 30 93 e5 80 30 03 e2 00 00 53 e3 |.0...0...0....S.|
0x000001c0 fa ff ff 0a 00 d0 8b e2 00 08 bd e8 1e ff 2f e1 |............../.|
0x000001d0 18 00 07 80 30 48 2d e9 0c b0 8d e2 f4 40 9f e5 |....0H-......@..|
0x000001e0 04 40 8f e0 f0 30 9f e5 03 30 84 e0 03 00 a0 e1 |.@...0...0......|
0x000001f0 5e 00 00 eb e4 30 9f e5 00 30 93 e5 03 00 a0 e1 |^....0...0......|Go!
Hardware version: 0x00000006
Screen pressed: 0
Setting up LCD to point at 0x44844000
Setting up LCD to point at 0x44844000
Reading 0x00000800 bytes from offset 0x0000b800 to destination 0x45a00000
Skipping 2944 chunks
Read 0 chunks. Trying again...
Comparing block [boot] with img1...
Comparing block [img1] with img1... Found!
Reading 0x00025800 bytes from offset 0x00044000 to destination 0x44844000
Skipping 17408 chunks
Read 0 chunks. Trying again...boot> shell
Chumby bootloader console v1.0
Booting in 2 seconds...
Press any key to enter shell... 0boot> regutil -w HW_RTC_WATCHDOG 0x00004e20
Setting 0x8005c050: 0xffffffff -> 0x00004e20 ok
boot> regutil -w HW_RTC_CTRL_SET 0x00000010
Setting 0x8005c004: 0x00000008 -> 0x00000018 okboot> regutil -w HW_EMI_CTRL 0x1c574040
Setting 0x80020000: 0x1c884040 -> 0x1c574040 okboot> regutil -w HW_POWER_BATTMONITOR 0x01ec0414
Setting 0x800440e0: 0x019b0600 -> 0x01ec0414 okboot> regutil -w HW_POWER_5VCTRL_CLR 0x00000080
Setting 0x80044018: 0x0403f193 -> 0x0403f113 okboot> regutil -w HW_POWER_MINPWR_SET 0x00001000
Setting 0x80044024: 0x00000040 -> 0x00001040 okboot> regutil -w HW_PINCTRL_MUXSEL1_SET 0x03300000
Setting 0x80018114: 0x0fffffff -> 0x0fffffff okboot> regutil -w HW_PINCTRL_DOUT0_CLR 0x24000000
Setting 0x80018508: 0x00000000 -> 0x00000000 okboot> regutil -w HW_PINCTRL_DOE0_SET 0x24000000
Setting 0x80018704: 0x00000000 -> 0x24000000 okboot> regutil -w HW_PINCTRL_DOUT0_CLR 0x24000000
Setting 0x80018508: 0x00000000 -> 0x00000000 okboot> regutil -w HW_PINCTRL_DOUT0_SET 0x20000000
Setting 0x80018504: 0x00000000 -> 0x20000000 okboot> regutil -w HW_PINCTRL_DOUT0_SET 0x04000000
Setting 0x80018504: 0x20000000 -> 0x24000000 ok
Would any of you happen to know what is it trying to do between printing this last message:
Skipping 3968 chunks
and the subsequent statements:
Jumping to address 0x40808000:
because this might hint to what is wrong in the hardware...
I have measured a few voltages, but I am not sure if any of the linear regulators needs to be turned on by software.
Some voltages are good, like these:
VDD_BATT= 4.48V OK!
RAW_PWR = 5.28V OK!
VDDXTAL = 0.96V OK!
VDD5V or VDD_5V = 5.29V OK!
USBH_P33VD = 3.59V OK!
USBH_P33V = 3.59V OK!
But these are not looking good:
When 3V3UART cable is plugged in:
P3.3 = 1.35V NOT OK!!! Should be ~3.3V
When 3V3UART cable is unplugged:
P3.3 = 0.888V NOT OK!!! Should be ~3.3V
DCDC_VDDIO = 1.28V NOT OK!!! Should be ~3.3V, because it is connected to P3.3V rail by R104 which is a zero ohm shunt.
VDDD = 0V NOT OKAY!
P2.5V = 0 (zero) NOT OKAY! Should be ~2.5V
Is the MX233 dead or is there hope?
What really puzzels me is that it can mange to print something in the serial debug line, before dying.
Thanks for reading.
Any help is appreciated!