Hello,
I have precompiled 3rd party library (driver) for handling device. Library works on my PC with x64 system but when I try to run very simple "Find -> Open -> Close device" program it gives me Illegal instruction. First I thought there is an error…
I'm using IAR Embedded Workbench to debug a Cortex-M0 system interfaced through ST-LINK/V2 SWD. The processor isn't officially supported because it is under development, but the configuration files have been updated with correct data. I'm not sure however…
Now that the funny PABT-behaviour is found to be (probably) caused ny debug state, I'd like to exit debug state before return from PABT exception. The ARM v7-A/R ARM says that I should write RRQ to DBGDRCR, but it seems that in Cortex-A7 it's not accessible…
Greetings,
sir/madam i am working on serial wire debug protocol. I was implemented serial wire debug protocol, which was successfully tested for used controllers like xmc1100,xmc4500..etc, when i tried to Access the control on newer controller i.e xmc1100…
I've been trying to get a watchpoint to trigger, but no luck.
There should be 4 watchpoints accordíng to DBGDIDR, DBGDSCR=0x0204000e, so there shouldn't be any problems there?
I use (just in case) the cp14 interface - write DBGWVR0 and DBGWCR0…
In a Cortex-A7 is there a register that shows which breakpoint or watchpoint has triggered a debug event?
Or what's the usual way to find out?
I understand that DFSR FS tells if the DABT took place due to debug event (IFSR for PABT) and MOE in DBGDSCR…
I believe that the Arm Community could be interested in the "Embedded C Programming Course with Arm Cortex-M" video course, which I've been teaching for over a year on YouTube. The playlist for this course is available below.
Embedded…
Arm and Synopsys just announced an extension of the long-standing collaboration between the companies, including a multi-year subscription agreement for access to Arm IP (CPU and GPU cores, system IP, physical IP and POP) to improve power, performance…