On Monday 12 September 2016 20:38:15 David Ung wrote: > IIRC, MRC/MCR thumb2 instr are 32bit, but they are reversed with the 1st > half word in 15-0 of DGBITR and the 2nd half word in 31-16 of DGBITR. > > I think the hard part is getting gdb to step through Aarch64 into Aarch32 > (or vice versa).
Exactly. > > If you look at my patch on how memory is access, its going through normal > access mode instead of memory access mode. to get both Aarch64 and Aarch32 > to share the same code, it probably would be better to use the memory > access mode. I didn't extend it to use the faster memory access mode since > all I needed at the time is for gdb to dump kernel stack and read > variables. If I'm not entirely mistaken then MA mode is available in -32 state, too. That being said, can anyone share some code to switch a PE to Aarch32 mode? I'm on Rpi3, using a custom little program that does nothing but set up the GPIOs and then execute an endless loop. The program runs at EL2 in Aarch64 state. This would certainly speed up work. > > David > > ________________________________________ > From: Matthias Welwarsky <matth...@welwarsky.de> > Sent: Monday, September 12, 2016 12:39 AM > To: Duane Ellis > Cc: David Ung; openocd-devel@lists.sourceforge.net > Subject: Re: [OpenOCD-devel] OpenOCD Aarch64 support > > On Sunday 11 September 2016 21:47:09 Matthias Welwarsky wrote: > > On Saturday 10 September 2016 23:27:15 Duane Ellis wrote: > > > > Do you know if there's a method to read registers that is usable in > > > > AArch32 > > > > and -64 execution states? > > > > > > NO - the basic technique is the same Insert an opcode - and use the DCC > > > to > > > transfer data, but the opcodes are totally different. > > > > OK. > > Just noticed; MRC/MCR in AArch32 mode are compatible with ARM32. A1 == T1 > and A2 == T2 encoding. So they're not completely insane. > > BR, > Matthias > > ---------------------------------------------------------------------------- > ------- This email message is for the sole use of the intended recipient(s) > and may contain confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > ---------------------------------------------------------------------------- > ------- ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
