The target endian issue still worries me. How the target memory is represented in host memory? Is it in physical byte order? When using a uint8 array, buf[0] is same value on target and host memory, isn't it?
If so, mips32_pracc_read_u32 mips32_pracc_read_mem32 mips32_pracc_read_mem16 etc. return wrong byte order on little endian hosts. Attached you will find a patch as discussion base. I tested all four combinations with BE and LE Host against BE and LE target. Commands tested: mdb, mdh, mdw, mwb, mwh, mww, dump_image and load_image fast_load does not work for me. But it also did not work before, so I is maybe a different issue. Since I have no access to EJTAG DMA capable devices, I could not test it. BR, Stefan
0001-mips-fix-some-more-endian-madness.patch
Description: 0001-mips-fix-some-more-endian-madness.patch
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
