Main > Main Forum
KADE miniArcade 2.0 beta release
PL1:
--- Quote from: lilou on February 06, 2020, 04:55:03 pm ---the buttons correspond to the basic software assignment not mine (exemple X is F5 but i asked X=D2)(other exmple : Left stick is on D3, but i don't assigned left stick on the mapper...).
I don't anderstand what go wrong
I put my own assignment on "kade miniarcade2.0 gamme mapper", i export to EEPROM.eep on the avrdude folder (i checked, the code inside eeprom file is different if i change assignment on mapper).
--- End quote ---
1. Is there a reason you reassigned ports instead of using the defaults?
Seems easier to wire using the defaults than to change the ports. :dunno
2. Since the buttons correspond to the defaults instead of your custom settings, you might be programming the board using the original EEPROM file.
--- Quote ---If the EEPROM file is not loaded to the board, the HEX firmware reverts to the default joypad configuration.
--- End quote ---
After you exported the custom EEPROM, did you copy the new "EEPROM.eep" file from the "\firmwares\" folder to the avrdude folder? (User Guide, page 14, step 5)
3. When you reassigned ports, did you check that the same port wasn't assigned to more than one function? (User Guide, page 5, step 6)
4. Leaving an xBox function like Left Stick with the "Input As" port set to blank might cause problems for the firmware -- not sure if Bruno tested this possibility. :dunno (User Guide, page 5, step 6)
The defaults for Xbox have a port assigned to Button Mapping ID #s 0-5, 8-11, 13-17.
5. You may need to set Output Mode to "Force Xbox". (User Guide, page 4, step 4)
Scott
lilou:
--- Quote ---1. Is there a reason you reassigned ports instead of using the defaults?
--- End quote ---
yes because arduino Pro micro do not have all buttons available. Only 12 output available, so i need to choose.
--- Quote ---2. Since the buttons correspond to the defaults instead of your custom settings, you might be programming the board using the original EEPROM file
--- End quote ---
ok it's probably that
--- Quote ---After you exported the custom EEPROM, did you copy the new "EEPROM.eep" file from the "\firmwares\" folder to the avrdude folder? (User Guide, page 14, step 5)
--- End quote ---
yes i did
--- Quote ---3. When you reassigned ports, did you check that the same port wasn't assigned to more than one function? (User Guide, page 5, step 6)
--- End quote ---
yes i did, because i puted "blank" on unused buttons
--- Quote ---4. Leaving an xBox function like Left Stick with the "Input As" port set to blank might cause problems for the firmware -- not sure if Bruno tested this possibility. :dunno (User Guide, page 5, step 6)
--- End quote ---
ok... this is a serious possibility in my case
--- Quote ---5. You may need to set Output Mode to "Force Xbox". (User Guide, page 4, step 4)
--- End quote ---
i tried that but nothing change.
lilou:
ok so, i try again.
I put the default setup, i juste flip A and B with Dpad up and down (no "blank" exept by default, and i check that the same port wasn't assigned to more than one function)
i flash the arduino and nothing change on xbox...
so do you see a mistake ? :
thank you
PL1:
--- Quote from: lilou on February 07, 2020, 07:03:16 am ---so do you see a mistake ?
--- End quote ---
The command line looks correct. ;D
The flash programming (MINIARCADE2.hex) messages look good, but there are no messages in the image you posted indicating that EEPROM programming (EEPROM.eep) was even attempted. :banghead:
1. When you ran that command did you get any other messages that aren't in the image?
2. Is there a copy of your custom "EEPROM.eep" in the "avrdude" folder where you typed in the command line?
3. Is the filename exactly "EEPROM.eep"?
- IIRC avrdude filenames are case sensitive so "EEPROM.EEP" or "eeprom.eep" won't work.
4. Does the creation date match the date you exported your custom file?
- "dir /p" for a directory listing with prompt so list doesn't scroll off the screen before you can read it.
5. If 1 is no and 2-4 are yes, your Pro Micro's bootloader or fuse settings might be the problem. :dunno
- I don't remember seeing another Pro Micro knockoff that uses COM12.
Scott
lilou:
--- Quote from: PL1 on February 07, 2020, 10:00:43 am ---but there are no messages in the image you posted indicating that EEPROM programming (EEPROM.eep) was even attempted. :banghead:
--- End quote ---
that's exactly what i noticed
--- Quote ---1. When you ran that command did you get any other messages that aren't in the image?
--- End quote ---
nothing
--- Quote ---2. Is there a copy of your custom "EEPROM.eep" in the "avrdude" folder where you typed in the command line?
3. Is the filename exactly "EEPROM.eep"?
- IIRC avrdude filenames are case sensitive so "EEPROM.EEP" or "eeprom.eep" won't work.
4. Does the creation date match the date you exported your custom file?
--- End quote ---
yes for all
--- Quote ---- "dir /p" for a directory listing with prompt so list doesn't scroll off the screen before you can read it.
--- End quote ---
--- Quote ---5. If 1 is no and 2-4 are yes, your Pro Micro's bootloader or fuse settings might be the problem. :dunno
- I don't remember seeing another Pro Micro knockoff that uses COM12.
--- End quote ---
i don't know what it mean :embarassed: