Steve Suddarth

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

7 years, 9 months ago.

DISC1 board board is "forgetting" files

When I plug in my STM32F429i-DISC1 board drive, the drive shows up fine on my Win10 machine. I then compiled the mbed LCD demo and tried to program it. When I drag-and-drop a program (or any other file) into "DIS_F420ZI" (E:) window, the file seems to copy fine and shows up under windows explorer. However, rebooting the board does nothing but give me a blank white screen. When I then unplug and replug the USB ST-LINK, the drive comes up, but the file copied is GONE! No matter what files I copy into the DISC1 board, they disappear when I restart it so the flash does not appear to be persistent. I have upgraded the board firmware and the ST-LINK driver. I have tried this with 2 Win10 computers with the same behavior on both.

Question relating to:

Last updated: 12 Aug 2020
The STM32F429 Discovery kit (STM32F429I-DISC1) allows users to easily develop applications with the STM32F429 high-performance MCUs with ARM®Cortex®-M4 core.

2 Answers

bco stm
7 years, 9 months ago.

Hi,

The disk you see when you plug the board is not a real mass-storage device. It is normal that the bin file disappears after it has been flashed.

Your problem is related to a bug introduced by uVisor in mbed v135 and v136. It should be solved in v137. In the mean time you can use v134.

Accepted Answer

Thanks for the reply! I'm afraid I don't understand. I don't build uVisor into my test project (at least not explicitly). When I look up uVisor, it appears to be designed to handle SSL, but I can't even get a simply LED demo to work. Do you know what I'm missing?

posted by Steve Suddarth 22 Feb 2017

OK, I got it it was my fault in that I thought you were suggesting rolling back revisions on the discovery board library. I rolled back the MBED library to v134 and it worked perfectly. Thanks!!

posted by Steve Suddarth 24 Feb 2017
Mark Peter Vargha
7 years, 9 months ago.

It is a known bug. https://github.com/ARMmbed/mbed-os/issues/3788