On 01/26/2012 02:15 AM, Luke wrote:
>
>> Auto-probing the parameters from the device would be great it it can be
>> done, but specifying them in the config file would also be OK (and
>> probably easier to implement).
> > From what I can tell, these devices don't make use of the ARM Private
> Periph
> You may either
> a) modify em357.c to support all chips (which would mean renaming it
> afterwards might be in order)
> b) move the common code from em357.c to some separate file, leaving
> em357.c a mostly empty wrapper that calls the common code with the right
> parameters, and add stm32w.c whi
Am 01/25/2012 07:10 AM, schrieb Luke:
> 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.
> I'm trying to get started on the stm32w version and I was
I just noticed that the STM32F1x series (and probably many others)
document the use of the ARM Private Peripheral Bus to program a MCU
device id code, located at 0xE0042000. From what I can tell, neither
the Ember nor the STM32w mention this in their data sheets. I don't
know if this means they j
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.
I'm trying to get started on the stm32w version and I was hoping to
start from em357.c as a template
On 20 January 2012 11:37, Luke wrote:
>>> 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.
>
> The chip I have is the STM32w108CB, which has 8kb of ram and
On 20 January 2012 10:55, Luke 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 irm
>> 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.
The chip I have is the STM32w108CB, which has 8kb of ram and 128kb of
flash. The Ember 351 and 357 both h
> 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.
> # Wireles
On 19 January 2012 23:42, Luke wrote:
> I'm trying to use OpenOCD with an STM32W108B as part of the
> STM32W108B-KEXT kit. The boards are equipped with JTAG cables and I
> have an Olimex ARM-USB-TINY-H cable.
>
> There was a Sparkfun forum post [0] and a couple of mailing list
> messages about th
I'm trying to use OpenOCD with an STM32W108B as part of the
STM32W108B-KEXT kit. The boards are equipped with JTAG cables and I
have an Olimex ARM-USB-TINY-H cable.
There was a Sparkfun forum post [0] and a couple of mailing list
messages about the STM32W, but there doesn't seem to be an appropri
11 matches
Mail list logo
