simon qian <simonqian.openocd@...> writes: > > > It's fast for 27kBytes/s for flash + erase. STM32F200 has 16M internal RC, so > the JTAG can run at 2.5M. > > As I test for STM32F100, flash programming is usually at 13KBytes/s under > OpenOCD. > > > ST website is not available in China, I don't know the state of STM32F200. > I have placed an sample order of 20 STM32F205 1M/64Pin, and they only give > the price, but not sure about when I can get it. > > The PCB will be sent to factory next week.2011/2/3 Øyvind Harboe > <oyvind.har...@zylin.com> > On Wed, Feb 2, 2011 at 7:53 PM, simon qian > <simonqian.open...@gmail.com> wrote: > > > I have one STM32F207, but PCB will be available at end of this month. > > I'll go to ST this month for some STM32F205s if available. > > I can do the test if I can get the samples, but only for SWD, because there > > is only SWD available in my PCB. > That's great! > In my first tests I'm seeing 27kBytes/s for flash + erase. 128kBytes > sectors takes > as much as 1000ms to erase(per the datasheet). > I was able to clean up the branch, but I want to let it cool off > before I merge it. > -- > > Øyvind Harboe > Can Zylin Consulting help on your project? > US toll free 1-866-980-3434 / International +47 51 87 40 > 27http://www.zylin.com/zy1000.html > ARM7 ARM9 ARM11 XScale Cortex > JTAG debugger and flash programmer > > > > > -- Best Regards, SimonQianhttp://www.SimonQian.com > > > > _______________________________________________ > Openocd-development mailing list > Openocd-development@... > https://lists.berlios.de/mailman/listinfo/openocd-development >
The driver works great. Here is my experience with it. I went to openocd, Downloaded the get repo, built. The first time I flashed code, everything worked great. The second time, I ran into issues. When I was trying to flash, I got the follow: Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40023c08 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40023c08 Finally I got a fix. First, ensure the blocks aren't write protected Inside gdb, run this: monitor mdw 0x40023c14 should yield 0x0fffaaec If you don't get 0x0fffxxxx, do the following: reboot the board monitor mww 0x40023c08 0x08192A3B monitor mww 0x40023c08 0x4C5D6E7F monitor mww 0x40023c14 0x0fffaaec reboot the board monitor mdw 0x40023c14 should yield 0x0fffaaec Second, here is my program script, the key is that you must clear any error bits at 0x40023c0c: #Get the system ready to run these commands init #flash a program halt sleep 10 #Clear any flash errors REQUIRED! sleep 10 mww 0x40023c0c 0xf3 #Flash my code sleep 10 flash probe 0 flash write_bank 0 /tmp/target.bin 0 # get thsi thing started again reset init reset run shutdown Great job on the stm32F207 driver, thanks! -Orbital_sFear _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
