Main > Raspberry Pi & Dev Board

Mounted Guns and Arduino mouse mapping

<< < (2/3) > >>

PL1:
1. Are you using the correct bootloader port number?

2. Are you double-click grounding the reset port to put it into bootloader mode just before you run avrdude?


--- Quote from: PL1 on September 10, 2018, 12:28:35 am ---Additional info learned in this thread for anyone using the Arduino AVR procedure on pages 13-14 of the User Guide under "Procedures for non-DFU boards".

Tested the avrdude .bat file on an Arduino Micro and a Pro Micro -- it works perfectly.   ;D

In Control Panel -- Devices and Printers, the bootloader port number is displayed in the device description when the board is put in bootloader mode.

To put a Pro Micro into bootloader mode, double-click ground the RST port as described in the "Reset to Bootloader" procedure here.



--- End quote ---


Scott

syntax_x:
Ok, so i soldered a capacitor leg to the RST via as a dodgy button to ground. Pressed it quickly twice.

Turns out the Pro Micro would change from COM5 in normal mode to COM6 when in bootloader mode.

Had to catch it in the arduino software by making a new sketch to refresh port numbers ect.

Seems to have programmed now.


But shouldnt this type of board work with the mapper flasher instead of having to command line AVRdude?

PL1:

--- Quote from: syntax_x on July 30, 2019, 04:41:48 am ---Ok, so i soldered a capacitor leg to the RST via as a dodgy button to ground. Pressed it quickly twice.

Turns out the Pro Micro would change from COM5 in normal mode to COM6 when in bootloader mode.

Had to catch it in the arduino software by making a new sketch to refresh port numbers ect.

Seems to have programmed now.

--- End quote ---
Glad you got it sorted.   :cheers:


--- Quote from: syntax_x on July 30, 2019, 04:41:48 am ---But shouldnt this type of board work with the mapper flasher instead of having to command line AVRdude?

--- End quote ---
One of the things we wanted to avoid is getting stuck with only one type of board that will only work with Mapper, like what happened with the Minimus boards and the original KADE Loader program.

Bruno wrote the Mapper program to work automatically with either the MattairTech MT-DB-U4 or the custom KADE 32U4 AVRs. (same pinout, similar bootloaders)

Don't know the details, but IIRC there was some obstacle getting Arduino boards/bootloaders to work automatically with the Mapper program.   :dunno

Bruno added the EEPROM HEX and ELF export features and we documented the command line procedure to ensure that the EEPROM/firmware would work with the greatest variety of 32U4 boards/bootloaders, whether or not the Mapper program is ever updated.   ;D


Scott

syntax_x:
After a short play ive found that I had to drop Mame deadzone to 0.

Also x-axis also controls z-axis. Is there a way around that? When I map mame Y-axis looks fine, x axis is a long line with both z axis.

PL1:
KADE miniArcade 2.0's "right analog" stick is on the Z and Zro axes since USB HID Joypads don't use the same axis naming conventions as MAME.
- Mapper calls them X and Y so you know which pot to connect to which port.


--- Quote from: syntax_x on July 30, 2019, 11:02:30 am ---Also x-axis also controls z-axis. Is there a way around that? When I map mame Y-axis looks fine, x axis is a long line with both z axis.

--- End quote ---
That's how Windows displays those four axes by default -- left analog stick on the X and Y box, right analog stick on the Z and Zro bars. (same as my generic USB PS2 controller)

If you'd like to see a test display with cross-hairs in two boxes, use the Pad Test function in Mapper.   ;D


Scott

Navigation

[0] Message Index

[#] Next page

[*] Previous page