This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: 66AK2H06
Linux is able to boot up when power on.
After Linux boot up,
When type "reboot", the process doesn't restart.
messag is below,
Sending all processes the KILL signal...Unmounting remote filesystems...Deactivating swap...Unmounting local filesystems...Rebooting... [ 1681.839217] reboot: Restarting system
Then it hangs there.
Our board is a custom board from k2hk-evm.
In reply to Yordan Kovachev:
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Peng Li:
I don't see the issue using a TI K2H EVM. I don't have the exact PSDK 126.96.36.199 release installed (kernel 4.4.41), but a newer version, 188.8.131.52 (Kernel 4.9.59). Please see the console log, k2h_reboot.log, attached. I have kernel 4.4.41 installed for the K2E EVM from the same family, and I don't see the issue either. The logs is reboot.log.
We are trying to find the difference between our board and EVM board. The major difference is that our board doesn't use DDR3B. So for the DDR3B clock input pins. We connected the DDR3BCLKP(AR38) to PVDD_SOC and DDR3BCLKN to ground.
I guess there is some codes in Linux to configure DDR3B clock PLL, but I don't know where to find it. Do you have any clue?
In reply to Rex Chang:
In Processor SDK, Linux does not use DDR3B so kernel doesn’t configure it in its device tree file. U-boot only configures the clock, but does not configure or initialize the DDR3B. If the DDR3B clock is the issue, then by disabling DDR3B clock in the u-boot should see the symptom on TI K2H EVM, but I don’t. I removed not only the DDR3B clock configuration, but also all DDR3B related code in u-boot even though they are not called at all. I still can’t reproduce the issue using Processor SDk 184.108.40.206. I don't think this is an issue that can be resolved from software change.
I don't think there is any more TI can do but you resolve the hardware issue.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.