[sdiy] STM32 processor

[Mikko Helin]

Found these Linux utils for ST-LINK:

http://code.google.com/p/arm-utilities/

In the stlink-download.c there are the VID an PID which should be
changed but I think also the

struct stm_chip_params

should be updated to support SMT32F4DISCOVERY kit.

Like the DBG_IDCODE according to data sheet should be

Bits 31:16 REV_ID(15:0) Revision identifier
This field indicates the revision of the device:
0x1000 = Revision A
Bits 15:12 Reserved, must be kept at reset value.
Bits 11:0 DEV_ID(11:0): Device identifier
The device ID is 0x413

Don'w know how this converts, is it 0x10006413 of something else? What
should the bits 15:12 be, these shuld be actually read from the device
I think? So the X in  0x1000X413 is the unknown part (does it matter I
don't know).

The flash and sram size & page sizes should be the easy part when
filling this struct.

- Mikko

On Sun, Oct 16, 2011 at 11:32 PM, Mikko Helin <maohelin at gmail.com> wrote:
> Hi,
>
> Don't know which are the existing stlink-download tool you use but the
> one I spotted used this USB VID and PID from some random
> stlink-access-test.c file found from internet:
>
> // st-link vendor cmd's
> #define USB_ST_VID                      0x0483
> #define USB_STLINK_PID                  0x3744
>
>
> However, after installing the Atollic TRUEStudio in Windoze (XP) and
> checking the connected USB device "STMicroelectronic STLink dongle"
> properties I found the next Device Instance ID with VID and PID for
> the SMT32F4DISCOVERY board:
>
> USB\VID_0483&PID_3748\5&340A0F05&0&1
>
> So if you have the C code available for recompilation in Ubuntu try
> changing the PID to 0x3748. Can't guarantee it will work, though I
> suspect the protocol has been changed (guess ST-LINK has some versions
> but guess it's backwards compatible anyway).
>
> Does the existing Linux toolchain  support the use of Eclipse? I would
> be quite lost without it (guess other Java coders as well).
>
> - Mikko
>
>
> On Sun, Oct 16, 2011 at 7:04 AM, Eric Brombaugh <ebrombaugh1 at cox.net> wrote:
>> Bad news re: the STM32F4 discovery board: got mine in today, hooked it up to
>> the Ubuntu box and while it powers up, the USB VID/PID are not recognised
>> and it doesn't appear to be compatible with the existing stlink-discovery
>> download tool.
>>
>> So, absent use of the Winders-based IDEs, and until someone manages to
>> reverse-engineer the new protocol this board is useful for pretty blinky
>> lights.
>>
>> Eric
>>
>> On 10/15/2011 01:15 PM, Mikko Helin wrote:
>>>
>>> Tried Atoll TRUEStudio, work OK, just got to remember to avoid spaces
>>> in path names (so in Winxx don't unzip or create workspaces under "My
>>> Documents").
>>
>>
>