Hello!
First of all, thanks for this amazing software and all the hardware work! It's certainly an impressive project!
I was thinking of using it with my PS4 but I have a question regarding the Development board.
Will it work with any USB development board which has the atmega32u4 processor?
So would it work with, for example, this one? http://www.ebay.com/itm/Leonardo-Pro-Mi ... 3ce4285eb2
I have a few atmega328p at home but I noticed that they won't do. =)
Thanks for the help!
Choice of USB-development board
Re: Choice of USB-development board
Hello,
The main issue with the "Leonardo pro micro" board is that it uses the USB port as a programming interface.
I think it should be possible to load a firmware with the arduino builder.
But once the new firmware is flashed you loose the programming interface as the USB port is now used for another purpose...
The main issue with the "Leonardo pro micro" board is that it uses the USB port as a programming interface.
I think it should be possible to load a firmware with the arduino builder.
But once the new firmware is flashed you loose the programming interface as the USB port is now used for another purpose...
GIMX creator
Re: Choice of USB-development board
OK, I will give it a shot once the board arrives and report back how it went.
About it losing the USB-port as programming interface don't bother me that much since I consider the board dedicated to gimx and I won't need to reprogram it again will I for use in gimx?
The firmware to flash, is it the atmega32u4.hex that is in the firmware zip?
Thanks! Your help is greatly appreciated!
About it losing the USB-port as programming interface don't bother me that much since I consider the board dedicated to gimx and I won't need to reprogram it again will I for use in gimx?
The firmware to flash, is it the atmega32u4.hex that is in the firmware zip?
Thanks! Your help is greatly appreciated!
Re: Choice of USB-development board
The firmware can be improved, and there generally is no backward compatibility (new software vs old firmware).Luggzon wrote:About it losing the USB-port as programming interface don't bother me that much since I consider the board dedicated to gimx and I won't need to reprogram it again will I for use in gimx?
Exactly.Luggzon wrote:The firmware to flash, is it the atmega32u4.hex that is in the firmware zip?
GIMX creator
Re: Choice of USB-development board
OK, but if the firmware needs a update would it be possible to flash back the original bootloader using the ICSP and then load the new firmware?
Re: Choice of USB-development board
With an ICSP you can directly flash the GIMX firmware 

GIMX creator
Re: Choice of USB-development board
Hehe yeah I realized 2 sec after the post that that probably would be easier =)
I'll get back to you on how it goes once my board arrives. Could be a bit cheaper alternative =D
I'll get back to you on how it goes once my board arrives. Could be a bit cheaper alternative =D
Re: Choice of USB-development board
The devboard worked flawlessly with your firmware! But as you said the usb port probably can't be used to program it any more. But atleast it's an alternative to the Teensy.
Haven't managed to get perfect mouse movement yet but I guess I just need to continue tweaking. Or perhaps I need a higher DPI than 5000.
On a sidenote, after 2 days of working without any issues all of a sudden I get an error and the controller shuts off:
send: Bad file descriptor
error writing ds4 control
Now it happens every time I try to use gimx.
Am I missing something, or have I done something wrong?
Thanks for your help, Matlo!
Haven't managed to get perfect mouse movement yet but I guess I just need to continue tweaking. Or perhaps I need a higher DPI than 5000.
On a sidenote, after 2 days of working without any issues all of a sudden I get an error and the controller shuts off:
send: Bad file descriptor
error writing ds4 control
Now it happens every time I try to use gimx.
Am I missing something, or have I done something wrong?
Thanks for your help, Matlo!
Re: Choice of USB-development board
Over bluetooth.
But I found what the error was, silly me forgot that battery-powered controllers might need charging once in a while... =)
Everything's working again once I just charged the controller.
But I found what the error was, silly me forgot that battery-powered controllers might need charging once in a while... =)
Everything's working again once I just charged the controller.