On 17 January 2012 13:35, Jonathan Dumaresq <jdumar...@cimeq.qc.ca> wrote: > > The stlinkV2. I got some of the protocol working but I could not get the > flash programmed. I can write to ram but could not get it work with the > flash. > > I try to disable the working area to have the jtag adapter to write directly > thru the register but this is not working too. I try to bisect the st-link > Utility but if I write to 1 word of flash or 1024 byte of flash they always > download the flash helper in ram. > > Until now, I can get the device reconised by openOCD with the device ID. and > Revision too. > > Regards >
Looking at the datasheet it looks as if it uses the same flash controller as stm32f1 (stm32f1x.c). Now as you are using the stlink most of the armv6m stuff is hidden from OpenOCD - this is assuming the stlink correctly supports armv6m. I cannot see anything in the armv6m arch ref that would cause any problems. The issue you will have is that stm32x_probe will not understand the target it finds. What is returned by reading 0xE0042000 ? At this stage we will also want to disable any working areas, until we update the stm32x_flash_write_code for armv6m. Does a stm32x mass erase succeed? Cheers Spen ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel