|
From: Antonio B. <bor...@gm...> - 2022-03-30 09:48:44
|
On Wed, Mar 30, 2022 at 10:58 AM Chae-yun Lim <all...@gm...> wrote: > > Thanks for your reply. > > >> Have you checkout the whole series ending with https://review.openocd.org/5591/ ? > > Yes, you can see the information as below, > ================================================================ > $ git log -n1 > commit 3f3ba7d3c1a7dcabae97fba4d1dcf3d94498c489 (HEAD) This is the correct version! Good! > ... > I'm not sure if that is CA53 or not. Please refer the following log, > ================================================================ > > targets > TargetName Type Endian TapName State > -- ------------------ ---------- ------ ------------------ ------------ > 0 BLABLA.armv8.apb mem_ap little BLABLA.armv8.tap running > 1 BLABLA.armv8.axi mem_ap little BLABLA.armv8.tap running > 2* temptarget.armv8_0 aarch64 little BLABLA.armv8.tap running >From this, it looks ok. Can you "halt" the core from the telnet connection? > > dap info > AP # 0x20000 > Peripheral ID 0x04000bb9ef > Designer is 0x23b, ARM Ltd > Part is 0x9ef, Unrecognized > Component class is 0x9, CoreSight component > Type is 0x00, Miscellaneous, other > Dev Arch is 0x47700a57, ARM Ltd "unknown" rev.0 > ================================================================ Only this? Or did you only copy the entry that looks like the CA53? I don't see anything wrong in the log. What happens when you connect the gdb? Regards Antonio |