[Elphel-support] Script for changing the SADDR bit for the MT9P031 sensor

[Elphel Support]

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 Gamache<frederick.gamache at gmail.com> wrote ---- 

Hello Andrey,

Normally I have a dc-dc converter chip on my pcb which translate 3.3V to 2.8V. 
The 3.3V source is provided by the cable attached to the 10393.


I'll wait to receive my chip today and will install it tomorrow. I'll see if things will get better with it.


Currently I'm using an external power supply to source the 2.8V voltage so I guess the timing for the power sequence is not ok.


Frederick


On Fri, Mar 9, 2018 at 5:51 PM, Elphel Support <support-list at support.elphel.com> wrote:
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 interface.

You may also put a buffer on all signals from the sensor, FPGA has flexible means to compensate pin delays if needed after the buffer insertion.

Andrey

---- On Fri, 09 Mar 2018 14:26:50 -0800 Elphel Support<support-list at support.elphel.com> wrote ---- 

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 should be powered _before_ any non-zero voltage appears on the FPGA pins. This is a feature of the FPGA.

Andrey

---- On Fri, 09 Mar 2018 13:47:51 -0800 Frederick Gamache <frederick.gamache at gmail.com> wrote ---- 

I use TeraTerm.

I receive something else than 0xffff, 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 <support-list at support.elphel.com> wrote:
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 0xffff? Do you use minicom or putty or other terminal program?


Regards,
Oleg

 

 


 _______________________________________________ 
Support-list mailing list 
Support-list at support.elphel.com 
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com 






_______________________________________________ 
Support-list mailing list 
Support-list at support.elphel.com 
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com 












 _______________________________________________ 
Support-list mailing list 
Support-list at support.elphel.com 
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com 





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20180313/16699b88/attachment.html>