Ok thanks.
I was able to start camogm manually but it wasn't starting automatically at
boot time like before.
What I did is I re-wrote the files on the SD Card and now camogm is called
automatically from the webpage link as before.
The problem I had was that the webpage using camogmgui.php was
Hi,
1. To check if camogm is alive:
> root@elphel393:~# ps | grep camogm
3059 root 267m Scamogm -n /var/state/camogm_cmd -p 3456 -s
> /mnt/sda1/camogm.disk
> 3081 root 2764 Sgrep camogm
2. Check camogm status:
http://192.168.0.9/camogm_interface.php?cmd=status
3. Start
Frederick,
A link to what?
How were you starting camogm? Did it work before? How were you using it? How
did it fail to load?
Andrey
On Thu, 15 Mar 2018 08:31:29 -0700 Frederick
Gamachefrederick.gama...@gmail.com wrote
Another thing,
After I tried pluging a USB drive through an
Another thing,
After I tried pluging a USB drive through an hub, attached to the 10389B
board, it seems that the camogm is failing to load, even after re-booting.
Is there a link?
Frederick
On Thu, Mar 15, 2018 at 10:53 AM, Frederick Gamache <
frederick.gama...@gmail.com> wrote:
> Andrey,
>
>
Frederick,
2A is not too much, Traco can provide 3.5A. How did you test 10385 - separately
or when connected to 10393? 10385 itself will not work - there is enable signal
coming from the 10393, so 10393 can shut itself down and then wake up with the
clock/calendar chip.
Heat frame by itself
Andrey,
The supply current drawn is nearly 2.0 Amps @ 3.3V, once the FPGA is loaded.
I have the 10389 interface board but no SSD mounted and no external SATA
drive attached at the moment.
When I received the camera kit, I found that the unit was especially hot
when touching it.
I don't have the
Hi,
Its seems that my power board (10385-B power board - 48V) is out of service
and I'm now powering the 3.3V from an external power supply.
Do I really need the 10385-B power board to supply the SATA adapter board
(10389-B) or should it works ok from my external 3.3V power source?
Frederick
Hello,
Just to let you know guys that my circuit is now working since I mounted my
DC-DC converter on my PCB.
Many thanks for your support!
Frederick
On Tue, Mar 13, 2018 at 12:18 PM, Elphel Support <
support-list@support.elphel.com> wrote:
> Frederick,
>
> Yes - your last problem (system
Frederick,
Yes - your last problem (system getting stuck after bitstream) is caused by the
wrong power sequencing. But as 1) you have 10338 working and 2) your board is
tested w/o 10393 it should be working together eventually.
Andrey
On Tue, 13 Mar 2018 07:48:42 -0700 Frederick
Fred,
Just to clarify: 10393 can drive up to ~1.0A, but there will be voltage drop on
the cable (Elphel cables have thick power traces). Connector is rated 0.4A/pin.
The sensor power is controlled by the script (same one that loads bitstream),
power status/control is available over the sysfs
Frederick, you need to power you board either directly from the 10393 3.3V on
the cable, or (if you board has other components that need more power than
10393 can provide) use external power switch driven by the cable power.
The problem is that the cable goes directly to the FPGA port that
I use TeraTerm.
I receive something else than 0x, but it seam to be the same value for
any register...
Maybe I should check my power on my sensor chip.
FPGA bitstream stalls, it doesn't initialize if I power on my sensor PCB.
Fred
On Fri, Mar 9, 2018 at 4:37 PM, Oleg
Hi,
> Question: does the software needs to reach the 34VL02 EEPROM at any point?
> Because I don't have one on my own sensor board...
>
It should work fine without eeprom.
Did it read chip id? or is it 0x? Do you use minicom or putty or other
terminal program?
Regards,
Oleg
Frederick,
1. Here are the files: https://community.elphel.com/f
iles/393/20180308_test_0x5d/
2. Before copying - boot from the card and check the linux version:
> root@elphel393:~# uname -r
> 4.9.0-xilinx-v2017.3
* If it's 4.9.0-xilinx-v2017.3 then copying only devicetree.dtb and uImage
Hi,
> Can you send me an updated version of the firmware using the 0x5D addr
> please?
>
Ok, I will send you a link once I prepare it later today. I will turn the
kernel debug on.
Will I be able to copy the files you will send me on the camera micro SD
> card so I can boot from it?
>
Do you
Hello Oleg,
Thank you for your fast response.
I'm not able to build the firmware at the moment. Following the spec,
changing the SADDR pin to a HIGH value should translate the device ID to
0xBA, so *0x5D* as the 7-bit address.
I'm able to read the device registers on your sensor board using the
Hi,
1.
I made change so it could be set int device tree (0x48) - just noticed a
bug and had to fix it:
> ...
elphel393_sensor_i2c: elphel393-sensor-i2c@0 {
> compatible = "elphel,elphel393-sensor-i2c-1.00";
> /* Add known devices: name, slave address
17 matches
Mail list logo
