On Thu, Nov 7, 2013 at 7:02 PM, Greg Hutchins <ghutch...@gmail.com> wrote:
> I am trying to run openocd.0.7.0 with an STM32F407vet6 and am running into
> an issue where the code tries to change the device-id from a 0x411 part to
> a 0x413 part, but I think this code was only supposed to be for RevA
> silicon and we are using RevB silicon. Wondering if anyone has encountered
> this issue, or if it has been fixed in a newer development version.
>
>
>
Not sure what you mean you have a problem with, but there are several fixes
to the stm32f2x flash driver since 0.7.0 so you may want to use a newer
build. The code handling the stm32f4x errata I think you're talking about,
is still the same as in 0.7.0 though. Does it not work? Even if it doesn't
check the revision code, there shouldn't be any 0x411 with a Cortex-M4,
right?
/Andreas
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
