On 20 January 2012 10:55, Luke <[email protected]> wrote:
>> It has been a while but it should work.
>>
>> I would check your cfg first - seems to be a few errors.
>> jtag newtap $_CHIPNAME bs -irlen 4 -ircapture 0x0e -irmask 0xf
>> -expected-id $_BSTAPID10 \
>> remove the line continuation char and ircapture and irmask should not
>> be required, eg.
>> # Wireless
>> set _BSTAPID 0x169a862b
>> jtag newtap $_CHIPNAME bs -irlen 4 -expected-id $_BSTAPID
>>
>> Also if i remember correctly the flash controller is not exactly the
>> same as the stm32f1x, may be worth checking the em357 driver.
>> The em35x family are the same device as the stm32w.
>
> Are these part of OpenOCD? I didn't seem them in the target folder,
> but I see that there is a em357.c file in the source.  Do I somehow
> need to indicate that I want to use the em357 driver in the flash
> statement?  Something like:
> flash bank $_FLASHNAME em357 0x08000000 0 0 0 $_TARGETNAME
>
>> Before even attempting gdb, you need to validate that you can control
>> the device, use the telnet interface to check the basic functionality.
>
> When I remove ircapture and irmask, I get the following error:
>
> Error: stm32w108.bs: IR capture error; saw 0x0e not 0x01
> Warn : Bypassing JTAG setup events due to errors
>

strange, use this then:
jtag newtap $_CHIPNAME bs -irlen 4 -ircapture 0x1 -irmask 0xf
-expected-id $_BSTAPID

Also try reducing the jtag clock:
adapter_khz 500

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to