10359 FPGA Simulation - Revision history

Oleg at 12:22, 31 October 2008

2008-10-31T12:22:55Z

← Older revision		Revision as of 12:22, 31 October 2008
Line 125:		Line 125:
	2. Not to forget - "ccam.php?trig=async&mode=set" works after calling the camera interface (camvc.html)		2. Not to forget - "ccam.php?trig=async&mode=set" works after calling the camera interface (camvc.html)

			--[[User:Oleg\|Oleg]] 07:22, 31 October 2008 (CDT)

	==2008/10/01==		==2008/10/01==

Oleg at 12:22, 31 October 2008

2008-10-31T12:22:27Z

← Older revision		Revision as of 12:22, 31 October 2008
Line 119:		Line 119:
	One of that things is memory controller initialization, registers are described in		One of that things is memory controller initialization, registers are described in
	/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h		/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h

			==2008/10/31==
			1. Was able to store the whole frame in SDRAM with modified controller.

			2. Not to forget - "ccam.php?trig=async&mode=set" works after calling the camera interface (camvc.html)


	==2008/10/01==		==2008/10/01==

Oleg at 22:40, 30 September 2008

2008-09-30T22:40:12Z

← Older revision		Revision as of 22:40, 30 September 2008
Line 122:		Line 122:
	==2008/10/01==		==2008/10/01==
	1. after reconfiguration (running camera_demo twice) the image gets darker even with 353+sensor		1. after reconfiguration (running camera_demo twice) the image gets darker even with 353+sensor

			--[[User:Oleg\|Oleg]] 17:40, 30 September 2008 (CDT)

	==2008/09/30==		==2008/09/30==
	update2:		update2:

	1. different md5s - in camera_demo [RSCALE]=305, and the one from *.conf [RSCALE] => 303 - that made the difference. - with [RSCALE]=303 md5 is correct.		1. different md5s - in camera_demo [RSCALE]=305, and the one from *.conf [RSCALE] => 303 - that made the difference. - with [RSCALE]=303 md5 is correct.

Oleg at 22:39, 30 September 2008

2008-09-30T22:39:07Z

← Older revision		Revision as of 22:39, 30 September 2008
Line 119:		Line 119:
	One of that things is memory controller initialization, registers are described in		One of that things is memory controller initialization, registers are described in
	/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h		/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h

			==2008/10/01==
			1. after reconfiguration (running camera_demo twice) the image gets darker even with 353+sensor

	==2008/09/30==		==2008/09/30==
	~~update~~:		update2:
			1. different md5s - in camera_demo [RSCALE]=305, and the one from *.conf [RSCALE] => 303 - that made the difference. - with [RSCALE]=303 md5 is correct.

			--[[User:Oleg\|Oleg]] 17:39, 30 September 2008 (CDT)

			update1:

	1. images from sensors are the same! reconnection of one of the cables fixed that - md5=4ebe69ad27d260c27d667747c431dc96		1. images from sensors are the same! reconnection of one of the cables fixed that - md5=4ebe69ad27d260c27d667747c431dc96

Oleg at 17:02, 30 September 2008

2008-09-30T17:02:17Z

← Older revision		Revision as of 17:02, 30 September 2008
Line 122:		Line 122:
	==2008/09/30==		==2008/09/30==
	update:		update:

	1. images from sensors are the same! reconnection of one of the cables fixed that - md5=4ebe69ad27d260c27d667747c431dc96		1. images from sensors are the same! reconnection of one of the cables fixed that - md5=4ebe69ad27d260c27d667747c431dc96

	2. different md5s is the result of the different configuration. Running adapted camera_demo with 353+sensor gave md5=4ebe69ad27d260c27d667747c431dc96.		2. different md5s is the result of the different configuration. Running adapted camera_demo with 353+sensor gave md5=4ebe69ad27d260c27d667747c431dc96.

	so again ... I just need to find out what is wrong with scripts - why color gain is programmed incorrectly? But it should. And - gain doesn't change after it is reprogrammed while sensor is working.		so again ... I just need to find out what is wrong with scripts - why color gain is programmed incorrectly? But it should. And - gain doesn't change after it is reprogrammed while sensor is working.

Oleg at 16:25, 30 September 2008

2008-09-30T16:25:19Z

← Older revision		Revision as of 16:25, 30 September 2008
Line 121:		Line 121:

	==2008/09/30==		==2008/09/30==
			update:
			1. images from sensors are the same! reconnection of one of the cables fixed that - md5=4ebe69ad27d260c27d667747c431dc96
			2. different md5s is the result of the different configuration. Running adapted camera_demo with 353+sensor gave md5=4ebe69ad27d260c27d667747c431dc96.
			so again ... I just need to find out what is wrong with scripts - why color gain is programmed incorrectly? But it should. And - gain doesn't change after it is reprogrammed while sensor is working.

	Images look very similar		Images look very similar
	{\| border="1" cellpadding="2"		{\| border="1" cellpadding="2"

Oleg at 13:03, 30 September 2008

2008-09-30T13:03:52Z

@@ Line 120: / Line 120: @@
   /elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h
 ==2008/09/29==
 . Images are stable now

Oleg at 16:49, 29 September 2008

2008-09-29T16:49:26Z

← Older revision		Revision as of 16:49, 29 September 2008
Line 119:		Line 119:
	One of that things is memory controller initialization, registers are described in		One of that things is memory controller initialization, registers are described in
	/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h		/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/x353.h

			==2008/09/29==
			1. Images are stable now
			2. md5 is different - the pattern image from sensor+359 is darker than from just the sensor.
			MD5 = 60119f4aea02d4624aad045221b4ede0

	==2008/09/19==		==2008/09/19==

Oleg at 13:03, 19 September 2008

2008-09-19T13:03:40Z

← Older revision		Revision as of 13:03, 19 September 2008
Line 148:		Line 148:
	\| \|\| [[Image:Bad2.jpeg\|thumb]]		\| \|\| [[Image:Bad2.jpeg\|thumb]]
	\|-		\|-
	\| Test patterns		\| Test patterns \|\| \|\| Etalon (353+sensor)
	\|-		\|-
	\|[[Image:Good2.jpeg\|thumb]]\|\| [[Image:Bad3.jpeg\|thumb]]		\|[[Image:Good2.jpeg\|thumb]] \|\| [[Image:Bad3.jpeg\|thumb]] \|\| [[Image:Etalon.jpeg\|thumb]]

	\|-		\|-

Oleg at 12:00, 19 September 2008

2008-09-19T12:00:37Z

← Older revision		Revision as of 12:00, 19 September 2008
Line 121:		Line 121:

	==2008/09/19==		==2008/09/19==
	~~set-up~~ "353+359", x359.bit:		==="353+359+2 sensors in ch0 and ch1"===
			====a)====
			x359.bit:
	* data from channel 0 after resync-ing to internal sclk0 goes to output which is synchronous to pclk at 353. Clock tree:		* data from channel 0 after resync-ing to internal sclk0 goes to output which is synchronous to pclk at 353. Clock tree:
	pclk-> 359's DCM -> sclk0)		353 -> pclk-> 359's DCM -> sclk0
	* other functionality is cut		* other functionality is cut
	* experimented with different cables and, sensors		* experimented with different cables and, sensors

	I get good images, sometimes not. This happens after the power off and the cable from 359 to 353 is a bit deformed, then power on.		I get good images, sometimes not - looks like depends on the boot. This happens after the power off and the cable from 359 to 353 is a bit deformed, then power on.

	Images do not change if the cable is deformed during camera work.		Images do not change if the cable is deformed during camera work.

	Bad images are unstable and can be of different color, ~~but~~ the test pattern is broken ~~and~~ stable.		Bad images are unstable and can be of different color, the test pattern is broken, but stable.



	Conclusion:		Conclusion:
Line 150:		Line 154:
	\|-		\|-
	\|}		\|}

			====b)====
			x359.bit:
			* data from channels 0 and 1 after resync-ing to internal sclk0 is multiplexed to output which is synchronous to pclk at 353. Clock tree:
			353 -> pclk-> 359's DCM -> sclk0
			* other functionality is cut
			* experimented with different cables and, sensors

			All images are broken.

	==2008/06/09==		==2008/06/09==