cancel
Showing results for 
Search instead for 
Did you mean: 

STM32 Nucleo-L053R8 board: ''No space left on device'' on linux

Raghavendra Kandur
Associate II
Posted on January 16, 2017 at 05:14

Hi,

I am downloading an elf file to STM32 Nucleo-L053R8 board.  The size of elf is given below:

text       data        bss        dec        hex    filename

54700        728       3504      58932       e634    ../mDigitalIO_ADC.elf

In Linux, for the very first time, the elf successfully downloaded to the target and running properly.  But next time if try to download I am facing the following issue:

No space left on device

If the board is disconnected and reconnected to the Linux machine the download is successful but the second time the same issue occurs.

But in windows, the repeated downloading to the target using simple copy commands works well and the elf runs successfully.

Is there any way to download the elf to Nucleo-L053R8 board without disconnect and reconnect on Linux machine without using st-link debugger instead using just 'cp' command.

Regards,

Raghavendra

12 REPLIES 12
Posted on January 16, 2017 at 12:47

My comment is meant to say: I never worked with this mbed bootloader.

I don't need this intermediary step, which might introduce additional trouble ...

Your issue most probably has to do with the inter-work between host OS (Windows/Linux) and the mbed bootloader.

As you noted in one of your former posts:

...as soon as executable is loaded the executable disappears.

So it disappears for the host OS (Linux) as well. So obviously the BL hides the loaded file - which, I guess, is far from being conforming to the USB MSC profile. And Linux mainline drivers are known to be quite stable and conforming.

In your place I would ask the people maintaining this BL - not sure if this is ST here, or MBED.

I have no skins in this game ...

Posted on January 16, 2017 at 14:06

Run

mount

and show us the result.

JW

DKASA
Associate II

Nucleo 144 H563ZI - same error message "out of space" fw update on Win10 fixed it right away.