Difference between revisions of "Diagnostic & repair"
(→Introduction) |
(→Introduction) |
||
| Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| − | + | Like any modern digital devices, Elphel network cameras include complex hi-tech components. We spend a lot of effort to ensure long term trouble-free working of our cameras, but, unfortunately, any complex technical equipment can break. | |
| − | The | + | The following section of the Manual contains information about possible malfunctions arising during the operation of the cameras, and ways of detecting and eliminating them. We hope that this will be the least visited section of the Manual ! |
| − | There is another reason for such section. You see, our hardware is open for hacking - you do not need to | + | There is another reason for such a section. You see, our hardware is open for hacking - you do not need to take photos of the PCBs and reverse-engineer the circuit diagrams or component placement - it is already 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 | + | Elphel cameras use a very nice feature of the [http://www.axis.com Axis Communications] processor - [http://developer.axis.com/products/etrax100lx/index.html ETRAX100LX] - an 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 furthermore - you cannot screw up the flashing process and make the cameras permanently unbootable. The network boot code resides in the CPU ROM, so if flashing fails - you can always start over again. |
| − | So you are welcome to hack | + | So you are welcome to hack away and we'll have some useful tips here on that matter. |
| − | One simple | + | One simple tip 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. forgetting to include the physical constraint file with the pin designations) can cause bus conflicts (CPU and FPGA will fight each other) and overheat fast - just unplug the power if this happens. |
Revision as of 05:55, 29 December 2005
353/363 | Using the cameras | Camera software | Live CD | Camera hardware | Diagnostic & repair | Development documentation | 333 prices | Information | FAQ | About Elphel, Inc
Introduction
Like any modern digital devices, Elphel network cameras include complex hi-tech components. We spend a lot of effort to ensure long term trouble-free working of our cameras, but, unfortunately, any complex technical equipment can break.
The following section of the Manual contains information about possible malfunctions arising during the operation of the cameras, and ways of detecting and eliminating them. We hope that this will be the least visited section of the Manual !
There is another reason for such a section. You see, our hardware is open for hacking - you do not need to take photos of the PCBs and reverse-engineer the circuit diagrams or component placement - it is already available for download under the Free Documentation License !
Elphel cameras use a very nice feature of the Axis Communications processor - ETRAX100LX - an 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 furthermore - you cannot screw up the flashing process and make the cameras permanently unbootable. The network boot code resides in the CPU ROM, so if flashing fails - you can always start over again.
So you are welcome to hack away and we'll have some useful tips here on that matter.
One simple tip 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. forgetting to include the physical constraint file with the pin designations) can cause bus conflicts (CPU and FPGA will fight each other) and overheat fast - just unplug the power if this happens.
Free Software and Open Hardware. Elphel, Inc., 2005
