Skip to content

Mass Storage upload "NODE not found error" #41

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.

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

Closed
MauroMombelli opened this issue Sep 30, 2019 · 7 comments · Fixed by #43
Closed

Mass Storage upload "NODE not found error" #41

MauroMombelli opened this issue Sep 30, 2019 · 7 comments · Fixed by #43

Comments

@MauroMombelli
Copy link

If i connect my nucleo to the pc i see the nuvleo recognized as mass storage device.
If i try to program it, i get the error:

An error occurred while uploading the sketch
NODE_F303RE not found. Please ensure the device is correctly connected

I believe that is caused by the fact that the device is seen (lsusb) but does not get automatically mounted (default in kde 5, but for what i find around seems more a systemd stuff)

a quick fix is to ask the user to check if the drive is mounted (it is done once the user try to open it)

a proper fix would be to check if the disk is mounted, and if not it can be mounted/unmounted with 'udisksctl for example: 'udisksctl mount -b /dev/sde /tmp/nucleo

@fpistm
Copy link
Member

fpistm commented Sep 30, 2019

I don't think this is the script which need to perform the mount.
This is to user to do this as it is related to their (system) rules moreover it could required admin rights.

@MauroMombelli
Copy link
Author

MauroMombelli commented Oct 1, 2019

it could required admin rights

this is why udisksctl is used

it is related to their (system) rules

this is the default kde behavior, for what i can find since 2010, see https://www.maketecheasier.com/manage-removable-devices-in-kde/

To the right of the device information, you will see an icon that looks like a plug or connector. Clicking it will immediately mount it but will not perform any further actions. This is useful if you want it mounted but do not necessarily want to access it at the moment.

if you dont click that mount button, the device is connected but not mounted.

I don't think this is the script which need to perform the mount.

good with me, would be nice to simply have a better error message then

@fpistm
Copy link
Member

fpistm commented Oct 1, 2019

if you dont click that mount button, the device is connected but not mounted.

This is linked to KDE behavior, so up to user to properly mount his device.

@fpistm
Copy link
Member

fpistm commented Oct 1, 2019

good with me, would be nice to simply have a better error message then

Do not hesitate to provide a PR with better description, this is a community project, any contribution are welcome.

@fpistm
Copy link
Member

fpistm commented Oct 10, 2019

I will change message when I will fix #42
Any proposition are welcome.

@matthijskooijman
Copy link

IMHO, automatically mounting the device would make sense and certainly make things easier to work with. I'm not sure how easy and portable the udiskctl command is, IIRC there have been quite some different ways how mounting works over the years, some of them desktop-environment-specific, but maybe this somewhat stabilized by now? If there is one somewhat-uniform mounting command, using that would make sense (it would then improve things for a lot of users and keep things unchanged for anyone using some other system)?

@fpistm
Copy link
Member

fpistm commented Oct 11, 2019

I will not add this kind of feature. It is the responsibility of the user to mount a device or configure their rules to automatically mount or not. Moreover, this could rely on some specific commands related to security (ICT rules, ...).

fpistm added a commit to fpistm/Arduino_Tools that referenced this issue Oct 11, 2019
This closes stm32duino#41 and stm32duino#42.

Signed-off-by: Frederic Pillon <[email protected]>
fpistm added a commit to fpistm/Arduino_Tools that referenced this issue Oct 11, 2019
This closes stm32duino#41 and stm32duino#42.

Signed-off-by: Frederic Pillon <[email protected]>
fpistm added a commit to fpistm/Arduino_Tools that referenced this issue Oct 11, 2019
This closes stm32duino#41 and stm32duino#42.

Signed-off-by: Frederic Pillon <[email protected]>
fpistm added a commit to fpistm/Arduino_Tools that referenced this issue Oct 11, 2019
This closes stm32duino#41 and stm32duino#42.

Signed-off-by: Frederic Pillon <[email protected]>
@fpistm fpistm mentioned this issue Oct 11, 2019
fpistm added a commit to fpistm/Arduino_Tools that referenced this issue Oct 14, 2019
This closes stm32duino#41 and stm32duino#42.

Signed-off-by: Frederic Pillon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants