[Elphel-support] captured image location in memory
gaurav dasondhi
gauravdasondhi2013 at gmail.com
Mon Aug 25 05:49:32 PDT 2014
Dear oleg
continuation of previous mail...
1. I want to perform correlation over raw data but as you mentioned it is
very difficult to find location of captured image and as you don t know
about it ,so can you please tell me who is able to answer my question??
2. i download all x353.v and x353.ucf file and its supporting files ,as i
try to create .bit file then i got some errors during implementation as
below:
1.ERROR:LIT:241 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z5" has a hexadecimal value,
> "11110000111000001100000010000000", which is too large. INIT should
> contain a
> maximum of 32 bits.
> ERROR:LIT:241 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z4" has a hexadecimal value,
> "10001100100110000011000001100000", which is too large. INIT should
> contain a
> maximum of 32 bits.
> ERROR:LIT:241 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z3" has a hexadecimal value,
> "01001010000001000000110000011000", which is too large. INIT should
> contain a
> maximum of 32 bits.
> ERROR:LIT:241 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z2" has a hexadecimal value,
> "01100011010101111010001001100000", which is too large. INIT should
> contain a
> maximum of 32 bits.
> ERROR:LIT:239 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z1" has an invalid hexadecimal
> value,
> "h611A7896".
> ERROR:LIT:241 - Attribute INIT on ROM32X1 instance
> "i_compressor/i_quantizator/i_zigzag/i_z0" has a hexadecimal value,
> "11000110011100110001100111001100", which is too large. INIT should
> contain a
> maximum of 32 bits.
then you provide me solution i.e.
change all ROM32X1 instances:
> ROM32X1 i_z0 ( .A0(rom_a[0]), .A1(rom_a[1]), .A2(rom_a[2]), .A3(rom_a[3]),
> .A4(rom_a[4]), .O(rom_q[0]));
> ...
> defparam i_z0.INIT = 32'hC67319CC;
to:
> ROM32X1 (.INIT(32'hC67319CC)) i_z0 ( .A0(rom_a[0]), .A1(rom_a[1]),
> .A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[0]));
I changed quantizator353.v as you told ,then it will look like:
ROM32X1(.INIT(32'hC67319CC)) i_z0(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]),.A3(rom_a[3]),.A4(rom_a[4]),.O(rom_q[0]));
ROM32X1(.INIT(32'h611A7896)) i_z1(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[1]));
ROM32X1(.INIT(32'h6357A260)) i_z2(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[2]));
ROM32X1(.INIT(32'h4A040C18)) i_z3(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[3]));
ROM32X1(.INIT(32'h8C983060)) i_z4(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[4]));
ROM32X1(.INIT(32'hF0E0C080)) i_z5(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[5]));
but again i got some ERRORS
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 379: Syntax
error near "i_z0".
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 380: Syntax
error near "i_z1".
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 381: Syntax
error near "i_z2".
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 382: Syntax
error near "i_z3".
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 383: Syntax
error near "i_z4".
ERROR:HDLCompiler:806 - "E:/x353original/quantizator353.v" Line 384: Syntax
error near "i_z5".
ERROR:ProjectMgmt:496 - 6 error(s) found while parsing design hierarchy.
ERROR:HDLCompilers:26 - "quantizator353.v" line 379 expecting ';', found
'i_z0'
ERROR:HDLCompilers:26 - "quantizator353.v" line 379 expecting 'endmodule',
found '('
then i googled it and i replace all of them by
ROM32X1 #(.INIT(32'hC67319CC)) i_z0(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]),.A3(rom_a[3]),.A4(rom_a[4]),.O(rom_q[0]));
ROM32X1 #(.INIT(32'h611A7896)) i_z1(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[1]));
ROM32X1 #(.INIT(32'h6357A260)) i_z2(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[2]));
ROM32X1 #(.INIT(32'h4A040C18)) i_z3(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[3]));
ROM32X1 #(.INIT(32'h8C983060)) i_z4(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[4]));
ROM32X1 #(.INIT(32'hF0E0C080)) i_z5(.A0(rom_a[0]), .A1(rom_a[1]),
.A2(rom_a[2]), .A3(rom_a[3]), .A4(rom_a[4]), .O(rom_q[5]));
output no error: i got x353.bit file but as i reboot camera with this newly
genrated x353.bit file i got some strips of different color. please find
attachment of blurred image .
SO IS I DID SOMETHING WRONG ??
On Fri, Aug 22, 2014 at 1:59 AM, Oleg <support-list at support.elphel.com>
wrote:
> Hello Gaurav,
>
> 1. when camera ON then it provide us blurred image. so how to overcome??
>>
> What kind of lens do you have?
> One possible problem can be is that you are using CS mount lens with
> CS-to-C 5mm adapter ring -
> http://wiki.elphel.com/index.php?title=File:Cap_and_ring.jpeg
>
>
>> 2. when camera ON then it is blinking continuously so what it means ?? is
>> it video recording or image capturing ??
>>
> The blinking green led means the camera is connected to a network -
> network packets. Recording or capturing is is not indicated anyhow.
> Solid orange - power.
>
> 3. i want to capture a image (say for reference image) and then by
>> rotating camera some degree i want to capture another image (say current
>> image) after that i want to perform correlation between reference image and
>> current image.
>>
>
> http://wiki.elphel.com/index.php?title=Elphel_353_series_quick_start_guide#Getting_the_first_images
> Store the images and perform correlation if you have a program that does
> it.
>
>
>> 4. i want to reprogram fpga for finding correlation , so i should know
>> storage location of my current image and reference image so can you please
>> tell me where image is store in memory??
>>
> That's a difficult question and I cannot answer it right away as I don't
> know. Could you please have a look at the verilog simulation of the
> compressor?
>
> Are you intending to run correlation over compressed images or raw data?
>
>
>> 5. when image is captured then are you applying any kind of image
>> processing operation and then image is stored in camera.??
>>
> After the image is captured - the raw pixel data is converted and
> compressed into a chosen image format. No other processing is performed.
> http://wiki.elphel.com/index.php?title=JP4
> http://wiki.elphel.com/index.php?title=Circbuf
>
>
>> 6. I successfully generate a x353.bit file but for rebooting camera i
>> unplug Ethernet cable and after 1 minute i plug it again, so it is rebooted
>> but there is no message popup for ensuring that it is rebooted and is it
>> right way to reboot camera??
>>
> Did you meet the timing constraints?
>
> Rebooting:
> a. Not clear. You don't have to wait for 1 min - just unplug and plug the
> cable to the camera network port and wait until it boots for ~1min. But if
> you copied something on the camera it's better to run sync over the
> filesystem first, in a browser:
> http://192.168.0.9/phpshell.php?command=sync
>
> So, it's not rebooted if the power supply is on and left connected to the
> camera.
>
> b. if you have Linux, run terminal and type:
>
>> telnet 192.168.0.9
>
> root/pass to login, then type:
>
>> sync
>
> reboot -f
>
>
> You can perform this from any telnet program.
>
> Best regards,
> Oleg Dzhimiev
> Electronics Engineer
> phone: +1 801 783 5555 x124
> Elphel, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20140825/30116730/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blurr.jpeg
Type: image/jpeg
Size: 192611 bytes
Desc: not available
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20140825/30116730/attachment.jpeg>
More information about the Support-list
mailing list