News:

Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at http://www.computersolutions.cn/blog

Author Topic: Recovering Siepem S6211-WR - Ingenic T10 based  (Read 741 times)

  • No avatar
  • *
August 16, 2017, 02:22:38 am
Been lurking for a while but now I need a little guidance as I actually make the vital keystrokes that will hopefully restore this camera.

It's nothing special but I picked it up cheap and ran it for a few days until I noticed heavy traffic when I knew no one was watching a stream. I decided to unplug it and do some securing of the network at a later date. When I went to finally turn it on, it did not move and the LAN lights would come on for a few seconds, and then appear to reset.

I'm to U-Boot and if anyone needs TX/RX pics, let me know but, I'm not sure how to get anything useful onto the camera. Here is the output with one boot cycle and then me halting it:

Code: [Select]
U-Boot SPL 2013.07 (Feb 27 2016 - 10:34:09)
pll_init:347
l2cache_clk = 450000000
pll_cfg.pdiv = 8, pll_cfg.h2div = 4, pll_cfg.h0div = 4, pll_cfg.cdiv = 1, pll_cfg.l2div = 3
nf=38 nr = 1 od0 = 1 od1 = 1
cppcr is 02604900
CPM_CPAPCR 04b0890d
nf=50 nr = 1 od0 = 1 od1 = 1
cppcr is 03204900
CPM_CPMPCR 0320490d
cppcr 0x9a7b5510
apll_freq 909312000
mpll_freq 1200000000
ddr sel mpll, cpu sel apll
ddrfreq 400000000
cclk  909312000
l2clk 303104000
h0clk 300000000
h2clk 300000000
pclk  150000000
CPM_DDRCDR(0000002c) = a0000002


U-Boot 2013.07 (Feb 27 2016 - 10:34:09)

Board: ISVP (Ingenic XBurst T10 SoC)
DRAM:  64 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 402k for U-Boot at: 83f98000
Reserving 32784k for malloc() at: 81f94000
Reserving 32 Bytes for Board Info at: 81f93fe0
Reserving 124 Bytes for Global Data at: 81f93f64
Reserving 128k for boot params() at: 81f73f64
Stack Pointer at: 81f73f48
Now running in RAM - U-Boot at: 83f98000
MMC:
the manufacturer c2
SF: Detected MX25L64**E

In:    serial
Out:   serial
Err:   serial
Net:   CPM_MACCDR(54) = a0000017
Jz4775-9161
Hit any key to stop autoboot:  0
the manufacturer c2
SF: Detected MX25L64**E

SF: 2883584 bytes @ 0x40000 Read: OK
## Booting kernel from Legacy Image at 80600000 ...
   Image Name:   Linux-3.10.14
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    2344413 Bytes = 2.2 MiB
   Load Address: 80010000
   Entry Point:  80404510
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.14 (root@aplink-desktop) (gcc version 4.7.2 (Ingenic 2015.02) ) #12 PREEMPT Sat Feb 27 10:32:49 CST 2016
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 RESET ERROR PC:B5C818FF
[    0.000000] CPU0 revision is: 00d00100 (Ingenic Xburst)
[    0.000000] FPU revision is: 00b70000
[    0.000000] CCLK:909MHz L2CLK:454Mhz H0CLK:200MHz H2CLK:200Mhz PCLK:100Mhz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 004c8000 @ 00010000 (usable)
[    0.000000]  memory: 00038000 @ 004d8000 (usable after init)
[    0.926159] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.936018] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[    0.944632] Rebooting in 3 seconds..Restarting after 4 ms

U-Boot SPL 2013.07 (Feb 27 2016 - 10:34:09)
pll_init:347
l2cache_clk = 450000000
pll_cfg.pdiv = 8, pll_cfg.h2div = 4, pll_cfg.h0div = 4, pll_cfg.cdiv = 1, pll_cfg.l2div = 3
nf=38 nr = 1 od0 = 1 od1 = 1
cppcr is 02604900
CPM_CPAPCR 04b0890d
nf=50 nr = 1 od0 = 1 od1 = 1
cppcr is 03204900
CPM_CPMPCR 0320490d
cppcr 0x9a7b5510
apll_freq 909312000
mpll_freq 1200000000
ddr sel mpll, cpu sel apll
ddrfreq 400000000
cclk  909312000
l2clk 303104000
h0clk 300000000
h2clk 300000000
pclk  150000000
CPM_DDRCDR(0000002c) = a0000002


U-Boot 2013.07 (Feb 27 2016 - 10:34:09)

Board: ISVP (Ingenic XBurst T10 SoC)
DRAM:  64 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 402k for U-Boot at: 83f98000
Reserving 32784k for malloc() at: 81f94000
Reserving 32 Bytes for Board Info at: 81f93fe0
Reserving 124 Bytes for Global Data at: 81f93f64
Reserving 128k for boot params() at: 81f73f64
Stack Pointer at: 81f73f48
Now running in RAM - U-Boot at: 83f98000
MMC:
the manufacturer c2
SF: Detected MX25L64**E

In:    serial
Out:   serial
Err:   serial
Net:   CPM_MACCDR(54) = a0000017
Jz4775-9161
Hit any key to stop autoboot:  0
isvp#

I found several Russian sites with directions for restoring cameras based on the Ingenic T10 but the one in particular that seemed most promising had broken links for the useful files. https://4pda.ru/forum/index.php?showtopic=807259
Google Translated: https://translate.googleusercontent.com/translate_c?depth=1&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=auto&sp=nmt4&tl=en&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D807259&usg=ALkJrhijolnhxY_Mh_50EBQh78Ced5YPtQ

My hopeful find was that Siepem has a Github where they apparently just dumped a bunch of files so, I'm hoping someone can point me to what is useful and how I should go about pushing something useful to the camera. https://github.com/siepem/cdonline
« Last Edit: August 16, 2017, 02:26:25 am by Chachi »

  • No avatar
  • *****
August 21, 2017, 08:15:37 pm
Haven't seen an ingenic SoC in a while.  One of the few MIPS processors left in the market, everything else is ARM...
Have done a bit of work on their older stuff (JZ4755 SoC), good documentation, shame the company got bought out.

Boot shows
[    0.936018] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)


Make sure you have a valid root file system wherever it needs to be in flash.
Not much clue where it should be from this (although we do have locations for other stuff).


Top of RAM usable for U-Boot at: 84000000
Reserving 402k for U-Boot at: 83f98000
Reserving 32784k for malloc() at: 81f94000
Reserving 32 Bytes for Board Info at: 81f93fe0
Reserving 124 Bytes for Global Data at: 81f93f64
Reserving 128k for boot params() at: 81f73f64


Suggest check in the uBoot to see if you can list partition locations, and work out where a FS ought to be.
You'll then need to make one, and copy over to the uBoot software to flash.

See what uBoot commands you have in order to check first.
Also suggest read up about uBoot.
« Last Edit: August 25, 2017, 11:51:39 am by admin »