Start a new topic

AD450 card returns error "Could obtain sipcid table (error fffffffb), exiting"

[size=3]We are trying to access AD450 PMC card (AD482+AD250) using vxWorks driver supplied by 4DSP.[/size]

[size=3]However on calling the function "tADC250(0)" returns following & exits:[/size]

Start of program
Could obtain sipcid table (error fffffffb), exiting
value = -3 = 0xfffffffd

[size=2]We checked that default FPGA firmware VHDL has 0x75 (117) as constellation ID & same was set in the supplied drivers also. Even than it returns "error fffffffb" related to wrong constellation ID.[/size]

[size=3]Also using  the function "t4FMGetInfo("FM482", 0)" returns following:[/size]

FPGA A Revision = 0.10
Successfully read information from device 0
        FPGA A PCI Revision  : 0.10
        FPGA A Revision      : 3.4
        FPGA A Customer Nr.  : 0
        FPGA A Firmware Type  : 0
        FPGA A Has Ext. Infos : 0
        CPLD Revision        : 0.0
        Board Serial Number  : 0
        User ROM Value        : 0
        FPGA B Device Type    : XC4VLX40-10FF1148C
        FPGA B Revision      : 0.11.14
        FPGA B Firmware Type  : 1712
        On Board Memory      : QDR bank 2 and 0 available

[size=2]In above data, FPGA-B device type is wrongly detected while ordered board configuration had " XC4VSX55" instead of  XC4VLX40.[/size]

[size=2]Pl. suggest the reason for the same. [/size]

Can you please provide me with a board serial number? I need to check if the hardware/software is covered by warranty or not.
The information displayed by t4FMGetInfo() is directly decoded from the BAR attached to our device. It looks like you are using a big endian (PowerPC) processor and our BSP only support Intel processors.
Best Regards,
Dear Arnaud,

Thanks for quick reply. We had baught two cards:

1. AD450  (AD482+AD250) : Serial Number 68800004
2. VID471 (FM482 + FP-CL) : Serial Number 49470003

Yes, we are using big endian (PowerPC) processor (C102 from Aitech) running VxWorks. We had confirmed about using the PPC host during techincal clarifications before ordering.

Both the boards are having the same issue.


Dear Abhishek,
I am surprised about that because we don't have any PowerPC mainboard available and we would have needed to obtain one in order to do validate VX support for PowerPC.
There is nothing I can do. The boards/bsps were delivered to Avnet India and are out of warrant unfortunately.
The best way to proceed is for you to contact [email][/email] and discuss that with them.
Best Regards,

[size=2]Dear Arnaud,[/size]
[size=2]Will surely contact through our supplier. But I guess warrenty support for other camera-link board (VID471-20-55-10I-AC-X , Serial Number 49470003) is still in support as it was purchased last year through Picosem Technology Pvt Ltd, India alongwith full BSP & VHDL reference codes.[/size]
[size=2]Also I am not able to understand how it will not support big endian architecture beacause supplied vxWorks drivers contains logic to verify big-endian byte ordering [see line# 869 for (_BYTE_ORDER == _BIG_ENDIAN) in 4fmdrv.c ][/size]

Dear Abhishek,
If you have order VID471 with a Vxworks BSP, then you might still be under warranty. If you have purchased a VID471 with default BSP (Windows), you can get support for Windows.
The endianness macro are there but the code was never verified on PowerPC. Fact is the Vxbus is already doing most of the endian conversion but still other places need to be asserted. We have not been doing that ourselves, we do have two customers who modified our BSP to PowerPC without asking any questions and they are happy with it.
I am not here to assert deliveries, pos, and sales but really technical support. I can tell you that the Vxworks BSP does not run as is on PowerPC. The ADC250 application will also need to be changed. Same for the VID471, I am not sure if we even have done VID471 on Vxworks, I assume not.
Best Regards,
[size=2]Yes, VID471 was purchased along with a Vxworks BSP last year. The BSP ( was downloaded from 4DSP ftp site : [font=Arial][ftp=][/ftp][/font] with username/password provided in email. But It looks like neither AD450 BSP nor the VID471 BSP were fully tested. Both of them results in same errors.[/size]

[size=2]We further tried to test FPGA-A DDR2 memory with  tFPGAAMemtest("FM482", 0, 1, 133) function. Initially function was exiting at line35.[/size]

if(freq<<85||freq>>180) {
printf("The target frequency should be 85..180MHz\n");
return -3;

[size=2]then we corrected above statement as[/size]

if(freq<85||freq>180) {
printf("The target frequency should be 85..180MHz\n");[/code]

[size=2]Now it passes above statement but with memory verification errors as shown below:[/size]

[size=2]tFPGAAMemtest("FM482", 0, 1, 133)[/size]
[size=2]Running FPGA A Memory test on device 'FM482' : Frequency=133MHz, size=1048576 by[/size]
[size=2]The test application send random data to DDR2 memory, receive data from DDR2 mem[/size]
[size=2]The test succeed if both data buffers are equal![/size]
[size=2]Initialize hardware: DONE[/size]
[size=2]Allocating/Randomizing a transmit buffer: DONE[/size]
[size=2]Sending data: DONE[/size]
[size=2]Allocating a receive buffer: DONE[/size]
[size=2]Receiving data: DONE[/size]
[size=2]Comparing data: Error @0x0 : Expected=0x5674b741, Real=0x0[/size]
[size=2]Error @0x1 : Expected=0x1662c295, Real=0x0[/size]
[size=2]Error @0x2 : Expected=0x909f9479, Real=0x0[/size]
[size=2]Error @0x3 : Expected=0xeae2a58c, Real=0x0[/size]
[size=2]Error @0x4 : Expected=0xbbd690dc, Real=0x0[/size]
[size=2]Error @0x6 : Expected=0x3be26188, Real=0x0[/size]
[size=2]Error @0x7 : Expected=0x4c41a54a, Real=0x0[/size]
[size=2]Error @0x8 : Expected=0xff5bae8, Real=0x0[/size]
[size=2]Error @0x9 : Expected=0xb8e40943, Real=0x0[/size]
[size=2]Error @0xa : Expected=0x542bca2f, Real=0x0[/size]
[size=2]Error @0xb : Expected=0xa5cb4203, Real=0x0[/size]
[size=2]Error @0xc : Expected=0xc111bce0, Real=0x0[/size]
[size=2]Error @0xd : Expected=0x69c748c2, Real=0x0[/size]
[size=2]Error @0xe : Expected=0x2a1d3648, Real=0x0[/size]
[size=2]Error @0xf : Expected=0x35545043, Real=0x0[/size]
[size=2]Found 262144 errors during verification[/size]
[size=2]Success, transfered 1048576 bytes without error...[/size]
[size=2]value = 0 = 0x0[/size][/quote]

[size=2]It looks like all read data is zero. Can you please suggest the way further to get the BSP's working. [/size]

Dear Sir,
We of course tested these BSP. As I explained you already, the BSP will not run under PowerPC. You will need to either figure out which modifications are required on your own or contract 4DSP in order to make sure that it will run on your target hardware. It should not be that difficult as many other customers have been doing that without asking many questions.
Nothing will work up to the point you have correct communication with the BAR. I insist get in touch with the sales people and explained them you purchased a BSP for PowerPC but it does not work on your PowerPC system.
Best Regards,
Dear Sir,
[size=1em]I tried to contact on 4DSP sales ([/size][size=1em][email][/email][/size][size=1em]), but there is no response from them. [/size]
[size=1em]Also as suggested, we tried to test the BSP on intel [/size][size=1em]x86[/size][size=1em] based single board computer as host ([/size][size=1em]C160 from Aitech[/size][size=1em]), still results are same.[/size]

[size=1em]Pl. find attached the log files captured from an x86 host (Aitech SBC C160). The 4DSP API returns the same data with & without the PMC boards being mounted on host (If card is not mounted then also API function returns no warning/error that PMC card is not mounted).[/size]

Dear Sir,
As explained already your software warranty period has lapsed. You will need to purchase a technical support contract so we can help you further. Not sure what you have asked to your var/sales but looks like they are busy or they have asked your local VAR to take care of that.
Out of my curiosity, have you tried to run the hardware on Windows in order to make sure the hardware is fine?
You are not even entitled to support directly from 4DSP but this should come from our distributor (Avnet or another one), any email you get from me is already more than what I am supposed to do. Many customers uses this BSP.
Best Regards,
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.