On 09/02/2010 15:35, Edgar Grimberg wrote: > There's the test run. At address 0x08000000, according to flash info > 0, there should be the flash. The RAM is at 0x20000000. You can see > that it fails to read the flash, but it manages to read the RAM just > fine: > > $ sudo src/openocd -f > /home/edgar/workspace/openocd/tcl/interface/parport.cfg -f > /home/edgar/workspace/openocd/tcl/target/stm32.cfg -d3 -llog.txt > >> reset init > JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: > 0xba00, ver: 0x3) > JTAG tap: stm32.bs tap/device found: 0x16410041 (mfg: 0x020, part: > 0x6410, ver: 0x1) > target state: halted > target halted due to debug-request, current mode: Handler HardFault > xPSR: 0x01000003 pc: 0xfffffffe msp: 0xffffffdc >> mdw 0x08000000 32 > JTAG-DP STICKY ERROR > MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x8000004 > JTAG-DP STICKY ERROR > MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x8000004 > Block read error address 0x8000000, count 0x20 > Command handler execution failed > in procedure 'mdw' called at file "command.c", line 650 > called at file "command.c", line 361 >> mdw 0x20000000 32 > 0x20000000: deadbabe deadbabe deadbabe deadbabe deadbabe deadbabe > deadbabe deadbabe > 0x20000020: deadbabe deadbabe deadbabe deadbabe deadbabe deadbabe > deadbabe deadbabe > 0x20000040: deadbabe deadbabe deadbabe deadbabe deadbabe deadbabe > deadbabe deadbabe > 0x20000060: deadbabe deadbabe deadbabe deadbabe deadbabe deadbabe > deadbabe deadbabe > > The log is attached. > > I get the same result if I try to mdw 0 32. >
Just tried this with two separate boards and working ok here. Up until the mdw the log is the same as mine, i am using a ftdi based adapter. I can try a parport wiggler tomorrow. For info the HardFault is quite normal when you have an erased device. The device is not read protected is it? stm32x options_read 0 Cheers Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
