Difference between revisions of "Diagnostic & repair"

From ElphelWiki
Jump to: navigation, search
(Introduction)
(Introduction)
Line 7: Line 7:
 
The given section of Manual contains the information about the probable malfunctions arising during work of cameras, and ways of their detection and elimination. We hope, that the given section of Manual will be least visited by you.
 
The given section of Manual contains the information about the probable malfunctions arising during work of cameras, and ways of their detection and elimination. We hope, that the given section of Manual will be least visited by you.
  
There is another reason for such section. You see, our hardware is open for hacking - you do not need to make photos of the PCBs and reverse-engineer the circuit diagrams or component placement - it is all ready available for download under the Free Documentation License. So you are welcome to hack into and we'll have some useful tips here on the matter.
+
There is another reason for such section. You see, our hardware is open for hacking - you do not need to make photos of the PCBs and reverse-engineer the circuit diagrams or component placement - it is all ready available for download under the Free Documentation License.
 +
 
 +
Elphel cameras use a very nice feature of [http://www.axis.com Axis Communications] processor - [http://developer.axis.com/products/etrax100lx/index.html ETRAX100LX] - embedded network boot loader. That means that you do not need any special tools/cables or special tricks (as [http://wiki.openwrt.org/OpenWrtDocs/Installing here]) to reprogram the cameras, and even more - you can not screw up the flashing process and make cameras forever non-bootable. The network boot code resides in the CPU ROM so if flashing failed - you can always start over again.
 +
 
 +
So you are welcome to hack into and we'll have some useful tips here on the matter.
  
 
One simple one that I can think of - if you start to modify/rebuild the FPGA code it can be a good idea to hold you finger over the FPGA and/or CPU during FPGA programming - some errors (i.e. forget to include physical constraint file with pins designations) can cause bus conflicts (CPU and FPGA will fight each other) and overheat fast - just unplug the power.
 
One simple one that I can think of - if you start to modify/rebuild the FPGA code it can be a good idea to hold you finger over the FPGA and/or CPU during FPGA programming - some errors (i.e. forget to include physical constraint file with pins designations) can cause bus conflicts (CPU and FPGA will fight each other) and overheat fast - just unplug the power.

Revision as of 14:28, 30 October 2005

Elphel Network Cameras Manual

353/363 | Using the cameras | Camera software | Live CD | Camera hardware | Diagnostic & repair | Development documentation | 333 prices | Information | FAQ | About Elphel, Inc


Introduction

As well as any modern digital devices, in Elphel network cameras the complex hi-tech components is included. We spend a lot of efforts for as possible long term trouble-free working of our cameras, but, unfortunately, any complex technical equipment has property to break.

The given section of Manual contains the information about the probable malfunctions arising during work of cameras, and ways of their detection and elimination. We hope, that the given section of Manual will be least visited by you.

There is another reason for such section. You see, our hardware is open for hacking - you do not need to make photos of the PCBs and reverse-engineer the circuit diagrams or component placement - it is all ready available for download under the Free Documentation License.

Elphel cameras use a very nice feature of Axis Communications processor - ETRAX100LX - embedded network boot loader. That means that you do not need any special tools/cables or special tricks (as here) to reprogram the cameras, and even more - you can not screw up the flashing process and make cameras forever non-bootable. The network boot code resides in the CPU ROM so if flashing failed - you can always start over again.

So you are welcome to hack into and we'll have some useful tips here on the matter.

One simple one that I can think of - if you start to modify/rebuild the FPGA code it can be a good idea to hold you finger over the FPGA and/or CPU during FPGA programming - some errors (i.e. forget to include physical constraint file with pins designations) can cause bus conflicts (CPU and FPGA will fight each other) and overheat fast - just unplug the power.



Free Software and Open Hardware. Elphel, Inc., 2005