[Arm-netbook] eoma26-a10s

[joem]

i2s / spdif - not sure which is best. The device will run Linux and speak using espeak.
Even a USB speaker is OK, so long as it makes for reasonable audio.

If stuck with DDR, Dr. Ajith Kumar [bpajith at gmail.com] who did the expeyes may be able to help
you out with DDR as he did the expeyes derivative.

FPC also cheaper to fit as well as being compact.
40 pin connector about $0.30 and cable about $0.15.

Ethernet is a must.

If the kicad files get GPL'd we'd make our own variants as needed as CPUs change
and technology changes. Ideally we don't to go there if we can just buy the bits knowing that
if the supply chain went down, we can still build our own versions because we got the cad files
and sources for all the software.


________________________________________
From: arm-netbook [arm-netbook-bounces at lists.phcomp.co.uk] on behalf of luke.leighton [luke.leighton at gmail.com]
Sent: 25 August 2013 19:34
To: Linux on small ARM machines
Subject: Re: [Arm-netbook] eoma26-a10s

On Sun, Aug 25, 2013 at 6:11 PM, joem <joem at martindale-electric.co.uk> wrote:
> Don't wimp out - just get on with it ok! :)

 ha ha ok.  i'm presently seeing if i can actually do DDR3 layout.

> http://www.gplsquared.com/eoma26/fpc_40_45_50.tar.gz
> For KiCAD 2D footprints and 3D parts for 40, 45, 50 way FPC, but I must say, I really like those board connectors
> for their density.

 ... the B2B connectors from amphenol have them beat, hands-down.
30x10mm for only 30 pins vs 5x14.5 for 40 @ 0.5mm pitch...

 aw hell i think i worked out a way to get an FPC40 on there...

> We would put the mating half on flexible PCB
> and that means only a very small slot is needed to bring out the wires
> from any case that this board may sit in.
>
> If you could push to get a small separate self contained b2b connector for a webcam as well,
> that would be reaaally good! There are so many applications that require it.

 on the FPC.  which, if you use it exclusively for a webcam b2b stuffs
up a whole lot of other multiplexing options.

> The 8 pins spare can be anything that may have a functional block attached
> to it like ADC channels,

 i've got the LRADCs already.

> the motor controller or more UARTs and USBs.

 there aren't any left - it's pretty much the headphone / mic / FM and
TVOUT.  oh, and ethernet, but that's 18 pins (too many).

 btw you still didn't answer if I2S and SPDIF (digital) is ok for
audio in your customer's application.

> (If those functional blocks are not needed in an application, the pins can be used as general
> purpose IO which is in strong demand in embedded use - but obviously need some care about selection
> as not all CPUs have same numbers of USB or motor controller built in like the A10s.)

 the only reason i'm putting the FPC on is because it helps you with a
customer., that gets some sales in etc. etc.  for actual EOMA26
applications that connector won't be there: I/O boards will need to
use UART, I2C or USB and have embedded controllers or GPIO expanders.

 if you're planning to tell the customer that they can upgrade later
please *don't* do that - there's absolutely no guarantee that the
exact same FPC pins will be available.

l.

_______________________________________________
arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
Send large attachments to arm-netbook at files.phcomp.co.uk