Other Parts Discussed in Thread: BEAGLEBONE, , TX12, TPS65217, TEST, OMAP2430, TUSB6010, BEAGLE, OMAP3530, DAC7512, PMP, CYPRESS, TCA6416, TCA8418, LM8323, LM8333, ADS7846, TSC2005, TSC2007, TWL6040, PCF8574, TPS65910, BQ27000, LP8727, BQ24190, LM63, LM70, LM73, LM77, LM80, LM83, LM87, LM90, LM92, LM93, LM95234, LM95241, LM95245, ADS1015, ADS7828, ADS7871, AMC6821, INA209, THMC50, TMP102, TMP401, TMP421, DRA752, LP8788, TPS65010, TPS65090, TPS65218, TPS65912, LM3533, LP3971, LP3972, LP8755, TPS51632, TPS62360, TPS65023, TLV320AIC23B, TVP5150, TVP7002, THS8200, THS7303, DA8XX, TFP410, TPD12S015, LM3630, LM3639, TWL6030, LM3530, LM3642, LP3944, LP5521, LP5523, LP5562, LP8501, DAC124S085, TCA6507
My customer has been using AM335x based design for several years. Their prior generation product (designed 2013/2014) uses TI-SDK-7, Linux kernel 3.12.10.ti-2013.12.01. across all their minor hardware changes and it works fine so far.
They are now working on a new product and plan to use Yocto. They have been able to get yocto setup and created images that run fine on BeagleBone black and should run on our EVM. However, they couldn’t get it working on the prior gen product. U-boot works fine but will always get linux-starting and then no messages.
For troubleshooting, they decided to use latest TI-SDK for the prior gen boards. They couldn’t boot their board using latest SDK. They have used exactly the same u-boot and used same ti-def config and DTS file. They copied the old dependency files, so there are no changes at all. At this point, only the kernel files are different. Everything related to their custom hardware is the same but they still can’t get the board running Linux.
Any ideas of what could be wrong?