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.
8 years, 1 month ago.
Impossible to download mbed .bin file in the NUCLEO_L011K4 board (free memory space too small)
Hello, I am just trying to use the STM32 NUCLEO_L011K4 evaluation board, by downloading first a very small program (Nucleo_blink-led), But when i try to download the corresponding .bin file (14.4 KByte) in the Nucleo evaluation board, a Windows message box appears saying that the NUCLEO_L011K4 available memory space is too small for that (12 additionnal kByte of memory space will be required for that !).
Remark : I use Windows 10 and I have also properly install the USB driver (STSW-LINK009), and the latest version of the Nucleo ST-LINK/V2 firmware that is currently available.
Thank you in advance for your help !
Question relating to:
7 Answers
7 years, 7 months ago.
Hi, I also have the exact same issue - Bin file is 14.4kb after build and does not fit into the flash drive
7 years, 7 months ago.
I have seen similar limits with an F103 board, it looks like STLink USB drive flashing is not capable of using the full flash size. In my case the .bin was 54k flashing it into a 64kB MCU. I was using Mac OS 10.11
A workaround is to use the STLink tool for flashing, another option would be the “openocd” tool.
7 years, 7 months ago.
I don't know if this help you guys but some time ago I had the same problem. The cause was that I was powering the nucleo externally, for a while before that and then I forgot to switch the jumpers to internal power. I solved by switching the jumpers to internal.
7 years, 10 months ago.
Ran into this same problem (attempt to upload code resulted in an error message that insufficient space was available even though the compiled size was within limits) with a NUCLEO-L011K4 connected to a Mac (macOS Sierra 10.12.2).
Updating to the latest ST-LINK/V2 firmware via the Java app available at the following link (also posted by Jerome Countant with reference to Windows 10) resolved the issue.
7 years, 10 months ago.
I had the exact same issue..
Unplug the USB port, reconnect, and it will work.
8 years, 1 month ago.
+1 for this question. I have the exact same problem. The same way, all firmwares and softwares are up to date.
In some cases I can upload programs with ST-LINK, but the mbed downloaded bin doesn't seem to work with this process. I was able to upload testprogram compiled with gcc. But in that case the OpenOCD doesn't support the chip and cannot do live debug in VisualGDB.
Is this chip/board so new that it's not well supported?
8 years, 1 month ago.
Hi I just tried Nucleo_blink_led with a NUCLEO_L011K4, and I didn't have any issue: compilation, flash, and blinking LED are OK
Note that only micro ARM is supported for this very small target (you can't compile with GCC).
Hello I tried again to compile the very small following program (Nucleo_blink-led) :
- include "mbed.h"
DigitalOut myled(LED1);
int main() { while(1) { myled = 1; LED is ON wait(0.2); 200 ms myled = 0; LED is OFF wait(1.0); 1 sec } }
But as already explain :
when i try to download the corresponding .bin file (14.4 KByte) in the Nucleo evaluation board, a Windows message box appears saying that the NUCLEO_L011K4 available memory space is too small for that (12 additionnal kByte of memory space will be required for that !).
Remark : I use Windows 10 and I have also properly install the USB driver (STSW-LINK009), and the latest version of the Nucleo ST-LINK/V2 firmware that is currently available.
Thank you in advance for your help !
posted by 14 Oct 2016Hello, Thank you for your advice. I have checked the firmware version of my ST-LINK/V2 and this is well the V2J28M16 version. The ST-LINK/V2 is properly recognized by Windows 10, but ever with a very small program (like blink_LED), a Windows message box said that the size of the .bin file (14.4 KByte) is too big to be downloaded in the L011K4 NUCLEO board (free space available : 12,0KByte). Thank you in advance for your help !
posted by 18 Oct 2016
Seeing the same issue, also with older versions of mbed library. Created an issue here and we'll ping ST.
posted by Jan Jongboom 04 Oct 2016