Skip to content
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

Unable to flash 360--permissions error #459

Closed
kelvinfann opened this issue Apr 25, 2024 · 18 comments
Closed

Unable to flash 360--permissions error #459

kelvinfann opened this issue Apr 25, 2024 · 18 comments

Comments

@kelvinfann
Copy link

% sudo cp firmware/202404250542-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/left.uf2
Password:
cp: /Users/kelvinfann/../../Volumes/ADV360PRO/left.uf2: Operation not permitted

When I try to copy the firmware files to set the layout I am not allowed to?

Running on a mac Sonoma 14.4.1 and the build seemed fine

@kamalkech
Copy link

with expensive price should support client
@kelvinfann me too i get the same error

@KinesisCorporation
Copy link
Owner

Hi folks,

We just tested copying files to a 360 Pro here from a MBP Running Sonoma 14.4.1. We got the now "standard" faux macOS error about file transfer but the update was nonetheless successful, so this doesn't seem to be a keyboard issue per se.

@ReFil Any thoughts?

image image

@KinesisCorporation
Copy link
Owner

Were you able to get it working?

@kelvinfann
Copy link
Author

kelvinfann commented Apr 30, 2024

Hi folks,

We just tested copying files to a 360 Pro here from a MBP Running Sonoma 14.4.1. We got the now "standard" faux macOS error about file transfer but the update was nonetheless successful, so this doesn't seem to be a keyboard issue per se.

@ReFil Any thoughts?

image image

  1. Using the macro the version is not updated--and you can tell because the keys were not remapped
  2. I tried on a couple of macs and none seem to work unfortunately
  3. I'll try the firmware tonight and get back

@ReFil
Copy link
Collaborator

ReFil commented Apr 30, 2024

Have you tried dragging and dropping the firmware on to the board in finder? I wonder if changing the destination name is throwing the bootloader off. It doesn't work like a real USB drive, it's emulating mass storage functionality so it may not support the rename operation, hence the permission denied error

@GoByeBye
Copy link

It seems the issue is that you're trying to rename the file along with copying it.
Same issue happens on Ubuntu 24.04 LTS if you try to cp with a rename of the file.

@ReFil is probably onto something in his comment

The proper command to copy it would be cp firmware/202404250542-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/ or cp firmware/202404250542-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/202404250542-d4b2204-left.uf2 as that leaves the file name intact

@kelvinfann
Copy link
Author

kelvinfann commented May 2, 2024

@GoByeBye I actually ran those cp commands first before I tried anything in finder--still no dice; I think this device has to go back for me unfortunately. Back to the advantage 2 I go. I'll check back in like 3 months when I switch desktop setups to see if this issue is resolved

% cp 202404292324-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/
cp: /Users/kelvinfann/../../Volumes/ADV360PRO/202404292324-d4b2204-left.uf2: Operation not permitted
% ls ~/../../Volumes/ADV360PRO/
CURRENT.UF2	INDEX.HTM	INFO_UF2.TXT
% cp 202404292324-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/
cp: /Users/kelvinfann/../../Volumes/ADV360PRO/202404292324-d4b2204-left.uf2: Operation not permitted
% cp 202404292324-d4b2204-left.uf2 ~/../../Volumes/ADV360PRO/202404292324-d4b2204-left.uf2
cp: /Users/kelvinfann/../../Volumes/ADV360PRO/202404292324-d4b2204-left.uf2: Operation not permitted

@ReFil
Copy link
Collaborator

ReFil commented May 2, 2024

@kelvinfann will the file not copy over in finder either?

@abreinig
Copy link

You can also try to flash with your mobile phone if you have Android. I'm not sure if it'll work with iPhone.

@pavveu
Copy link

pavveu commented Jul 12, 2024

i have the same issue on mac, seems to be the problem with the partition schema (when checking in terminal) but not sure if running command for repairing the partition schema is good idea... so probably will skip it for now. Checked permission - seems good, checked free space, also good.

$ diskutil verifyDisk /Volumes/ADV360PRO
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition
scheme, you might be able to repair it with "diskutil repairDisk /Volumes/ADV360PRO"

@ReFil
Copy link
Collaborator

ReFil commented Jul 12, 2024

Writing the partition scheme will do nothing, the board bootloader will not recognise that as a valid command

@pavveu
Copy link

pavveu commented Jul 12, 2024

will try from my windows desktop, but if it doesnt work does it mean its something with the drive on the keyboard?
also i noticed that the files that i have installed are from 2022 - does it mean i need to run some upgrade before flashing ZMK (got the keyboard today, wanted to change the layout and remap some keys)

Screenshot 2024-07-12 at 19 06 44

@ReFil
Copy link
Collaborator

ReFil commented Jul 12, 2024

The date on those files is the compile date of the bootloader, it bears no relevance to the firmware you can install. The drive is not a real drive, it is emulated, if the main firmware works properly it is highly unlikely there is anything wrong

@pavveu
Copy link

pavveu commented Jul 12, 2024

i've used mod+v to print the version, it seems it was uploaded - its printing the date and version hash, so it seems to work but some of the keys are not working on the FN layer
Basically fn+ (= and 1-9-0) works as f1 to f12
but the lower the keys below it, doesn't. the mod3 key - where i assigned f12 works. On other keyboards that i have f13-f24 works normally. So it's not some system setting i assume, in this configuration -> as seen on the screen f13-f24 doesnt work

Screenshot 2024-07-12 at 21 26 47

@pavveu
Copy link

pavveu commented Jul 12, 2024

also i assigned some keys under num layer - and they work. i cannot understand why in this scenario f13-f14 and rest doesnt work as intended

@KinesisCorporation
Copy link
Owner

F13-F24 were in conflict with NKRO. Trying disabling NKRO.

https://kinesis-ergo.com/support/kb360pro/#faq

@pavveu
Copy link

pavveu commented Jul 12, 2024

works like charm, thanks for the patience ;)

@KinesisCorporation
Copy link
Owner

Great!

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

No branches or pull requests

7 participants