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-6...
------------ Display: ------------
Part Number: BTL507212-W677L Datasheet: https://dl.dropboxusercontent.com/u/19251472/11/5.0%27%27%20LCD%20HD%20-%20G... 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%A... 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.pd... 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%20v... 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/175591... 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/pro... http://www.st.com/web/en/resource/technical/document/datasheet/DM00090510.pd... 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.
On Fri, Sep 5, 2014 at 11:56 AM, Miguel Garcia gacuest@gmail.com wrote:
I appreciate you analyze the block diagram.
the diagram is out-of-date it references ADC ICs and doesn't have an STM32F072 on it
also could you send the link to the "raw" image in future rather than the one which has advertising on it, it is deceptive in that there is a "close" button in the top right which, instead of *being* a close, takes you to a link.
as i am in a secure environment this has caused an unauthorised security breach, so please only send the link to the "raw" image.
l.
On Fri, Sep 5, 2014 at 12:18 PM, Miguel Garcia gacuest@gmail.com wrote:
The new link: http://i.imgur.com/sN2xAgA.png
taaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff. you might want to consider a more expensive part from MXC which does range *from* 0x00 to 0xff, and maybe on 3 axes.
especially for a games console.
l.
On Fri, 5 Sep 2014 12:52:33 +0100 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
aaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff.
In fact it *gives* you an output for X and Y (Which is from -128 to 127). Have a look at page 9. It just gives you an additional register with some bits which will show you the basic orientation and if the devices has been shaken.
On Mon, Sep 8, 2014 at 11:33 AM, Richard Zink zink@hexatux.org wrote:
On Fri, 5 Sep 2014 12:52:33 +0100 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
aaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff.
In fact it *gives* you an output for X and Y (Which is from -128 to 127).
i have the prototype first tablet, i tested the MXC6225 which was installed on it: the only values given were 0x00 and 0xff. the MXC6225 is basically for ultra-low-cost devices where all you need to know is:
"is this device upright or is it on its side, yes or no".
a games console may wish to use an accelerometer (or tilt system) where the motion of the device - a small tip to the left - is used in essence as a mouse or analog joystick.
i think there's a gnu/linux game where you have a ball-bearing that you steer through obstacles by moving the mouse to "tilt" a surface.
the MXC6225 would be completely and utterly inadequate for such a game.
l.
On Mon, Sep 8, 2014 at 11:23 AM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 8, 2014 at 11:33 AM, Richard Zink zink@hexatux.org wrote:
On Fri, 5 Sep 2014 12:52:33 +0100 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
aaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff.
In fact it *gives* you an output for X and Y (Which is from -128 to 127).
http://www.memsic.com/accelerometers/MXC6226XU
this is one that gives values from -128 to 127 - the MXC6226 not the MXC6225.
l.
On Mon, 8 Sep 2014 11:38:58 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 8, 2014 at 11:23 AM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 8, 2014 at 11:33 AM, Richard Zink zink@hexatux.org wrote:
On Fri, 5 Sep 2014 12:52:33 +0100 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
aaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff.
In fact it *gives* you an output for X and Y (Which is from -128 to 127).
http://www.memsic.com/accelerometers/MXC6226XU
this is one that gives values from -128 to 127 - the MXC6226 not the MXC6225.
Yes, the MXC6225 should give you the correct values for acceleration, which is 64 LSB/g and a measuring range of +/- 2g. I don't have a device using this chip, so I need to rely on the datasheet ( http://hands.com/~lkcl/eoma/kde_tablet/MXC6225XU.pdf / http://www.memsic.com/userfiles/files/Datasheets/Accelerometer-Datasheets/MX... ) If I'm wrong with the datasheet, please point me to the correct one.
- Richard
On Mon, Sep 8, 2014 at 2:27 PM, Richard Zink zink@hexatux.org wrote:
On Mon, 8 Sep 2014 11:38:58 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 8, 2014 at 11:23 AM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 8, 2014 at 11:33 AM, Richard Zink zink@hexatux.org wrote:
On Fri, 5 Sep 2014 12:52:33 +0100 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
aaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff.
In fact it *gives* you an output for X and Y (Which is from -128 to 127).
http://www.memsic.com/accelerometers/MXC6226XU
this is one that gives values from -128 to 127 - the MXC6226 not the MXC6225.
Yes, the MXC6225 should give you the correct values for acceleration,
a-a-ahh nooo, it *doesn't*. it does *not* give *any* values for acceleration, the MXC6225 is a *tilt* sensor.
which is 64 LSB/g and a measuring range of +/- 2g. I don't have a device using this chip,
i do. i read the data using python-i2c. it gave either 0x00 or 0xff. that was all. i did not see any changes in the values read from the device when either shaking it or rotating it slightly.
so I need to rely on the datasheet http://www.memsic.com/userfiles/files/Datasheets/Accelerometer-Datasheets/MX... )
If I'm wrong with the datasheet, please point me to the correct one.
ok that's a general-purpose datasheet covering the *family* of MXC622x products (landing patterns, I2C communication protocols etc.).
so it covers *both* the MXC6225 *and* the MXC6226 which have *different* capabilities. from what i can see, the 6225 has less capabilities than the MXC6226.
does anyone know where the specific datasheets are so that this can be made absolutely clear? the right IC needs to be found.
l.
On Mon, 8 Sep 2014 13:30:47 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
ok that's a general-purpose datasheet covering the *family* of MXC622x products (landing patterns, I2C communication protocols etc.).
so it covers *both* the MXC6225 *and* the MXC6226 which have *different* capabilities. from what i can see, the 6225 has less capabilities than the MXC6226.
does anyone know where the specific datasheets are so that this can be made absolutely clear? the right IC needs to be found.
Oh, now I understand. Sorry for worrying you with that nonesense. You can simply forget anything I said about that ;)
On Mon, Sep 8, 2014 at 4:09 PM, Richard Zink zink@hexatux.org wrote:
On Mon, 8 Sep 2014 13:30:47 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
ok that's a general-purpose datasheet covering the *family* of MXC622x products (landing patterns, I2C communication protocols etc.).
so it covers *both* the MXC6225 *and* the MXC6226 which have *different* capabilities. from what i can see, the 6225 has less capabilities than the MXC6226.
does anyone know where the specific datasheets are so that this can be made absolutely clear? the right IC needs to be found.
Oh, now I understand. Sorry for worrying you with that nonesense.
nono, i was asking you if you could double-check :)
On Mon, 8 Sep 2014 14:11:51 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
ok that's a general-purpose datasheet covering the *family* of MXC622x products (landing patterns, I2C communication protocols etc.).
so it covers *both* the MXC6225 *and* the MXC6226 which have *different* capabilities. from what i can see, the 6225 has less capabilities than the MXC6226.
does anyone know where the specific datasheets are so that this can be made absolutely clear? the right IC needs to be found.
Oh, now I understand. Sorry for worrying you with that nonesense.
nono, i was asking you if you could double-check :)
Will try to get the proper datasheet in the evening and do a check then.
On Mon, Sep 8, 2014 at 4:41 PM, Richard Zink zink@hexatux.org wrote:
On Mon, 8 Sep 2014 14:11:51 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
ok that's a general-purpose datasheet covering the *family* of MXC622x products (landing patterns, I2C communication protocols etc.).
so it covers *both* the MXC6225 *and* the MXC6226 which have *different* capabilities. from what i can see, the 6225 has less capabilities than the MXC6226.
does anyone know where the specific datasheets are so that this can be made absolutely clear? the right IC needs to be found.
Oh, now I understand. Sorry for worrying you with that nonesense.
nono, i was asking you if you could double-check :)
Will try to get the proper datasheet in the evening and do a check then.
star.
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
On Mon, 8 Sep 2014 15:29:59 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
Will try to get the proper datasheet in the evening and do a check then.
star.
Datasheets: http://www.memsic.com/userfiles/files/Datasheets/Accelerometer-Datasheets/MX... http://media.digikey.com/pdf/Data%20Sheets/MEMSIC%20PDFs/MXC6225XU.pdf
I've checked both datasheets, but can't find any difference between the two ICs. The technical specifications are the same (the 6226 is a bit more detailed), but both tell the same information. Your output of python-i2c is "safe"? Checked it with a different IC? Maybe we should ask the manufacturer if the values are right or if the IC gives a floating output between -128 to 127.
On Tue, Sep 9, 2014 at 11:10 AM, Richard Zink zink@hexatux.org wrote:
On Mon, 8 Sep 2014 15:29:59 +0200 Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
Will try to get the proper datasheet in the evening and do a check then.
star.
Datasheets: http://www.memsic.com/userfiles/files/Datasheets/Accelerometer-Datasheets/MX... http://media.digikey.com/pdf/Data%20Sheets/MEMSIC%20PDFs/MXC6225XU.pdf
I've checked both datasheets, but can't find any difference between the two ICs. The technical specifications are the same (the 6226 is a bit more detailed), but both tell the same information.
bizarre.
Your output of python-i2c is "safe"?
yeah.
Checked it with a different IC?
no i only had the one.
Maybe we should ask the manufacturer if the values are right or if the IC gives a floating output between -128 to 127.
... or find an IC from a company with a better datasheet!
l.
mån 2014-09-08 klockan 13:30 +0200 skrev Luke Kenneth Casson Leighton:
a-a-ahh nooo, it *doesn't*. it does *not* give *any* values for acceleration, the MXC6225 is a *tilt* sensor.'
From what I understand the whole series is primarily a tilt sensor, with
the only difference between the chip numbers being the I²C address they respond to.
datasheets says those two registers is the instaneous orientation reading, but none of the suggested applications uses more than the status tilt-orientation & shake bits.
I doubt this series of accelerometers are intended for any detailed readings of orientation as needed for making a air mouse / game controller type application.
Regards Henrik
On Tue, Sep 9, 2014 at 8:06 PM, Henrik Nordström henrik@henriknordstrom.net wrote:
mån 2014-09-08 klockan 13:30 +0200 skrev Luke Kenneth Casson Leighton:
a-a-ahh nooo, it *doesn't*. it does *not* give *any* values for acceleration, the MXC6225 is a *tilt* sensor.'
From what I understand the whole series is primarily a tilt sensor, with the only difference between the chip numbers being the I²C address they respond to.
datasheets says those two registers is the instaneous orientation reading, but none of the suggested applications uses more than the status tilt-orientation & shake bits.
I doubt this series of accelerometers are intended for any detailed readings of orientation as needed for making a air mouse / game controller type application.
can you recall which manufacturers do something more appropriate?
2014-09-05 13:52 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
taaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff. you might want to consider a more expensive part from MXC which does range *from* 0x00 to 0xff, and maybe on 3 axes.
especially for a games console.
Is Bosch BMA250 a better alternative?
Datasheet: http://ae-bst.resource.bosch.com/media/products/dokumente/bma250/BST-BMA250-...
Thanks.
On Wed, Sep 10, 2014 at 1:32 PM, Miguel Garcia gacuest@gmail.com wrote:
2014-09-05 13:52 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
taaa. btw the MXC6225XU is basically "are we vertical, are we horizontal" it doesn't provide any kind of "tilt" or angle, and it is 2-axis not 3-axis. the data output is either 0x00 or 0xff. you might want to consider a more expensive part from MXC which does range *from* 0x00 to 0xff, and maybe on 3 axes.
especially for a games console.
Is Bosch BMA250 a better alternative?
yes very much so.
Datasheet: http://ae-bst.resource.bosch.com/media/products/dokumente/bma250/BST-BMA250-...
which says it's designed for games consoles, so yes.
l.
you can dump things here: ftp://sharedwriteaccess:0Sharedwriteaccess@ftp.george.the-petries.co.uk/eoma/tmp
for tmp files put in this tmp dir for longer term files put them in the dir above. if a file is more that 1gb please treat it as short term upload. the webhost doesn't like all these gb's I'm using up.
read access via http: http://aross.me/shared-write-access/eoma
2014-09-05 13:19 GMT+02:00 Alexander Stephen Thomas Ross maillist_arm-netbook@aross.me:
you can dump things here: ftp://sharedwriteaccess:0Sharedwriteaccess@ftp.george.the-petries.co.uk/eoma/tmp
for tmp files put in this tmp dir for longer term files put them in the dir above. if a file is more that 1gb please treat it as short term upload. the webhost doesn't like all these gb's I'm using up.
read access via http: http://aross.me/shared-write-access/eoma
Thanks!
The link: http://george.the-petries.co.uk/shared-write-access/eoma/Block%20Diagram%20C...
there are two EINT lines on EOMA68. i suggest that one of them be connected to the AXP209, and the other to the STM32F072, although because there are only 2 this leaves some slight issue with the touchpanel to resolve (in linux kernel source, which will need modification).
the problem is this: things like the touchpanel it is fairly essential (because you want to wake up the entire device based on an EINT) to have external interrupt.
one alternative to modifying the linux kernel source is to have a NAND (NOR?) IC multiplexing multiple IRQ lines from various peripheral ICs onto the one EINT line.
another alternative is to wire the AXP209 to the STM32F (on one of its GPIOs, then put that into EINT mode), then have the STM32F software generate a simple GPIO pull-up out to one of the EOMA68 EINTs.
so instead of doing the multiplexing using a NAND (NOR) gate IC, you do it in software (firmware) instead.
then you can do whatever you want, without modifying any linux kernel source.
so, you need to identify which devices have IRQ outputs. i count these:
* Accelerometer * Touch panel * AXP209 * STM32F072xx * MicroSD * Headphone detect
all of these _should_ be connected to (generate) EINTs... but there are only 2 EINTs available...
* analog joysticks are exactly that, they always generate data so there is no concept of "IRQ" * power button is connected to the AXP209 so the AXP209 does the "IRQ" * Buttons are converted to USB HID (keyboard) events via the STM32F072 in software...
anything else?
l.
2014-09-05 13:48 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
there are two EINT lines on EOMA68. i suggest that one of them be connected to the AXP209, and the other to the STM32F072, although because there are only 2 this leaves some slight issue with the touchpanel to resolve (in linux kernel source, which will need modification).
the problem is this: things like the touchpanel it is fairly essential (because you want to wake up the entire device based on an EINT) to have external interrupt.
one alternative to modifying the linux kernel source is to have a NAND (NOR?) IC multiplexing multiple IRQ lines from various peripheral ICs onto the one EINT line.
another alternative is to wire the AXP209 to the STM32F (on one of its GPIOs, then put that into EINT mode), then have the STM32F software generate a simple GPIO pull-up out to one of the EOMA68 EINTs.
so instead of doing the multiplexing using a NAND (NOR) gate IC, you do it in software (firmware) instead.
then you can do whatever you want, without modifying any linux kernel source.
Thanks.
And, what is your recommendation?
- Headphone detect
What is the INT/IRQ pin here?
Thanks.
On Sat, Sep 6, 2014 at 10:37 AM, Miguel Garcia gacuest@gmail.com wrote:
2014-09-05 13:48 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
there are two EINT lines on EOMA68. i suggest that one of them be connected to the AXP209, and the other to the STM32F072, although because there are only 2 this leaves some slight issue with the touchpanel to resolve (in linux kernel source, which will need modification).
the problem is this: things like the touchpanel it is fairly essential (because you want to wake up the entire device based on an EINT) to have external interrupt.
one alternative to modifying the linux kernel source is to have a NAND (NOR?) IC multiplexing multiple IRQ lines from various peripheral ICs onto the one EINT line.
another alternative is to wire the AXP209 to the STM32F (on one of its GPIOs, then put that into EINT mode), then have the STM32F software generate a simple GPIO pull-up out to one of the EOMA68 EINTs.
so instead of doing the multiplexing using a NAND (NOR) gate IC, you do it in software (firmware) instead.
then you can do whatever you want, without modifying any linux kernel source.
Thanks.
And, what is your recommendation?
i'd suggest multiplexing them all via the STM32F07xx onto one pin. this will mean that all drivers which use that pin will all receive interrupts whenever any of the other devices generate one but that is much more preferable to polling
- Headphone detect
What is the INT/IRQ pin here?
i don't understand the question. the headphone detect pin is the INT/IRQ pin.
l.
Thanks.
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@lists.phcomp.co.uk
-
Alexander Stephen Thomas Ross -
Henrik Nordström -
Luke Kenneth Casson Leighton -
Miguel Garcia -
Richard Zink