ST-LINK files for M29W128 External Loader for F407

pmoore · ‎2015-04-13

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

Amel NASRI · ‎2015-04-17

Posted on April 17, 2015 at 17:41

Hi Patrick,

And what do you read exactly at the address 0x1FFFF796 for failing chips with USART bootloader?

-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.

pmoore · ‎2015-04-21

Posted on April 21, 2015 at 23:47

Mayla:

We provided the data we were asked for at the time and never heard any reply. (I didn't send it, so I don't have an archive of it.) We purged the older date code parts from boards once we found the issue seems to be date code range specific, and instructed production to only buy newer date code STM32F303 parts. The issue has not resurfaced with newer parts.

If you have a

http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/LN1848/PF254044?s_searchtype=partnumber

board available with the date codes shown to be an issue, I would expect them to still have the issue.

-Patrick

Tesla DeLorean · ‎2015-04-22

Posted on April 22, 2015 at 22:26

Ok, from an ES 236 on an STM32F3-DISCO, System ROM situated at 0x1FFFD800, bytes at 0x1FFFF796 0x41,0x00

.HEX file attached

________________

Attachments :

STM32F3_236_BOOTROM.hex : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HzTY&d=%2Fa%2F0X0000000bMI%2FeX1bZvm.FnY97xUUBfYCubETj6iQhhZMg78mehHyTFY&asPdf=false

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..