u-boot 2022.04 for MCIMX6S7 board (TS-7970)
Hi,
while trying to port OEM u-boot (https://github.com/embeddedTS/u-boot) for TS-7970 (https://www.embeddedts.com/products/TS-7970) to latest 2022.04, I cannot get the init.S running.
Connecting GDB+JLink it appears at certain point the processor does not execute: ``` 0x17802200 <s_init>: push {r3, lr} ``` properly and hang there. See attached gdb.txt: sp does not increments, not `x/x $sp` shows any change in memory. Note: `mon memu32 0x93fe38=1` allows you to write memory (and restore it: `mon memu32 0x93fe38=0`).
Also I traced all instructions executed by "orig" OEM delivered u-boot.imx (based on v2015), and "new" one (attached). There is some diffs in IMX ERRATAS (no impact: removing code from orig works fine); I noted new codes `bl s_init` (from start.S) as `blx s_init`, while orig keeps the same. Not sure why and what is the impact.
Any idea what the reason is and how to get this working?
Regards, Andrea
Hi,
while trying to port OEM u-boot (https://github.com/embeddedTS/u-boot) for TS-7970 (https://www.embeddedts.com/products/TS-7970) to latest 2022.04, I cannot get the init.S running.
Connecting GDB+JLink it appears at certain point the processor does not execute: ``` 0x17802200 <s_init>: push {r3, lr} ``` properly and hang there. See attached gdb.txt: sp does not increments, not `x/x $sp` shows any change in memory. Note: `mon memu32 0x93fe38=1` allows you to write memory (and restore it: `mon memu32 0x93fe38=0`).
Also I traced all instructions executed by "orig" OEM delivered u-boot.imx (based on v2015), and "new" one (attached). There is some diffs in IMX ERRATAS (no impact: removing code from orig works fine); I noted new codes `bl s_init` (from start.S) as `blx s_init`, while orig keeps the same. Not sure why and what is the impact.
Any idea what the reason is and how to get this working?
Regards, Andrea
participants (1)
-
DataSelfService Srl