On Tue, Sep 22, 2015 at 4:31 PM, GaCuest gacuest@gmail.com wrote:
En 22 de septiembre de 2015 en 15:15:51, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Tue, Sep 22, 2015 at 1:12 PM, GaCuest wrote:
The only solution I can think is to put the BMA250 in the second PCB and connect directly to STM32F and configure it as a USB device. I do not know if this is easy to do for us (software development) and solve the problem of EINTs.
making a GPIO an EINT on the STM32F, then reading I2C, then sending a few bytes of data as a USB event, it's about... 30-40 lines of code. if it's any more than that, you're doing something *drastically* wrong.
So I suppose that the better option is to put the BMA250 on the second PCB and connect it to STM32F, right?
that's what i would do, because, if i was considering making a separate controller (as a 2nd joypad) i would want to be able to "tilt" the controller... rather than just the games console.
On the other hand, we don’t need a EINT of the EOMA-68 to the STM32F, right?
correct, you don't. USB events will take care of generating an interrupt, automatically.
l.