AnsweredAssumed Answered

We are using LS2085A-RDB with a CodeWarrior TAP connected. We are using CodeWarrior Development Studio for QorIQ LS series - ARM V8 ISA.  How can we use CodeWarrior to debug once we transited to aarch32?

Question asked by Hans Hedin on Oct 6, 2016
Latest reply on Oct 6, 2016 by Adrian Stoica

We are using LS2085A-RDB with a CodeWarrior TAP connected. We are using CodeWarrior Development Studio for QorIQ LS series - ARM V8 ISA. We booting the board with uboot in aarch64. Our application starts executing in aarch64 but does early, for legacy reasons, transit to aarch32. The transits to aarch32 works ok which we can follow with debug prints to the serial port until we enable the mmu. After mmu enable it hangs forever. We are using mmu with short descriptor format. With CodeWarrior ARMV8 we can debug our application in aarch64  but after to transit to aarch32 the CodeWarrior ARMv8 is lost. We tried to connect CodeWarrior ARMV7 but that did not work neither. How can we use CodeWarrior to debug LS2085A-RDB once we transited to aarch32?

Outcomes