[En-Nut-Discussion] Virtual disk on STM32 mbed-compatible Nucleo Boards.

[Ringwald Matthias]

Hi Uwe

I’ve also played with the STM32 Nucleo boards. The stklink tools seem to work, at least st-util reports the correct series and RAM/Flash sizes.

I’ve also tried the blinky example from the mbed workbench. After copying the file to the virtual disc, the board did reboot (giving me an error from OS X about unproperly removing a device without unmounting it first). After the reboot, the new firmware was used, but there are no files on the virtual disk.

Best
 Matthias

On 27.02.2014, at 16:32, bon at elektron.ikp.physik.tu-darmstadt.de wrote:

> Hello,
> 
> STM started to sell STM32 nucleo boards and some may have got samples of
> these boards on Embedded world 2014. These board come with ST-Link V2-1 as
> opposed to the STLINKV2 on the discovery boards. The ST-Link V2-1 in
> addition to the ST-Link has a USB Mass Storage
> [scsi 5:0:0:0: Direct-Access     MBED     microcontroller  1.0  PQ: 0 ANSI: 2
> [sd 5:0:0:0: Attached scsi generic sg3 type 0
> [sd 5:0:0:0: [sdc] 1072 512-byte logical blocks: (548 kB/536 KiB)
> 
> for easy. mbed compatible program download. Files on the disk are:
> 
> drwxr-xr-x  4 root root 1024  1. Jan 1970  .
> drwxr-xr-x 26 root root 4096 19. Feb 14:03 ..
> drwxr-xr-x  2 root root 4096 14. Dez 2012  .fseventsd
> -rwxr-xr-x  1 root root  512 14. Dez 2012  mbed.htm
> -rwxr-xr-x  1 root root    0 14. Dez 2012  .metadata_never_index
> drwxr-xr-x  2 root root 4096 19. Nov 17:20 System Volume Information
> -rwxr-xr-x  1 root root    0 14. Dez 2012  .Trashes
> 
> What needs to happen to download a program?
> 
> Is it normal that the flashed program is not visible via the virtual disk?
> 
> Bye
> -- 
> Uwe Bonnes                bon at elektron.ikp.physik.tu-darmstadt.de
> 
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion