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: I deleted Image: 0 name:BOOT INFO. Could anyone send it to me.  (Read 52606 times)

June 27, 2011, 09:25:18 pm
ARNING: Image 0 was not found. Try to create one ...
.Image 0 created


W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Dec 10 2009
Memory Size is 0x1000000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.


For help on the available commands type 'h'

Press ESC to enter debug mode ......
ERROR: Image 0 not found


ERROR: Data Abort @ pc=0x00001680
bootloader > ls
Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000048 exec:0x7F010000 -af

bootloader >

  • *****
June 27, 2011, 09:32:10 pm
Uboot thinks that it successfully created image 0. Whatever ls checks leads it to believe that it sees a valid image 0. Yet, other tests (ERROR: Data Abort @ pc=0x00001680) make it appear that image 0 is corrupted. Seems like read or write errors with the flash or ram, to me.

  • *****
June 27, 2011, 09:39:30 pm
casbeto,

You say loading my image 0 yields:
Code: [Select]
bootloader> fx 0 bootinfo.bin 0x7F010000 0x7F010000 -f
 Waiting for download ...

Does it hang and never progress beyond the "Waiting for download ..." message?
Does the xmodem block count progress on your PC?

June 27, 2011, 09:39:40 pm
it all started when I put this command: fx 7 linux.zip 0x7f020000 0x8000 -acxz

 when the truth would be: fx 7 linux.zip 0x7f020000 0x00008000 -acxz
« Last Edit: June 27, 2011, 09:41:39 pm by casbeto »

June 27, 2011, 10:04:09 pm
celem has a command to clear the references below?

bootloader > d -b 0x00008000
Displaying memory at 0x8000
[00008000] 00 11 A0 20 48 82 03 C0 - 85 45 04 42 40 E0 80 23  ....H....E.B@..#
[00008010] 42 61 50 D4 68 D0 80 26 - 00 C0 84 97 08 09 85 0C  BaP.h..&........
[00008020] A8 98 42 18 02 49 30 9A - 28 2A 48 87 D1 61 03 1A  ..B..I0.(*H..a..
[00008030] 38 06 C0 2A 28 81 02 A6 - 85 91 7A C4 26 06 3D 14  8..*(.....z.&.=.
[00008040] 88 A8 A4 35 80 02 30 40 - A8 0B 20 20 10 39 1A 31  ...5..0@.....9.1
[00008050] 30 C2 00 44 00 8C 48 A8 - F0 62 21 01 EB 91 12 B0  0..D..H..b!.....
[00008060] 60 05 10 40 81 04 CA C0 - 36 BE 9C 0A 85 A5 2C 0F  `..@....6.....,.
[00008070] 1A 33 22 EF 8A 71 06 10 - 22 12 24 02 67 87 A0 00  .3"..q..".$.g...
[00008080] 25 8A 98 4A 51 4C 09 62 - 41 D9 1C 09 21 11 26 02  %..JQL.bA...!.&.
[00008090] 90 5C B8 94 8D 12 62 81 - 08 3A 8E B0 BA 1C F4 92  .\....b..:......
[000080A0] B6 98 44 7D 81 BB 40 81 - D2 82 26 03 21 22 10 18  ..D}..@...&.!"..
[000080B0] C2 88 60 93 01 94 02 43 - B8 08 E0 42 86 85 2E 26  ..`....C...B...&
[000080C0] 01 27 49 17 B2 04 09 43 - 08 B6 C2 AA CC 86 40 81  .'I....C......@.
[000080D0] 00 84 84 42 21 AE 05 F0 - 82 E6 EC 40 1E 02 96 22  ...B!......@..."
[000080E0] E6 14 D8 CC C2 48 09 E5 - E4 48 44 E6 65 12 9A 13  .....H...HD.e...
[000080F0] 13 28 52 BB BD 23 21 23 - 38 01 8A D8 8C 20 A0 AC  .(R..#!#8.......

bootloader >

  • *****
June 27, 2011, 10:15:07 pm
0x00008000 is a RAM address. Given that, upon each boot, RAM is reloaded by uboot from the flash images, I don't see how this is relevant. Additionally, 0x00008000 and 0x8000 are the same.

I still suspect a flash or ram issue.

Here is what I have:
Code: [Select]
bootloader > d -b 0x8000
Displaying memory at 0x8000
[00008000] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008010] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008020] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008030] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008040] AA AA A2 AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008050] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008060] AA AA AA AA AA AA AA AA - AA AA AA AA AA 2A AA AA  .............*..
[00008070] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008080] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[00008090] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[000080A0] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[000080B0] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[000080C0] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA AA  ................
[000080D0] AA AA AA AA AA AA AA AA - AA AA AA AA AA AA AA A2  ................
[000080E0] AA AA AA AA AA AA AA AA - A2 AA AA AA AA AA AA AA  ................
[000080F0] AA AA AA AA AA AA AA AA - AA AA AA AA 2A AA AA AA  ............*...

You did not answer my previous question - You say loading my image 0 yields:
Code: [Select]
bootloader> fx 0 bootinfo.bin 0x7F010000 0x7F010000 -f
 Waiting for download ...

Does it hang and never progress beyond the "Waiting for download ..." message?
Does the xmodem block count progress on your PC?


June 27, 2011, 10:20:19 pm
celem, after using it I saw that Mac was reset, boot and there I could no longer enter.

 it hangs at Waiting for download!


celem, what is the command mx? accepted this and asked to send the file.


bootloader > mx 0x8000
Waiting for download
Press Ctrl-x to cancel ...
CCC
« Last Edit: June 27, 2011, 10:39:41 pm by casbeto »

  • *****
June 27, 2011, 10:38:56 pm
Here is what is in image 0:
Code: [Select]
Note: the base address is 0x7F010000 - add 0x7F010000to the addresses shown:

$ hd bootinfo.bin
00000000  48 00 00 00 01 00 00 00  00 b8 00 00 68 d2 c0 a8  |H...........h...|
00000010  00 b2 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  01 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  |................|
00000030  00 00 30 00 00 00 10 00  00 c2 01 00 ff ff ff ff  |..0.............|
00000040  ff ff ff ff 01 00 00 00  ff ff ff ff ff ff ff ff  |................|
00000050  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
0000ffc0  ff ff ff ff ff ff ff ff  ff ff ff ff 00 00 00 00  |................|
0000ffd0  00 00 01 7f 48 00 00 00  00 00 01 7f 00 00 01 7f  |....H...........|
0000ffe0  42 4f 4f 54 20 49 4e 46  4f 00 00 7f 78 00 00 00  |BOOT INFO...x...|
0000fff0  4b 01 fc 56 9f ff ff a0  08 00 00 00 99 65 63 71  |K..V.........ecq|

The MAC is in the first 48 bytes. The image parameters are at the end of the 65k, as you can see above. In between is nothing. I suspect a flash problem up near the end.

June 27, 2011, 10:43:13 pm
celem, what is the command mx? accepted this and asked to send the file.

bootloader > mx 0x8000
Waiting for download
Press Ctrl-x to cancel ...
CCC

  • *****
June 27, 2011, 10:49:00 pm
Downloads to ram via xmodem. For example,

Code: [Select]
mx 0x8000
Loads the image that you send via xmodem into RAM starting at 0x8000.

  • *****
June 27, 2011, 10:49:56 pm
So, loading to RAM works but loading to Flash fails!

June 27, 2011, 10:57:28 pm
I think we have to end here! 've tried everything and failed, but this post with your knowledge will help many people who have problems like mine.

 thanks for your help, thank you for everything my friend, I will order one from china.

 sds,
 Carlos Alberto
 Sao Paulo - Brazil

  • *****
June 27, 2011, 11:00:24 pm
OK. Rather than make it a doorstop, try loading the kernel e/w busybox that Lawrence posted somewhere on this forum. You could try to load it straight to RAM @ 0x8000 via mx and then execute it with G 0x8000

You never said what brand of camera your was?

June 27, 2011, 11:11:34 pm
Sorry my camera and Chinavasion ES_IP607_ARM_2 (20091216), I'll try what you said to get something, post it here for you also know, thanks!

  • *****
June 27, 2011, 11:29:57 pm
This might work.

Download Lawrence's kernel e/w busybox:
http://www.openipcam.com/files/Firmware/Testing/romfs745_busybox_openipcam_v1.img

This file has a header that will probably need to be stripped off. Lawrence discusses this, somewhere in the forum, how to do this.

Load from your PC directly to RAM via xmodem with:
mx 0x8000

Execute the image by ‘g 0x8000’ command.
bootloader > g 0x8000

If it works, you'll have a nice Linux interface with busybox as your shell. No gui, of course. Also, if this works, it really points to the flash as being bad.
« Last Edit: June 27, 2011, 11:32:27 pm by celem »