Hello, this is my first post here, so I'll try to stick to proper etiquette, but let me know if I'm doing something wrong.
I am building a MIDI controller using an Arduino UNO, and would eventually like to progress from the Arduino to a PCB.
For context, I'm following Logan Nimo's instructions from this video:
In the final stage, two of the ISCP pins on the Arduino are shorted and a hex file is uploaded using Atmel FLIP.
For the life of me, I can't seem to figure this out:
Why do the ISCP pins have to be shorted in the first place?
How would I go about uploading the hex file to a standalone AtMega328P microcontroller - would I have to also include those pins on the PCB/breadboard in order to short them before uploading the hex file?
If this is a newbie question or the answer is glaringly obvious, I'd like to point out that I am VERY new and basically know next to nothing about embedded engineering...
to get an Uno to speak Midi, you have to re-program the 16u2 that normally does the usb-to-serial converstion as well as the main Atmega328. Since this is a much less common thing to do, it requires certain pin states to get the 16u2 to run its bootloader (whereas the 328 ALWAYS runs the bootloader.)
(that also means that your custom board will require both a 328 and a 16u2.)
If your goal is Midi from the start, you'd be better off starting with a board that has native USB and doesn't need two chips re-programmed, like a Leonardo or Arduino Micro.
Many many thanks for the amazing reply! It really put things in the correct perspective.
So, if I understood correctly, the better way to go about this is to use a standalone ATMega32u4 microcontroller, burn the Arduino bootloader onto it, add the code and finally upload the MIDI hex file?
the better way to go about this is to use a standalone ATMega32u4 microcontroller, burn the Arduino bootloader onto it, add the code and finally upload the MIDI hex file?
