Broken i_ema_a<8>
Added by Łukasz Dałek almost 11 years ago
Hello,
My FPGA has a little problem with modules detection,
Linux driver and controlling program always double-detect them.
So I've tested address lines with this simple VHDL file:
o_nmi_n <= '1';
o_int <= (others => '0');
io_ema_d <= i_ema_a & i_ema_ba when i_ema_cs5_n = '0' else (others=>'Z');
io_ema_wait_n <= (others=>'Z');
and C program:
fd = open("/dev/mem", O_RDWR);
...
mem = mmap(NULL, 0x4000000 /* 64 kB */, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0x66000000);
...
fpga = (volatile uint16_t *)mem;
log = fopen("emifatest.log", "w");
...
for (i = 0 ; i < 0x10000 / 2 ; ++i) {
fprintf(log, "{ 0x%04X , 0x%04X }, // [%s]\n",
i << 1, fpga[i], ((i << 1)!=fpga[i])?"NOK":"OK");
}
fclose(log);
munmap((void *)mem, 0x4000000);
And It showed up that 8th address line is broken: { 0xFFFE , 0xFBFE }, // [NOK]
the same file on working board: { 0xFFFE , 0xFFFE }, // [OK]
0xfffe 0y1111111111111110
0xfbfe 0y1111101111111110
And my question is if there is any chance, that this problem exists
because of misconfiguration?
Best regards,
Lukasz Dalek
| emifa_broken.log (944 KB) emifa_broken.log | |||
| emifa_ok.log (928 KB) emifa_ok.log | |||
| emifatest-0.1.zip (4.67 KB) emifatest-0.1.zip |
Replies (7)
RE: Broken i_ema_a<8> - Added by Michael Williamson almost 11 years ago
Hello Mr. Dalek,
It might be a problem. Between your "good and bad" boards:
- You are referring to 2 separate modules? Can you provide the serial numbers of the modules?
- You are running the same software image (same kernel, same application, same FPGA image, etc.)?
- You are using the same host board. Is it our DevKit or your custom board?
Do you have an FPGA JTAG pod? Can you run Xilinx's chipscope and capture the bus cycles from your test? That would confirm it (allowing rather direct inspection at the pin input), though you have a pretty good test case.
It sounds like we may need to issue you an RMA. If you send an email to orders@criticallink.com you can initiate this process, please reference this forum post if you need to.
I am sorry for the inconvenience. Such a failure should not have made it though our automated factory tests.
-Mike
RE: Broken i_ema_a<8> - Added by Łukasz Dałek almost 11 years ago
Hello Mike,
1. What do you mean by two separate modules, two mity boards?
2. Yes, Same kernel, same application, same FPGA image.
3. Two diffrent host boards, but I don't think that host board can be a problem,
because no EMIF signal is routed outside module.
I'll try to test it using Chipscope by the end of the week.
Lukasz Dalek
RE: Broken i_ema_a<8> - Added by Michael Williamson almost 11 years ago
Yes. Two different mity boards. Can you give me the serial numbers?
-Mike
RE: Broken i_ema_a<8> - Added by Łukasz Dałek almost 11 years ago
ChipScope confirmed that sth is wrong with i_ema_a<8> pin.
Serial numbers of Mity modules: 121924 (broken), 131576 (working).
Lukasz
| i_ema_a_8_broken_2.pdf (42.6 KB) i_ema_a_8_broken_2.pdf |
RE: Broken i_ema_a<8> - Added by Łukasz Dałek over 10 years ago
I have more questions about RMA procedure.
The company send an e-mail to orders@criticallink.com with a question about
initiating RMA procedure and till now there is no answer from there.
Can anyone from CL help me to solve this case?
RE: Broken i_ema_a<8> - Added by Alexander Block over 10 years ago
Lukasz,
I have found the RMA request e-mail you have mentioned and have replied to that e-mail accordingly.
Thank you,
Alex
