I'm trying to use the TRDB-D5M camera connected to a DE2-115 with the UP video design examples. However I can't achieve what the example design file contained in following folder is supposed to do: IP_Core_Demos\Video_Demos_using_SOPC_Builder\DE2-115\Example_4_Video_In The main modifications that I made in SOPC builder is to change the input of the 'Video-In Decoder' core to THDB_D5M camera, add 'Bayer Pattern Resampler', use 'Scaler' and 'Clipper' components to match VGA 640 x 480 specifications. The system was generated successfully. Then I added the following lines to the main example_4_video_in.v file to be able to read from the camera: .PIXEL_CLK_to_the_Video_In_Decoder(PIXEL_CLK), .FRAME_VALID_to_the_Video_In_Decoder(FRAME_VALID), .LINE_VALID_to_the_Video_In_Decoder(LINE_VALID), .PIXEL_DATA_to_the_Video_In_Decoder (PIXEL_DATA), This compiled without errors too. But when I download the .sof to the board, I don't get any display on the VGA output. Am I missing something there? I can see that the 'Video-In Decoder' component has option THDB_D5M but the camera is called TRDB_D5m. Could that be a reason? The camera system CD has an example file which works fine, but it does not make use of SOPC. I would like the video source to be an SOPC component. Has anybody used this camera in this way?

I'm thinking that it may best to take the verilog example and re-construct it to be faster. The reason is i'm afraid that the uni cores will restrict the manipulations of the data too much. As in having to scale down to the format acceptable by those cores, but they might be that restrictive for a reason. From the SOPC perspective the FIFO does work as I have done the earlier Uni core examples and customised them so they would work on the DE2-115. I rebuilt the SOPCs with the DE2-115 modules and took the software into a Nios project for examples 1, 2 and 3. I think the issue is possibly the AV core, i never noticed that the camera model number was different until i saw your post. I'm goig to look at the verilog example and try understand it, i may even try to modularise it for a schematic build or SOPC (but i got no idea about SOPC component creation). Also check to ensure you changed the clocks to their appropriate ones based on the Example 4 of the uni program cores.

I managed to find a DE2 board from another student. I tried the TRDB-D5M camera with the example UP files for DE2 and they all worked! - The Extra_D5M_Video_In worked fine apart from ouput is showing at slow frame-rate. - The Extras_Edge_Detection also is detecting the edges of whatever the camera is reading in. The only flaw is that the output display is upside down.. don't know why. So, we can say that the IP_Core_Demos are not fully DE2-115 compliant yet. The fact that no example SOPC design example 'Extra_D5M_Video_In' exists in DE2-115 folder should have been a hint to us I guess. Who writes these UP examples? Is it Terasic or Altera? I contacted Terasic but they say they can't help with the SOPC section, and told me to use their example verilog design file and SignalTap to sort it out myself. I'm bit annoyed by this. I thought I could get up and running quickly connecting the camera to the DE2-115 board using SOPC builder because I only bought this kit after reading the following in the UP literature "The video decoder converts raw video input from videoin chips on Altera DE2/DE2-70/DE2-115 boards, or Terasic’s 5 megapixel CCD camera, into packets that can be processed by the video-processing cores." Anyway I have to carry on with the DE2-115 and work using the verilog design file as AsValdr has suggested. I don't understand the verilog code fully. I think one potential mistake among many others is with the GPIO ports. DE-115 define the ports as //////////// GPIO, GPIO connect to D5M - 5M Pixel Camera ////////// input D5M_D; input D5M_FVAL; input D5M_LVAL; input D5M_PIXLCLK; output D5M_RESET_N; output D5M_SCLK; inout D5M_SDATA; input D5M_STROBE; output D5M_TRIGGER; output D5M_XCLKIN; while DE2 would just do inout [35:0] GPIO_0; // GPIO Connection 0 OK anyway, time to go back to work and figure out how to solve all this.

What difference in cores is there between the two? Remeber the DE2-115 has a seperate example 4. Also by using quartus and nios manually i got the earlier 3 examples going which proves all those included cores work. (Those examples being the char, pixel buffers and the combo of the two. Are you able to get the Example 4 video going. It says the video it needs must be NTSC, but i'm from Australia and all our devices are PAL format; so i can't try it. Most of the cores are have a setting for which DE2 your using. The thing i'm suss on is the config core. When you select the camera it greys out the board selection. Perhaps this matters not. But if your shy to the verilog perhaps you could do some experimentation and determine which core/s is the problem. That way we can focus on replacing that core with our own. I'm prbably going to make my own cores (long road) by changing up the verilog example, but i'm cool to help you plug the gaps for an SOPC design if i can along the way. Don't get your hopes up, i'm a noob aswell, but there is only 1 way to un-nob yourself and thats to have a go. in summary i think you should try: 1. The example 4 thats specific for the DE2-115. Confirm it works. 2. List the cores in example 1,2,3 and 4. All the cores there can be confirmed as working. 3. Compare the old DE2 example you got working with the camera and identify the cores that are different from the list you made. 4. Therefore those differing cores are the issue. 5. We can attack those cores ourselves and replace them. Meanwhile i'll be experimenting with the verilog, which will hopefully allow me to understand it and develop seperate components. Then if someone knows how to convert these to SOPC, then "TADA"; we'll have a working SOPC DE2-115 D5M camera combo.

I have same problem. In my opinion Audio and Video Configuration ip module works wrong. alt_u32 data; alt_up_av_config_dev* d5m=alt_up_av_config_open_dev(CAMERA_CONFIG_NAME); alt_up_av_config_read_D5M_cfg_register(d5m, 0,&data); printf("Data %x",data); CAMERA_CONFIG_NAME - is Audio and Video Configuration ip name in SOPC Register 0 is Chip Version register and its default value is 0x1801, but i have data = deadbeef so Audio and Video Configuration module cant read/write data from/to D5M P.S. I have DE0 module and i cant use examples from D5M CD. P.P.S Sorry for my English

Sorry, it was my mistake. Audio and Video Configuration ip works fine, the solution for DE0 was found =) I have attached my project. In this project i use 8-bit grayscale mode, 80x60 pixel buffer. I connect D5M module to GPIO_0 header. In the project folder a lot of unnecessary files, but the main thing here is the SOPC and the correct pinout (see bdf).

Problem using TRDB-D5M Camera with SOPC Builder

25 Replies

Altera_Forum
Honored Contributor
14 years ago
I'm thinking that it may best to take the verilog example and re-construct it to be faster. The reason is i'm afraid that the uni cores will restrict the manipulations of the data too much. As in having to scale down to the format acceptable by those cores, but they might be that restrictive for a reason.

From the SOPC perspective the FIFO does work as I have done the earlier Uni core examples and customised them so they would work on the DE2-115. I rebuilt the SOPCs with the DE2-115 modules and took the software into a Nios project for examples 1, 2 and 3.
I think the issue is possibly the AV core, i never noticed that the camera model number was different until i saw your post.

I'm goig to look at the verilog example and try understand it, i may even try to modularise it for a schematic build or SOPC (but i got no idea about SOPC component creation).

Also check to ensure you changed the clocks to their appropriate ones based on the Example 4 of the uni program cores.
Altera_Forum
Honored Contributor
14 years ago
I managed to find a DE2 board from another student. I tried the TRDB-D5M camera with the example UP files for DE2 and they all worked!

- The Extra_D5M_Video_In worked fine apart from ouput is showing at slow frame-rate.
- The Extras_Edge_Detection also is detecting the edges of whatever the camera is reading in. The only flaw is that the output display is upside down.. don't know why.

So, we can say that the IP_Core_Demos are not fully DE2-115 compliant yet. The fact that no example SOPC design example 'Extra_D5M_Video_In' exists in DE2-115 folder should have been a hint to us I guess. Who writes these UP examples? Is it Terasic or Altera? I contacted Terasic but they say they can't help with the SOPC section, and told me to use their example verilog design file and SignalTap to sort it out myself.

I'm bit annoyed by this. I thought I could get up and running quickly connecting the camera to the DE2-115 board using SOPC builder because I only bought this kit after reading the following in the UP literature "The video decoder converts raw video input from videoin chips on Altera DE2/DE2-70/DE2-115 boards, or Terasic’s 5 megapixel CCD camera, into packets that can be processed by the video-processing cores."

Anyway I have to carry on with the DE2-115 and work using the verilog design file as AsValdr has suggested. I don't understand the verilog code fully. I think one potential mistake among many others is with the GPIO ports. DE-115 define the ports as
//////////// GPIO, GPIO connect to D5M - 5M Pixel Camera ////////// input D5M_D; input D5M_FVAL; input D5M_LVAL; input D5M_PIXLCLK; output D5M_RESET_N; output D5M_SCLK; inout D5M_SDATA; input D5M_STROBE; output D5M_TRIGGER; output D5M_XCLKIN;
while DE2 would just do
inout [35:0] GPIO_0; // GPIO Connection 0

OK anyway, time to go back to work and figure out how to solve all this.
Altera_Forum
Honored Contributor
14 years ago
What difference in cores is there between the two? Remeber the DE2-115 has a seperate example 4. Also by using quartus and nios manually i got the earlier 3 examples going which proves all those included cores work.
(Those examples being the char, pixel buffers and the combo of the two.

Are you able to get the Example 4 video going. It says the video it needs must be NTSC, but i'm from Australia and all our devices are PAL format; so i can't try it.

Most of the cores are have a setting for which DE2 your using.
The thing i'm suss on is the config core. When you select the camera it greys out the board selection. Perhaps this matters not.

But if your shy to the verilog perhaps you could do some experimentation and determine which core/s is the problem. That way we can focus on replacing that core with our own.

I'm prbably going to make my own cores (long road) by changing up the verilog example, but i'm cool to help you plug the gaps for an SOPC design if i can along the way.

Don't get your hopes up, i'm a noob aswell, but there is only 1 way to un-nob yourself and thats to have a go.

in summary i think you should try:
1. The example 4 thats specific for the DE2-115. Confirm it works.
2. List the cores in example 1,2,3 and 4. All the cores there can be confirmed as working.
3. Compare the old DE2 example you got working with the camera and identify the cores that are different from the list you made.
4. Therefore those differing cores are the issue.
5. We can attack those cores ourselves and replace them.

Meanwhile i'll be experimenting with the verilog, which will hopefully allow me to understand it and develop seperate components. Then if someone knows how to convert these to SOPC, then "TADA"; we'll have a working SOPC DE2-115 D5M camera combo.
Altera_Forum
Honored Contributor
14 years ago
I have same problem. In my opinion Audio and Video Configuration ip module works wrong.

alt_u32 data;
alt_up_av_config_dev* d5m=alt_up_av_config_open_dev(CAMERA_CONFIG_NAME);
alt_up_av_config_read_D5M_cfg_register(d5m, 0,&data);
printf("Data %x",data);

CAMERA_CONFIG_NAME - is Audio and Video Configuration ip name in SOPC

Register 0 is Chip Version register and its default value is 0x1801, but i have data = deadbeef so Audio and Video Configuration module cant read/write data from/to D5M

P.S. I have DE0 module and i cant use examples from D5M CD.
P.P.S Sorry for my English
Altera_Forum
Honored Contributor
14 years ago
Sorry, it was my mistake. Audio and Video Configuration ip works fine,
the solution for DE0 was found =) I have attached my project. In this project i use 8-bit grayscale mode, 80x60 pixel buffer. I connect D5M module to GPIO_0 header. In the project folder a lot of unnecessary files, but the main thing here is the SOPC and the correct pinout (see bdf).
mrdk_de0.qar414 KB
Altera_Forum
Honored Contributor
14 years ago
I've gotten an SOPC to work for the DE2-115, but its incredibly slow fps (unusably slow for video).
How is the fps on yours evired?
Altera_Forum
Honored Contributor
14 years ago
FPS is not so good as I would like, but in my opinion is better than in the example without SOPC from terasic. In my project I dont need high resolution and color, so that the FPS is quite suits me.
Altera_Forum
Honored Contributor
14 years ago
Ok. For the DE2-115 the verilog example is exceptionally better.
I haven't had the chance to look at your design but is it using the Uni program cores or the VIP?
Altera_Forum
Honored Contributor
14 years ago
University Program IP's
Altera_Forum
Honored Contributor
14 years ago
Now I have new problem. Video from D5M camera is normally displayed on the VGA screen. The problem arises when I start to write a program for NIOS.

# include "main.h"

int main()
{

alt_up_av_config_dev* d5m=alt_up_av_config_open_dev(D5M_CONFIG_NAME);
return 0;

}

This simple code build successfully. But when I run it in debugger I have wrong d5m (alt_up_av_config_dev) structure: base adress is correct, but type=17 (instead of 9 for TRDB_D5M_CONFIG). Since the alt_up_av_config_dev structure is wrong, any further attempts to read / write from/to configuration registers of D5M module do not worked out. What am I doing wrong?

Forum Discussion

Problem using TRDB-D5M Camera with SOPC Builder

25 Replies

Recent Discussions

Cannot find download location for Quartus Prime Lite 19.1

Unable to checkout 'intelqsimstarter' license

DE1-SoC to connect a camera via USB

Arria10 Transceiver Oversampling

Donation fpga boards