Upgrading the image via serial on 9100
Goto page Previous  1, 2, 3  Next
 
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    Yoics Support Forums Forum Index -> Misc Yoics Enabled Devices
View previous topic :: View next topic  
Author Message
dejuh



Joined: 22 Jul 2007
Posts: 8

PostPosted: Sun Jul 29, 2007 3:30 am    Post subject: Reply with quote

hello mycal,
I did not muste upgraden again and again and in the end run yoics9100a_2_41_d now it super only zoneminder less wants yet.
greet Dejuh
Back to top
View user's profile Send private message Send e-mail
doubletop



Joined: 08 Aug 2008
Posts: 8

PostPosted: Wed Aug 13, 2008 4:41 am    Post subject: Reply with quote

Mycal - Thanks for pointing me at this post

My IP9100 is V2.38 which I had upgraded to V2.39

I have downloaded both the linux.zip and 9100a.bin files.

As I had 2.46 loaded my ls had linux at 0x7F020000 and romfs at 0x7F0A0000. I notice that in a previous post you had the romfs at 0x7F0C0000 but your instructions say load to 0x7F0A00.

Il loaded 9100a.bin romfs to 0x7F0A00 but linux couldn't find it. So I tried it to 0x7F0C000 and that didn't work either.

I get the error dejuth had

Blkmem: bad access: block=0, count=2 (pos=400, len=0)
end_request: I/O error, dev 1f:00 (Blkmem), sector 0
romfs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 1f:00

As dejuh fixed his system by reloading linux I tried that but I still get the same problem. when I load 9100a.bin to either address

I read somewhere that the Aviosys files contain the complete image. So do you know the command line to load that file so I can get the thing back to a known working state?
Back to top
View user's profile Send private message
mycal



Joined: 03 Dec 2006
Posts: 601

PostPosted: Wed Aug 13, 2008 11:41 am    Post subject: Reply with quote

Older versions of 9100 used a different linux.zip.

Thats why it is a real bad idea to include this in the flash upgrade
as aviosys does.

As long as you have the correct linux.zip for your model you should not get the error. We should double check that the linux.zip on the site is for the post V2.34 models.

also in the boot loader you can dump memory, dump the first few
lines of the image that you loaded and post it back.

-M
Back to top
View user's profile Send private message AIM Address
doubletop



Joined: 08 Aug 2008
Posts: 8

PostPosted: Wed Aug 13, 2008 11:59 pm    Post subject: Reply with quote

Here's the details

9100a V2.38

Have loaded Linux.zip and 9100a files provided in this post

Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000038 exec:0x7F010000 -af
Image: 7 name:linux.bin base:0x7F020000 size:0x00078480 exec:0x00008000 -acxz
Image: 6 name:romfs.img base:0x7F0A0000 size:0x00139480 exec:0x7F0A0000 -a

Displaying memory at 0x7F020000
[7F020000] 04034B50 00000014 - 04560008 1B37356F PK........V.o57.
[7F020010] 83A1F76C E6380007 - 0009000F 696C0000 l.....8.......li
[7F020020] 2E78756E EC6E6962 - 54780DBD BC3FB5D5 nux.bin...xT..?.
[7F020030] 93247CCF 5F272430 - 01CA2112 F5188DA2 .|$.0$'_.!......
[7F020040] 8D234100 2A54483A - 48080751 D041B52D .A#.:HT*Q..H-.A.
[7F020050] 2A3516D2 D52DE96D - 034827C9 C51F0806 ..5*m.-..'H.....
[7F020060] ED2B1CD4 DEF4BDA5 - D72DA5B4 C1477B4B ..+.......-.K{G.
[7F020070] B16C5A96 DB5A96D2 - 69C3399E DA6B4242 .Zl...Z..9.iBBk.
[7F020080] 3A954ADA F7B7EFEF - 68886499 7FFBEFBD .J.:.....d.h...
[7F020090] BCFBCFFF 9B0F3FCF - 7D9F673D 6BDAE7F6 .....?..=g.}...k
[7F0200A0] DAF6B5AF 95B8896B - C95BA7D8 14958497 ....k.....[.....
[7F0200B0] 15129343 869CC7D1 - 45FADB29 C4864AC4 C.......)..E.J..
[7F0200C0] D22044A2 95267556 - F46E559A 7768C2B8 .D..Vu&..Un...hw
[7F0200D0] 67C819F7 5E8AEA3C - 26A3792B E8F72206 ...g<..^+y.&."..
[7F0200E0] BABDC562 8A14B688 - 9E22C406 FAE9B42F b........."./...
[7F0200F0] 18858BF4 B2566214 - 49FE5851 94CEE442 .....bV.QX.IB...

Displaying memory at 0x7F0A0000
[7F0A0000] 47454E42 00000001 - 00000000 00000000 BNEG............
[7F0A0010] 00139400 6D6F722D - 2D736631 00921300 ....-rom1fs-....
[7F0A0020] 42D59049 206D6F72 - 38343634 61373462 I..Brom.4648b47a
[7F0A0030] 00000000 49000000 - 20000000 00000000 .......I........
[7F0A0040] 97FFFFD1 0000002E - 00000000 00000000 ................
[7F0A0050] 00000000 60000000 - 20000000 00000000 .......`........
[7F0A0060] 80FFD1D1 00002E2E - 00000000 00000000 ................
[7F0A0070] 00000000 A98F0800 - 80000000 00000000 ................
[7F0A0080] D7018E9D 006E6962 - 00000000 00000000 ....bin.........
[7F0A0090] 00000000 A0000000 - 60000000 00000000 ...........`....
[7F0A00A0] 00FFFFD1 0000002E - 00000000 00000000 ................
[7F0A00B0] 00000000 C0000000 - 20000000 00000000 ................
[7F0A00C0] 20FFD1D1 00002E2E - 00000000 00000000 ................
[7F0A00D0] 00000000 EA920000 - 00000000 FA910000 ................
[7F0A00E0] 1CDB968C 00006873 - 00000000 00000000 ....sh..........
[7F0A00F0] 00000000 544C4662 - 04000000 40000000 ....bFLT.......@


I have available these files

9100_EN_IE_V239-A.bin
9100a_2_46.bin
9100a_2_47.bin
9100a.bin
linux.bin

which do you suggest I load and to what location?
Back to top
View user's profile Send private message
doubletop



Joined: 08 Aug 2008
Posts: 8

PostPosted: Fri Aug 15, 2008 9:44 pm    Post subject: Reply with quote

I've tried all the combinations of romfs files loaded to 0x7f0a0000 and 0x7f0c0000 and re-down loaded linux.zip and I still get the

Blkmem: bad access: block=0, count=2 (pos=400, len=0)
end_request: I/O error, dev 1f:00 (Blkmem), sector 0
romfs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 1f:00

When linux boots it indicates I have this version of linux.zip

Executing image 7 ...
Linux version 2.4.20-uc0 (mike@xxxx.net) (gcc version 3.0) #956 Wed Nov 15 00:2
8:23 PST 2006

it also finds the romfs

Blkmem 1 disk images:
0: 7F0C0000-7F0BFFFF [VIRTUAL 7F0C0000-7F0BFFFF] (RO)

but I always get the unable to read superblock error.

my device came with V2.38

Any answers
Back to top
View user's profile Send private message
doubletop



Joined: 08 Aug 2008
Posts: 8

PostPosted: Sat Aug 16, 2008 11:38 pm    Post subject: Reply with quote

I've fixed it

The start of the 9100a romfs file loaded from this post looks like this

[7F0A0000] 47454E42 00000001 - 00000000 00000000 BNEG............
[7F0A0010] 00139400 6D6F722D - 2D736631 00921300 ....-rom1fs-...

however the "-romfs-" tag is offset by 0x14

so I used the line

fx 6 romfs.img 0x7f0a0000 0x7f0a0014 -a

the system then rebooted correctly (just about, as it crashed after a while) but a second reboot and the webpages came up OK and I could reload 2.39 and get back to a clean start.
Back to top
View user's profile Send private message
mycal



Joined: 03 Dec 2006
Posts: 601

PostPosted: Sun Aug 17, 2008 7:44 am    Post subject: Reply with quote

Nice! I'm glad you got it all working.

-M
Back to top
View user's profile Send private message AIM Address
doubletop



Joined: 08 Aug 2008
Posts: 8

PostPosted: Sun Aug 17, 2008 12:21 pm    Post subject: Reply with quote

Thanks for your help on this

P
Back to top
View user's profile Send private message
gabonator



Joined: 03 Jul 2008
Posts: 3
Location: Slovakia

PostPosted: Wed Aug 27, 2008 11:20 pm    Post subject: IP9100a dead? Reply with quote

My device was running quite long time. Sometimes after 4-5 days it hanged and I just reconnected the power cord and device was running again. Unfortunatelly the device is not running anymore - When I connect it with ethernet cable to PC, ipedit.exe utility cannot find any video devices. The network connection looks ok, only the device does not respond to ipedit or ping command. Ethernet connector leds are blinking so I thought I can fix this problem by flashing the internal memory trough internal 4 pin UART header. I followed the manual in this thread - deletion of image 6. and 7. After running "fx 7 linux.bin 0x7F020000 0x00008000 -acxz" command, the transfer command could not finish. After 1024 bytes the transfer stopped. Then I tried to transfer the image through TFTP (http://www.solivant.com/9100aplus/) but immediatelly I connect ethernet cable to PC, the terminal stopps responding. Then I tried to set the IP manually (set -ip0 192.168.1.55) and after reboot I was not able to ping it from PC.

The terminal I use is Tera Term and UART converter is homemade MAX232 + RS232->USB converter. Maybe it is the problem of terminal software, but HyperTerminal is not present on this PC. Please help
Back to top
View user's profile Send private message
gabonator



Joined: 03 Jul 2008
Posts: 3
Location: Slovakia

PostPosted: Sat Aug 30, 2008 11:32 pm    Post subject: Reply with quote

Ok, that was my fault. With the hyperterminal the image upload went ok. After flashing it worked about one day, and now I am having similar problem... When booting, it suddenly stopps working, the boot messages are coming through serial and in some point, only few blank lines (1 blank line per second) came and then two random characters. After this, the device is dead and not responding. The ethernet leds are blinking in normal way.

When I try to flash the linux.zip image, after xmodem transfer it doesnt respond "Flashing image........" as it should, instead it respods in same way I described above. Few blank lines with two messed characters.

I have bad feeling the flash memory is damaged


edit: Here is the comm log: http://gabonator.yweb.sk/dead.txt
Back to top
View user's profile Send private message
mycal



Joined: 03 Dec 2006
Posts: 601

PostPosted: Sun Aug 31, 2008 1:13 am    Post subject: Reply with quote

I've seen quite a few 9100's die or get flaky. If it is in a hot environment
try getting it cooler. It does seem heat related.

Sometimes the ADC just dies and it will boot but no video.

Other times I've seen them get into a state like you describe.

try cooling it down and see if you can get back into the bootloader and
reload it.

-M
Back to top
View user's profile Send private message AIM Address
gabonator



Joined: 03 Jul 2008
Posts: 3
Location: Slovakia

PostPosted: Mon Sep 01, 2008 1:44 am    Post subject: next time... Reply with quote

Thanks for reply,
it seems that it was my fault again. When flashing, the device was connected to laboratory supply set to 5.0V, when I increased the voltage to 6.0V flashing went without any problems.

I am just wondering, what is the purpose of the on/off switch and reset button. Because it seems that the device does not respond on the reset, and the device is always on - ignoring the position of the switch. I would like to make a hardware watchdog that would restart the device when it freezes. The yoics firmware is sending every few seconds a debug messages, so when there is no activity on UART for more than 10 seconds, it should cause software reset. But how to reset the device, when the reset button does not respond ?

The videoserver is connected to router (wl500g premium), and in the router is a script that takes every 5 seconds a picture from camera and stores it on USB flashdisk. Every day at 3:00 the router runs a script that packs all the files from previous day into single zip file. And on home-PC (Win XP) is every day executed a batch file that downloads this zip file and convert into MPEG video + subtitle file (mencoder) and this is copyied back to USB harddrive attached on router. I dont know whether taking picture every 5 seconds from the 9100a is too much, and sometimes the device cannot handle more http sessions and simply freezes...

Currently it is only taking one picture from one camera every 5 seconds, I was planning to extend it to 4 pictures from all cameras per 12 seconds. (from each camera in 3 seconds intervals). But first I need to solve these stupid problems.

I will put a cooling fan on the device, but I dont believe it will change anything.

And the last question - what firmware (and where) should I download, when I dont want the motion detection and telnet daemon ? Maybe the device is only running out of memory... Currently I am using 9100a_2_47.bin
Back to top
View user's profile Send private message
mycal



Joined: 03 Dec 2006
Posts: 601

PostPosted: Mon Sep 01, 2008 3:19 pm    Post subject: Reply with quote

The reset button is not for resetting the device, but resetting the
device to factory defaults. Pressing it for 10 seconds with a paper clip will cause it to reboot to factory default settings, it does not act like a hardware reset button on a PC. The on off switch is just that and should work.

If your not doing motion detection, then a properly cooled and powered 9100 should stay up indefinably, I have one up 1.5 years running a zoneminder backed, and it is grabbing 4 cameras at a couple fps for each camera.

I don't know if any of the current firmware releases don't have telnet enabled. Maybe next release I can do both.

-M
Back to top
View user's profile Send private message AIM Address
suncity



Joined: 22 Oct 2008
Posts: 3

PostPosted: Wed Oct 22, 2008 10:49 am    Post subject: Reply with quote

First, Thank you to all who have contributed to this thread as it has been quite helpful in gaining additional insight into the 9100a.

My 9100a stopped picking up an ip address. I reloaded the firmware per the instructions in this thread (I needed doubletops x14 offset) but I am now getting an error during boot. The 9100a is still not picking up an ip address, but, it is booting. the error is listed below. Thank you in advance to any assistance you may be able to provide!!





W90N740 Boot Loader [ Version 1.1 $Revision: 6 $ ] Rebuilt on Sep 26 2003

Running on a W90N740 Evaluation Board

Board Revision 1.0, W90N740 MCU

Memory Size is 0x800000 Bytes, Flash Size is 0x200000 Bytes

Board designed by Winbond

Hardware support provided at Winbond

Copyright (c) Winbond Limited 2001 - 2003. All rights reserved.

Boot Loader Configuration:


TFTP server port : MAC 1

Network phy chip : DAVICOM DM9161E

MAC 0 Address : 00:69:70:63:6D:21

IP 0 Address : 0.0.0.0

MAC 1 Address : 00:91:00:00:5E:C6

IP 1 Address : 0.0.0.0

DHCP Client : Enabled

CACHE : Enabled

BL buffer base : 0x00300000

BL buffer size : 0x00100000

Default baud rate : -1



For help on the available commands type 'h'


Press ESC to enter debug mode ......

Cache enabled!

Processing image 1 ...

Processing image 2 ...

Processing image 3 ...

Processing image 4 ...

Processing image 5 ...

Processing image 6 ...

Processing image 7 ...

Unzip image 7 ...

Executing image 7 ...

Linux version 2.4.20-uc0 (mike@xxxxx.net) (gcc version 3.0) #956 Wed Nov 15 00:28:23 PST 2006

Processor: Winbond W90N740 revision 1

Architecture: W90N740

On node 0 totalpages: 2048

zone(0): 0 pages.

zone(1): 2048 pages.

zone(2): 0 pages.

Kernel command line: root=/dev/rom0

Calibrating delay loop... 39.83 BogoMIPS

Memory: 7MB = 7MB total

Memory: 5880KB available (920K code, 192K data, 40K init)

Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)

Inode cache hash table entries: 512 (order: 0, 4096 bytes)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)

Page-cache hash table entries: 2048 (order: 1, 8192 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

Winbond W90N740 Serial driver version 0.9 (2001-12-27) with no serial options enabled

ttyS00 at 0xfff80000 (irq = 6) is a W90N740

Blkmem copyright 1998,1999 D. Jeff Dionne

Blkmem copyright 1998 Kenneth Albanowski

Blkmem 1 disk images:

0: 7F0A0014-7F1D9413 [VIRTUAL 7F0A0014-7F1D9413] (RO)

RAMDISK driver initialized: 16 RAM disks of 1024K size 1024 blocksize

loop: loaded (max 8 devices)

The flash size:0x00200000

Boot Loader Configuration:


TFTP server port : MAC 1

Network phy chip : PHY

MAC 0 Address : 00:69:70:63:6d:21

IP 0 Address : 0.0.0.0

MAC 1 Address : 00:91:00:00:5e:c6

IP 1 Address : 0.0.0.0

DHCP Client : Enabled

CACHE : Enabled

01 eth0 initial ok!

which:0

01 eth1 initial ok!

which:1

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

PPP BSD Compression module registered

Linux video capture interface: v1.00

Welcome wireless network! Smile

GPIO: 50d0

wireless driver reset failed, dfbe

prism: error -5 registering device "wlan0"

AM29LV160DB Flash Detected

usb.c: registered new driver hub

add a static ohci host controller device

: USB OHCI at membase 0xfff05000, IRQ 9

hc_alloc_ohci

usb-ohci.c: AMD756 erratum 4 workaround

hc_reset

usb.c: new USB bus registered, assigned bus number 1

hub.c: USB hub found

hub.c: 2 ports detected

usb.c: registered new driver audio

audio.c: v1.0.0:USB Audio Class driver

usb.c: registered new driver W99683

W99683.c: v1.00 for Linux 2.4 : W99683 USB Camera Driver

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 512 bind 1024)

VFS: Mounted root (romfs filesystem) readonly.

Freeing init memory: 40K

Shell invoked to run file: -t
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc/Html/Reboot
Command: cp /etc/Html/Simple/Reboot.htm /etc/Html/Reboot/Reboot.htm
Command: cp /etc/yoics_img.jpg /usr/yoics0.jpg
Command: cp /etc/yoics_img.jpg /usr/yoics1.jpg
Command: cp /etc/yoics_img.jpg /usr/yoics2.jpg
Command: cp /etc/yoics_img.jpg /usr/yoics3.jpg
Command: ifconfig lo 127.0.0.1
Command: #ifconfig eth1 hw ether 00:1c:2a:42:46:11
Command: ifconfig eth1 up
MiiStationWrite 1

MiiStationWrite 1


Wait for auto-negotiation complete...ResetPhyChip Failed

SIOCSIFFLAGS: Unknown error 1
Back to top
View user's profile Send private message
suncity



Joined: 22 Oct 2008
Posts: 3

PostPosted: Wed Oct 22, 2008 11:47 am    Post subject: Reply with quote

continued from above.............................................................

SIOCSIFFLAGS: Unknown error 1
Command: camera.flat&
[15]
Command: mctest&
[16]
Command: inetd&
[17]
Command: splitter&
9100a Video Server Stream Splitter Startup V0.3 Alpha
--(c)2006 Yoics Inc. All Rights Reserved.
sleep
2003/2/1 0:0:0
Total size 5572
Web Camera Version: Oct 25 2004 15:24:59
.
Camera config file: length error!
Can not get config parameters, use factory-default instead.
*pIpParam=36
ReadCameraINI count=5568
MCTEST:SendRequest:NetConnect error
MCTEST:SendRequest:NetConnect error
MCTEST:SendRequest:NetConnect error
MCTEST:SendRequest:NetConnect error
[18]
Command: yoicsd -f /bin/yoics.txt &
[19]
Command: sh
config file /bin/yoics.txt
Computer MAC for eth1 = 00:00:00:91:00:00:5e:c6
Using server server1.yoics.net on port 5959
Using device uid = 00:00:00:91:00:00:5e:c6

Sash command shell (version 1.1.1)
/> Initializing eth1...
MiiStationWrite 1
MiiStationWrite 1

Wait for auto-negotiation complete...
ResetPhyChip Failed
/> SIOCSIFFLAGS: Operation not permitted

/>
/>
/> Starting up...
-connecting to target..
error in connect error= 111
-connecting to target..
perror in connect error= 111
TCP connect Fail
sleep
s
PID PORT STAT SIZE SHARED %CPU COMMAND
1 S 150K 0K 17.2 /bin/sh -t /bin/inittab
2 S 0K 0K 0.0 keventd
3 R 0K 0K 0.0 ksoftirqd_CPU0
4 S 0K 0K 0.0 kswapd
5 S 0K 0K 0.0 bdflush
6 S 0K 0K 0.0 kupdated
7 S 0K 0K 0.0 khubd
15 S 1033K 0K 80.0 camera.flat
16 S 86K 0K 1.8 mctest
17 S 41K 0K 0.2 inetd
18 S 69K 0K 1.2 splitter
19 S 270K 0K 3.2 yoicsd -f /bin/yoics.txt
20 R 137K 0K 3.8 sh
/> Initializing eth1...
MiiStationWrite 1
MiiStationWrite 1

Wait for auto-negotiation complete...help
ResetPhyChip Failed
-connecting to target..
error in connect error= 111
-connecting to target..
error in connect error= 111
TCP connect Fail
sleep
cd [dirname]
sleep seconds
chgrp gid filename ...
chmod mode filename ...
chown uid filename ...
cmp filename1 filename2
cp srcname ... destname
df [file-system]
echo [args] ...
exec filename [args]
exit
free
help
hexdump [-s] filename
hostname [hostname]
kill [-sig] pid ...
ln [-s] srcname ... destname
ls [-lidC] filename ...
mkdir dirname ...
mknod filename type major minor
more filename ...
mount [-t type] devname dirname
mv srcname ... destname
printenv [name]
pwd
pid
quit
rm filename ...
rmdir dirname ...
setenv name value
source filename
sync
touch filename ...
umask [mask]
umount filename
ps
cat filename ...
date date [MMDDhhmm[YYYY]]
/> SIOCSIFFLAGS: Operation not permitted
Initializing eth1...
MiiStationWrite 1
MiiStationWrite 1

Wait for auto-negotiation complete...ResetPhyChip Failed
-connecting to target..
error in connect error= 111
-connecting to target..
error in connect error= 111
TCP connect Fail
sleep
SIOCSIFFLAGS: Operation not permitted
Initializing eth1...
MiiStationWrite 1
MiiStationWrite 1

Wait for auto-negotiation complete...
Back to top
View user's profile Send private message
Display posts from previous:   
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    Yoics Support Forums Forum Index -> Misc Yoics Enabled Devices All times are GMT - 7 Hours
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum