cancel
Showing results for 
Search instead for 
Did you mean: 

ST-LINK files for M29W128 External Loader for F407

pmoore
Associate II
Posted on April 14, 2015 at 01:16

I have an application with a F407 that has a correctly working M29W128 that happens to be on NE1 (so the starting address is 0x60000000).  The application works wonderfully using a resident bootloader that accepts a large file via Ethernet that fills the balance of the internal F407 flash and then ''overflows'' into the external M28W128 as needed.

For production, it would be easier if I could load the external flash via SWD using the ST-LINK, but the ST-LINK software does not seem to have pre-existing loader for my configuration.  The ST-LINK Utility 3.6.0 documentation tells me how to create my own loader, but the directory with the source code for the M29W128 is empty.  The other three other memory types are fully populated with files. 

Does anyone know where I might be able to find the ST-LINK external loader code examples for the M29W128?

#st-link-m29w128-f407 #f303-bootloader
12 REPLIES 12
Posted on April 14, 2015 at 05:35

Looked familiar, dupe

Pushing to moderation.

Edited: Removed pointless DEAD LINK to now non-existent duplicate post.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
pmoore
Associate II
Posted on April 14, 2015 at 17:36

Hi Clive1.  Technically I think this is the right spot for it to live, as it's really a software tool issue.  I have no clue on this site how to shift an item from one area to another, so I reposted it here in STM32 Software Tools.

Posted on April 14, 2015 at 18:21

If this was real forum software things could be managed, I've flagged the post so someone at ST has it as an action item, we'll see if it gets a response.

Really the FAE's should participate here, and honestly I don't see that.
Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
pmoore
Associate II
Posted on April 14, 2015 at 19:05

I had an issue (still have really, just found a work around) with the STM32F303 from the first year of production with the built-in USART bootloader (no issue getting it to work with the F051 or F100 or F407), in an application with a master F407 updating the flash on 4 slave processors.  It turns out that after a datecode, the problem went away, as I found by trial and error.  Still waiting for the ST FAEs to get back to me (or one of the distributor's FAEs that also put in the request)...still waiting for it to show up in the errata.  Perhaps 25K+ STM32 parts per year isn't enough to be bothered for?  FAEs seem to be mythical beings, so it's good news that the STM32 parts are a great value and most things are documented well enough that with some trial and error, they can be utilized.

Thanks for taking your time to be a light in the darkness here.

Amel NASRI
ST Employee
Posted on April 15, 2015 at 10:04

Hi Clive,

I removed the other input in order to avoid repeated posts.

We keep the tracking of issues only in this thread.

Hi Patrick,

Your first problem with the ST-Link is under review. We will keep you informed.

Regarding the second issue faced with STM32F303 parts, for sure FAEs are investigating it and will come back to you as soon as they have more information to be shared.

You may provide in this thread more details on the used part (datecode of parts with problem and the one for others where there is no issue...).

You may also share any information that seems helpful to understand clearly the situation.

Thanks for your interest and welcome for all your valuable feedbacks.

-Mayla-

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Nickname306_O
Senior
Posted on April 15, 2015 at 13:30

Hi Patrick,

Seems an installation problem from your side.

To unblock the situation, please find here attached the M29W128 flash loader.

Best Regards,

Nouha

________________

Attachments :

M29W128GL_STM3210E-EVAL.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HzTd&d=%2Fa%2F0X0000000bMN%2FQdGUvOEp0cXvuAYt79lRA7uihJf9ShoUAHC4mekqNuQ&asPdf=false
pmoore
Associate II
Posted on April 15, 2015 at 17:42

Hi Nouha:

Thanks for the archive of files.  I downloaded ST-LINK Utility_v3.6.0 on Feb 27th, 2015. 

I notice the file dates in the archive you provided are from March 31st, 2015.

I had installed ST-LINK 3.6.0 on three machines and two different versions of Windows without a change in the folder contents.  Do the files in the ST-LINK utility installation available for download from the ST website continue to update without the listed version updating?  If so, I'll download fresh copies of the installation each time in the future.  Historically, I have downloaded the utility only when the release version changed.

-Patrick

pmoore
Associate II
Posted on April 15, 2015 at 19:22

Hi Mayla:

This information is from Q4 of 2013, ST Online support issue# R13470053 assigned to Cristian Tomescu:

STM32F303VCT6 have non-functioning bootloader, or perhaps just do not have the bootloader installed, as the bootloader never responds. We had correct functionality with STM32F407IGT6 and STM32F100(various memory and QFP package configurations) parts.

The earlier date codes we tried:

STM32F303VCT6 with date code 236 (which we made a pilot production run with)

STM32F303VCT6 with date code 241 (which was on several STM32F3discovery board we bought, plus 2 gifted to us)

----

In early Q1 2014, by trial and error (buying parts after validating the date codes did not match what we already had tried), we found that STM32F303VCT6 with date codes 247 and 302 had correct functionality for the USART bootloader in the same hardware and software environments that the earlier date code parts failed to function in. (In the time since, the with later date codes, the problem has not been seen again.)

We read the first few bytes starting from 0x1FFFF796 (per Cristian's request) and validated something had been installed for the bootloader in all of the STM32F303VCT6 parts. We also provided schematics for the application, which are the same as we use today in functioning product(s).

All the F303 date codes tried, both with working and non-working USART bootloaders, are marked as revision ''Y''

I checked the STM32F303xB/C errata (DocID023637 Rev 6, February 2015), and the bootloader issue is not noted.

Also see:

https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/stm32f303%20bootloader%20problem

- li.max - 11/13/2013 (Max is one of the programmers that worked on this project with me.)

-Patrick

Nickname306_O
Senior
Posted on April 16, 2015 at 15:53

Hi Patrick,

No, all the files are only vailable throw the ST-LINK Utility Setup on the web site (besides the documents; User manual..)

You'll find in attach the same, archive dates from 16/02 if you want.

Best Regards,

Nouha

________________

Attachments :

M29W128GL_STM3210E-EVAL.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HzR4&d=%2Fa%2F0X0000000bMM%2FdyKNzNLh6WSuSK4qBviZd5hGdJ15aPZtYWIdY3ttpiA&asPdf=false