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? On the other hand, we don’t need a EINT of the EOMA-68 to the STM32F, right?
Thanks.
Also I found the following FFC cable: http://aliexpress.com/store/product/Free-Shipping-FPC-FFC-connector-cable-so...
Do you recommend use that connector or other (cheaper) connector?
honestly it's up to you. personally i just went for standard 0.254mm connectors, because that *really* makes it easy for developers. however, they're quite big, you need to get R/A ones, and i believe those could well be more expensive than a 6pin FFC.
so it is your decision, you know what the goal is, available space, target price and target market.
Well, I think that one of the most important goal is the price.
l.
Thanks.
l.
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk