The bug is as follows (arm11.c): -memcpy(buffer + count * sizeof(uint16_t), &svalue, sizeof(uint16_t)); +memcpy(buffer + i * sizeof(uint16_t), &svalue, sizeof(uint16_t));
--Michal On Mon, 2009-08-03 at 15:45 -0700, michal smulski wrote: > Little-endian mode. I can correctly access the ARM11 core via MAJIC JTAG > interface and Mentor's software. Only Olimex/openocd is giving me > trouble with 16-bit access. > > I tried to configure openocd with big-endian but I get the same results > (32bit & 8bit work, 16bit return always 0x0000) > > Attached is my config file. > --Michal > > On Tue, 2009-08-04 at 00:08 +0200, Michael Schwingen wrote: > > michal smulski wrote: > > > I am using C100 (Mindspeed ARM11 dual core). I can correctly access > > > DDR2 and 16 bit flash on it via 8-bit and 32-bit commands (mdb,mdw) but > > > not 16-bit access. > > Are you running it in big or little endian mode? > > > > I did some work on that CPU some time ago, and ran into problems because > > there were some issues regarding big-endian support (I was using a > > BDI2000 at that time, not OpenOCD). > > > > I did not get to dig much deeper, because the project was cancelled, and > > there were some documentation updates later, so maybe this was just a > > documentation issue. > > > > cu > > Michael > > > > _______________________________________________ > > Openocd-development mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
