-
Hi! However when I flash it with mega2560_muxsh2.hex writing completes successfully but after connecting the board to the computer directly without programmer the board is not recognized by the system (not appearing as usb device neither in Windows nor in Macos). OpenDeck configurator says "No OpenDeck board found. Please connect the board in order to use the interface." Regardless if I connect it with Mux Shield 2 installed on the top of arduino or not. Is there anything specific I need to do to make it work with Mux Shield apart from loading dedicated firmware? I'm flashing on M1 Macbook using avrdude and arduino uno as a programmer. EDIT: I noticed that "L" led on the Mega board is constantly glowing after flashing mega2560_muxsh2.hex variant while it is off with standard firmware. Not sure if this means anything. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
And here is the log from flashing, if it helps in any way: tomek@MacBook-Air-Tomek ~ % "/Users/tomek/Library/Arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/bin/avrdude" "-C/Users/tomek/Library/Arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/etc/avrdude.conf" -v -V -patmega2560 -cstk500v1 -P/dev/cu.usbmodem1201 -b19200 "-Uflash:w:/Users/tomek/Downloads/mega2560_muxsh2.hex:i" avrdude: Version 6.3-20190619
avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.03s avrdude: Device signature = 0x1e9801 (probably m2560) Writing | ################################################## | 100% 73.23s avrdude: 77556 bytes of flash written avrdude: safemode: lfuse reads as FF avrdude done. Thank you. |
Beta Was this translation helpful? Give feedback.
-
Today I set up the environment on Ubuntu 22.04, including installing Docker and cloning OpenDeck repository as I thought maybe there is something wrong with flashing on Mac. |
Beta Was this translation helpful? Give feedback.
-
It's most likely that the configuration for the variant with Mux Shield v2 uses too much RAM and hence crashes. Try removing some of the stuff you don't use from the configuration - touchscreen, I2C display, DIN MIDI etc. |
Beta Was this translation helpful? Give feedback.
-
I removed dinMIDI and i2c from the config file and boom! it worked perfectly :) |
Beta Was this translation helpful? Give feedback.
It's most likely that the configuration for the variant with Mux Shield v2 uses too much RAM and hence crashes. Try removing some of the stuff you don't use from the configuration - touchscreen, I2C display, DIN MIDI etc.