Hi Ganapathi,
Thank you for your reply!
First I should apologize for mixing the two problems together, and it's a little crude for me to push the second problem (ATU) here without enough test and examination. I am working on it today, and some new decoveries have been made, I'll expain it below in details.
I have to emphasize the only way to make to PC recognize the EVM is to connect external power supply to the EVM and let it start first, the EVM will be stuck in a while loop which is detecting the LOCK bit of PCIE_SERDES_PLL register. And till now, it's safe to power on the PC and let BIOS do the enumeration work. No DSP core hang, no device un-recognition, they just work fine.
I am using the '-03' version of TMDXEVMPCI which is OK. However, PCIe boot is unavailable in our target system because there is no EEPROM on our custom board and thus the IBL which has been declared to have a "PCIe Workaround" for the RBL( Have it been fixed now?) is unavailable. And I am just using the EVM for debug purporse because our target system is somehow more complicated with a PCIe switch(IDT,12NT12) connected between X86 and DSPs, and I do not want to be trapped by the 'mysterious' switch chip.
Power sequences are very important because we are controlling the power sequence of the x86, switch, DSPs and even FPGAs by ourselves, so could you please provide some more info on the "some power sequence problem on initial power on time" ? Thanks.
And finally I can explain the ATU problem here. I am still working on it, but a big mistake I've made is that I trusted the "simple" util "lookat" too much, it seems that linux should do something to the pcie driver object before using the BAR memories, I used the linux_bootloader example and it's starting to get to work now. I'll tell you if I've made any progress (today or tomorrow).
Regards,
Hawk
