Hi TI,
according to the suggestion given in this thread (https://e2e.ti.com/support/processors/f/processors-forum/993379/tda4vm-clarification-on-dev-boot-mode), I tried to attach to J721E_EVM after U-Boot has booted. Reason behind this is, as already mentioned in the linked thread, that I want to reduce the time it takes to attach to the board. Using GPIO_LedBlink_TestApp from Processor SDK RTOS, there are no issues and the GPIO connected to TP45 is toggling as expected.
However, when I try to load an application to MCU2_0, which uses PCIe interface, I face the following problem (As an additional information: the following program works fine when the board is set to NO-BOOT Mode and initialized via launch.js script):
The screenshot is taken one step before the program crashes. The last assembly instruction ist loading register 0x5010404, after that instruction, the Program Counter is set to 0x10 and the program crashes. According to the TRM, the address 0x5010404 is SERDES_CTRL Register for SerDes instance 1. So apparently, this SerDes instance is not properly configured when booting via U-Boot, whereas when using the launch.js + GEL Files in NO-Boot Mode, it is. Another strange thing is, that I have access to this address in Memory Browser (as you can see in the screenshot), which indicates, that the SerDes instance is some how up.
Can you help me to narrow down the source of this error? As a first step I tried to look for this SerDes instance in U-Boot's device tree. (I am using PSDKL 07.02 at the moment). I found out that there are some SerDes instances defined, but this specific one (SerDes 1) is missing. So do you think adding the correct SerDes instance here would solve my problem? In which node should I add the instance? Or do you think that there is already something missing before U-Boot comes up?
Thank you very much for your help and best regards,
Felix
