Skip to content

Unable to upload using massStorageCopy #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
RickKimball opened this issue Jun 10, 2017 · 3 comments
Closed

Unable to upload using massStorageCopy #23

RickKimball opened this issue Jun 10, 2017 · 3 comments
Labels
question ❓ Usually converted as a discussion

Comments

@RickKimball
Copy link
Contributor

I'm creating a new variant for the NUCLEO-F030R8. When using the massStoraryCopy build, platform.txt uses the {node} parameter of the board to decide where to copy the bin file at upload time. This fails for me when I follow the scheme used by all the other board.txt entries.

On my 64 bit linux 16.04, my NUCLEO-F030R8 board shows up with the name mass storage name of "NUCLEO" instead of "NODE_F030R8".

I tried running Win7 in a VM and it also shows up as "NUCLEO" there.

Is there an expected driver or udev entry I'm supposed to be using? Or should the my board entry look like this:

Nucleo_64.menu.Nucleo_64_board.NUCLEO_F030R8.node=NUCLEO

BTW: that works properly
@fpistm
Copy link
Member

fpistm commented Jun 11, 2017 •
edited
Loading

Yes you have to set it with NUCLEO as displayed by the host os. For other board this is also the name diplayed by host os.

@fpistm fpistm added the question ❓ Usually converted as a discussion label Jun 11, 2017
@fpistm
Copy link
Member

fpistm commented Jun 13, 2017 •
edited
Loading

As I have mentioned in other thread.
The mount point of my F030R8 is:
/dev/sdc on /media/<login>/NODE_F030R8 type vfat (rw,nosuid,nodev,uid=xxxxxx,gid=xxxxxx,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)

@fpistm fpistm mentioned this issue Jun 14, 2017
Closed
@fpistm
Copy link
Member

fpistm commented Jun 14, 2017

This issue was moved to stm32duino/Arduino_Tools#6

@fpistm fpistm closed this as completed Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question ❓ Usually converted as a discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RickKimball @fpistm