arm-netbook

arm-netbook@lists.phcomp.co.uk

1079 discussions

eoma68-a20 v2.2 PCBs arrived
by Luke Kenneth Casson Leighton 16 Sep '14

16 Sep '14

ok i haven't tested them yet - wits tech kindly ran a preliminary check - they arrived over the weekend. they have at least been booted up from USB-OTG and an OS installed, so it is known that RAM, CPU, PMIC, NAND, HDMI and USB-OTG all operate correctly. i will be able to fully test the rest of the functionality once the micro-desktop PCBs are assembled, which should be another month or so. l.

2 1

Operating Systems, CPU Cards, EOMA68
by Luke Kenneth Casson Leighton 10 Sep '14

10 Sep '14

this is triggered mainly by the discussion last month from manuel, i had a bit of time to think and i came up with an idea. if you recall, manuel asked "would it be ok to buy a specific model of CPU card, install an OS that only works with the Games Console?" and the answer was "yes... but you could not call it EOMA68 compliant" so anyway i thought about this a bit and i figured that it makes a lot of sense to have the OS (which really has nothing to do with the CPU Card per se) basically adjust so that it works with whatever it detects... ... in other words, from an end-user perspective, you would buy a Gaming *Card*, or an Work *Card*, or an Android *Card*, or a Photo/Camera *Card* that would have an OS preinstalled which adapts to the base units it's plugged into. i'd be interested to hear people's thoughts on this. l.

2 2

Block Diagram EOMA-68 Handheld Games Console
by Miguel Garcia 10 Sep '14

10 Sep '14

I appreciate you analyze the block diagram. If you know any better component or an error or a missing connection, please tell me. Thanks. ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- Block Diagram EOMA-68 Handheld Games Console v.1.0 ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- A basic sketch of the block diagram: http://oi57.tinypic.com/16aeffb.jpg ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- ----------------- Slot PCMCIA: ----------------- Part Number: Amphenol G659EU1X2472X Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/G659EU1X2472X.PDF Table of EOMA-68 pinouts: http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Table_of_EOMA-… ------------ Display: ------------ Part Number: BTL507212-W677L Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/5.0''%20LCD%20HD%20-%20GL5005%20Spec_D.pdf Connections: - The MIPI pins are connected to MIPI pins of the MIPI-a-RGB IC. - The pins of the PWM are connected to PWR pins of the EOMA-68. - The display is connected to GPIO of the STM32F for power-up of LCD. --------------- MIPI-to-RGB IC: --------------- Part Number: SSD2828 Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/SSD2828QN4_1.0.pdf Connections: - The MIPI pins are connected to MIPI pins of the display. - The RGB pins are connected to RGB pins of the EOMA-68. - The SPI pins are connected to SPI pins of the EOMA-68. ---------------- Touch Panel: ---------------- Part Number: no hay Part Number definitivo. Datasheet: no definitive part number. A datasheet of a similar part number: https://dl.dropboxusercontent.com/u/19251472/D50-L4030A-K0D.pdf Connections: - The I2C pins of the Touch Panel are connected to I2C pins of the EOMA-68. ----------- Battery: ----------- Part Number: LP8067100-CI Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/LP8067100-CI.pdf Connections: - The pins of the battery are connected to battery connector. ------------------ Battery Connector: ------------------ Part Number: PH-LT-WT-NA Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/PH-LT-WT-NA%E6%89%BF%E8%AE%A4%E4%B9%… Connections: - The pins of the battery connector are connected to battery pins of the PMIC. ------------------ MicroUSB for Charging: ------------------ This microUSB is only responsible for charging the battery (no USB Host). Part Number (provisional): 47590-0001 Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/micro_usb_ab_475900001_sd.pdf Connections: - The power pins of the microUSB are connected to load pins of the PMIC. ------------------ LED of Charging: ------------------ This LED is used to illuminate when the battery is charging. We have not yet selected a part number (a generic LED). Connections: - The pins of the LED of Charging are connected to LED pins of the PMIC. -------------- PMIC: -------------- Part Number: AXP209 Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/AXP209-SpecSheet-Translated.pdf y http://hands.com/~lkcl/eoma/kde_tablet/AXP209%20Datasheet%20v1.0_cn.pdf Connections: - The PMIC are connected to PWR1, PWR2, PWR3 and PWR4 pins of the EOMA-68. - The PMIC are connected to I2C_SCL and I2C_SDA pins of the EOMA-68. - The PMIC are connected to a GPIO of the STM32F microcontroller (IRQ-OUT of AXP209). - The pins of the battery connector are connected to battery pins of the PMIC. - The power pins of the microUSB are connected to load pins of the PMIC. - The pins of the LED of Charging are connected to LED pins of the PMIC. ------------ EEPROM: ------------ Part Number: AT24C64 Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/AT24C64.eeprom.pdf Connections: - The EEPROM pins are connected to I2C pins of the EOMA-68. ------------------ Accelerometer: ------------------ Part Number: MXC6225XU Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/MXC6225XU.pdf Connections: - The Accelerometer pins are connected to I2C pins of the EOMA-68. - The Accelerometer is connected to a GPIO of the STM32F microcontroller (accelerometer IRQ). ------------ MicroSD: ------------ Part Number: MM027S020R Datasheet: http://hands.com/~lkcl/eoma/allwinner/litkconn_MICRO%20SD%20PUSH-PUSH%20A.p… Connections: - The MicroSD pins are connected to GPIO pins of the EOMA-68. - The MicroSD is connected to a GPIO of the STM32F microcontroller (for MicroSD "detect"). --------------- Power Button: --------------- The Power Button is a generic button with click Connections: - The Power Button is connected to 43 POWER# of EOMA-68. ----------------- Audio Jack: ----------------- Part Number: PJ-3545-5L1G Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/PJ-3543-L6G%20Model%20(1).pdf Connections: - The pins of the Audio Jack are connected to USB Audio Controller. ---------------- Speaker (x2): ---------------- We have not yet selected a part number (a generic Speaker (x2)). Connections: - The speaker pins are connected to Audio Amplifier pins (x2). ---------------------- Audio Amplifier: ---------------------- Part Number: UTC2822D Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/YW-UTC2822D_C.pdf y http://pdf.datasheetcatalog.com/datasheets/90/492970_DS.pdf Connections: - The Audio Amplifier is connected to the audio output that goes from the USB Audio Controller to Audio jack. - The speaker pins are connected to Audio Amplifier pins (x2). -------------- Microphone: -------------- We have not yet selected a part number (a generic Microphone). Connections: - The Microphone pins are connected to USB Audio Controller. -------------------------- USB Audio Controller: -------------------------- Part Number: CM108AH Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/CM108_DataSheet_v1.6.pdf Connections: - The USB Audio Controller is connected to USB HUB. - The USB Audio Controller is connected to a GPIO of the STM32F microcontroller (to alter volume on headphone-out). - The Microphone pins are connected to USB Audio Controller. - The pins of the Audio Jack are connected to USB Audio Controller. ------------- WIFI USB: ------------- Part Number: CCandC WM-294 1T1R Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/WM-294_module-V2.2%28PCB%20… Connections: - The Wifi USB pins are connected to USB HUB. ---------------- Bluetooth USB: ---------------- The Bluetooth USB part number has not yet been chosen, even so, is a generic BT, so the onnection/power would be similar to the WIFI. Connections: - The BT USB pins are connected to USB HUB. ---------------- USB Host 2.0: ---------------- The USB Host 2.0 part number has not yet been chosen, even so, is a generic USB Host 2.0, so the connection/power would be similar to the WIFI. Connections: - The USB Host 2.0 pins are connected to USB HUB. ---------------- USB HUB: ---------------- Part Number: FE1.1s Datasheet: http://hands.com/~lkcl/eoma/kde_tablet/FE1.1s%20Data%20Sheet%20(Rev.%201.0)… Connections: - The USB HUB is connected to 1st USB pins of the EOMA-68. - The USB Host 2.0 pins are connected to USB HUB. - The BT USB pins are connected to USB HUB. - The Wifi USB pins are connected to USB HUB. - The USB Audio Controller is connected to USB HUB. ------------------------ Digital Buttons (x17): ------------------------ 4 buttons (2 digital triggers and Vol + and Vol-) would be generic buttons with click (although maybe we put rubbers to makes softer press them, should be viewed) and the other buttons are the typical buttons ABXY on the PCB with rubbers (similar to xbox 360 controller or snes controller). Connections: - The Digital Button is connected to a GPIO of the STM32F microcontroller (x17). --------------------------- Digital Trigger (x2): --------------------------- The analog trigger is a piece of plastic connected to a potentiometer, which when pressed moves the potentiometer, and to return to its original position there is a spring (see analog trigger of GameCube or Wii Classic Controller as an example). Part Number (potentiometer): Panasonic EVA-W7NR04B34 Datasheet: http://www.digikey.com/product-detail/en/EVA-W7NR04B34/P13569-ND/1135944 Connections: - The potentiometer pins are connected to an ADC of the STM32F microcontroller (x2). ----------------- Joystick (x2): ----------------- Part Number: CTS 254TA103B50B-ND Datasheet: http://www.digikey.com/product-detail/en/254TA103B50B/254TA103B50B-ND/17559… Connections: - The analog pins of the Joystick are connected to 2 ADCs of the STM32F microcontroller (x2). - The digital pin of the Joystick is connected to a GPIO of the STM32F microcontroller (x2). -------------------- Microcontroller: -------------------- Part Number: STM32F072xx (we have not yet chosen a specific part number). Datasheet: http://www.st.com/st-web-ui/static/active/en/resource/technical/document/pr… http://www.st.com/web/en/resource/technical/document/datasheet/DM00090510.p… y http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/PF259717 Connections: - The STM32F is connected to 2nd USB pins of the EOMA-68. - The analog pins of the Joystick are connected to 2 ADCs of the STM32F microcontroller (x2). - The digital pin of the Joystick is connected to a GPIO of the STM32F microcontroller (x2). - The potentiometer pins are connected to an ADC of the STM32F microcontroller (x2). - The Digital Button is connected to a GPIO of the STM32F microcontroller (x17). - The USB Audio Controller is connected to a GPIO of the STM32F microcontroller (to alter volume on headphone-out). - The MicroSD is connected to a GPIO of the STM32F microcontroller (for MicroSD "detect"). - The Accelerometer is connected to a GPIO of the STM32F microcontroller (accelerometer IRQ). - The PMIC are connected to a GPIO of the STM32F microcontroller (IRQ-OUT of AXP209). - The display is connected to GPIO of the STM32F for power-up of LCD.

5 23

Fwd: Allwinner A33 Quad Core 2GB board in development
by Luke Kenneth Casson Leighton 05 Sep '14

05 Sep '14

this has gone out to debian-arm and fedora arm lists, if anyone else would like an A33 CPU Card let me know. l. ---------- Forwarded message ---------- From: Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> Date: Fri, Sep 5, 2014 at 10:33 AM Subject: Fwd: Allwinner A33 Quad Core 2GB board in development To: Fedora ARM <arm(a)lists.fedoraproject.org> i'm doing an EOMA68-A33 CPU Card which will cost $5600 to complete the layout and 5 samples. i can cover that cost over a couple of months, so it is going ahead, and first (working) 5 samples should be done and received by Dec 2014. if there is anyone who would like to buy either one of the 5 samples (at a premium) or would like to be part of a group-buy please do contact me directly. specifications are: * Allwinner A33 Quad Core ARM Cortex A7 * 2GByte RAM on a 32-bit interface * 18-pin RGB/TTL up to 1280x800 resolution * on-board SMC9514 USB-Ethernet IC (10/100) * 2x USB2 (480mb/s) on EOMA68 interface * 1x USB-OTG (can be used to power CPU Card) * 1x Micro-SD note that unlike the A20 CPU Card this one does *not* have HDMI out (it's a lower-cost SoC) and the max resolution really is limited to 1280x800 because the A33 is a tablet SoC... albeit a quad-core one. news as it happens will be at http://rhombus-tech.net/allwinner/a33/news/ l.

1 0

eoma68 a20 rev 2.2 cpu cards
by Luke Kenneth Casson Leighton 05 Sep '14

05 Sep '14

... have passed testing and are being shipped out to me today. still todo: the micro-desktop board prototypes. l.

1 0

mendel90 3d printer arrived
by Luke Kenneth Casson Leighton 03 Sep '14

03 Sep '14

also the mendel 90 kit arrived last week, i am about 20% through a build, it is... challenging shall we say: around 200 nuts/bolts/screws which i really wasn't expecting! i'll likely be done by end of this week and can start experimenting. l.

2 4

thoughts about a set top box
by Simon Kenyon 02 Sep '14

02 Sep '14

i've been thinking about this over the last year to two. decided to put it out there to see if anyone a) had any comments b) knows of existing hardware or c) interested in collaborating the idea is for a device which can act as a set top box, either as a pure player of content stored or streamed from elsewhere or as a receiver of content using one or more DVB-S2/T2 tuners. design criteria: - linux - open source including all drivers and codecs - fast enough to render 1080p - hdmi out - bluetooth/wifi on board - all connectors on one edge of board so casework can be professional quality - tuners on board or pluggable. i had an idea to re-use the dimensions of a standard motherboard and instead of spci slots - have usb plugs instead. a tuner could then plug in like a pci card. - space on the pc for a 2.5" disk (see http://www.sinovoip.com.cn/ecp_view.asp?id=554) -- simon Simon Kenyon Managing Director. The Koala Computer Company Limited e: simon(a)koala.ie m: +353 86 240 0005 l: http://ie.linkedin.com/pub/simon-kenyon/0/6b2/744/ s: simonckenyon t: @simonckenyon g: google.com/+SimonKenyon

1 0

eoma68 trademark
by Luke Kenneth Casson Leighton 01 Sep '14

01 Sep '14

i think i have a solution now to the eoma68 trademark issues, i will let people know in a couple of months how it goes. l.

1 0

eoma68-a20 rev 2.2 pcbs done
by Luke Kenneth Casson Leighton 01 Sep '14

01 Sep '14

the rev 2.2 boards are now at wits tech, there are three with 1gb of RAM, the 2 with 2gb RAM need to be redone, will keep people informed. l.

1 0

discussion of operating systems on cpu cards
by Luke Kenneth Casson Leighton 28 Aug '14

28 Aug '14

after manuel asked if it was ok to have a specific CPU Card only support one OS, i had a bit of a think about that, and wanted to run an idea by everyone. the discussion is basically "should all CPU Cards work with all base units with all OSes?" meaning that we have a *three-way* (3D) matrix of options: a) CPU Cards b) base units c) OSes previously we had discussed the idea of OSes being able to auto-download (in some fashion) such that CPU Cards could adapt to the base unit. i have an alternative idea which i think may turn out to be more workable... at least slightly simpler. the idea is quite simple: * tie the OS to the CPU Card * have the OS adapt (as best as possible) to the base unit *without* needing OS updates (as best as practical) the implications are that, for example (manuel?) the Gaming OS should adapt so that if the CPU Card is plugged into a laptop base, it should go "oh, i am in a laptop base, i have no touch screen but that's ok i have a mouse, and oh look i have a joystick rather than a set of analog track-pads". given that most games have some form of in-game configuration options for keys/mouse/joystick etc. would this be workable at all? l.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

arm-netbook