I am developing an application with a custom sensor using the DM385 platform.
Up until now, I've been working with the Appro DM385 IPNC RDK 3.5 evaluation model.
Everything has been working fine, until I moved to our own custom board using the same SoC.
I am using the same u-boot, uImage and filesystem (mounted via NFS).
So far, peripherals seem to be working well, and Linux boots up properly.
However, after bootup, I get unpredictable behavior.
Sometimes, but not always, I get "TimeOut occure in boot_proc", suggesting memory allocation problems and/or no video input from the sensor.
This is often solved either by rebooting, or by deleting /mnt/nand/sysenv.cfg and then rebooting.
In addition, whenever I use FVID2_Control() from camera link to control the sensor driver, the function never returns and causes the Alg_ITK_Link_tskMain
function to hang and unable to receive and handle further messages from A8.
Video capture and streaming still continue to work though.
Can anybody suggest places where I can see what's wrong or propose any changes?
If it's any help, on our custom board we are using 4Gbit DDR3 instead of 1Gbit that is used in the EVM.
Here are 2 boot logs, one with timeout error, and the other without:
(Please visit the site to view this file)