Hello everyone.
Now I am going to talk about handheld games console based on EOMA-68.
As I mentioned in other posts, we have finally changed some things. For example, we have made the interchangeable screen. It will be available 3 models (without display, cheaper; with 480p display; and with 720p display, more expensive). Furthermore, more advanced users can change the display.
Moreover, we will design the console in 3 PCB. On one hand, the central PCB (first PCB) where all components except the controls are, and the second and third PCB where the controls are.
This allows us to design the 1st PCB first, and then design the case around the 1st PCB and decide where to place the controls. After, we design the second and third PCB.
You can see this concept here: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Now I put the block diagram of all PCB.
Block diagram of the first PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Datasheet of components of first PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Block diagram of the second PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Datasheet of components of second PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Block diagram of the third PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Datasheet of components of third PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Block diagram of the 480p display PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Datasheet of components of 480p display PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Block diagram of the 720p display PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Datasheet of components of 720p display PCB: http://george.the-petries.co.uk/shared-write-access/eoma/HandheldGamesConsol...
Any help/change/suggestion is welcome.
On Sun, Sep 20, 2015 at 11:53 PM, GaCuest gacuest@gmail.com wrote:
Hello everyone.
Now I am going to talk about handheld games console based on EOMA-68.
awesome, miguel - i'll chip in tomorrow, it's late here: if anyone would like to put these below on the wiki page http://rhombus-tech.net/community_ideas/games_console/news/ that would be great, i will do it tomorrow if someone else hasn't.
l.
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
En 21 de septiembre de 2015 en 2:16:39, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Sun, Sep 20, 2015 at 11:53 PM, GaCuest wrote:
Hello everyone.
Now I am going to talk about handheld games console based on EOMA-68.
awesome, miguel - i'll chip in tomorrow, it's late here: if anyone would like to put these below on the wiki page http://rhombus-tech.net/community_ideas/games_console/news/ that would be great, i will do it tomorrow if someone else hasn't.
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
On Mon, Sep 21, 2015 at 4:56 PM, GaCuest gacuest@gmail.com wrote:
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
yeah that looks fantastic.
hmmmm, i have an idea for you. how about moving the EC onto the buttons PCB? that way you only need an absolute minimum of connections to it. USB, power, GND... maybe BOOT and RESET errr... that's all you'd really need.
that would be 6 wires, and i'm sure you could find some suitable spring-loaded connector for that. maybe even a SIM card holder (one without the "holder" bit - just the bare spring-loaded bits. as you'd be talking USB 1.0 or USB 1.1 that would hardly tickle any EMF.
l.
En 21 de septiembre de 2015 en 18:17:15, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Mon, Sep 21, 2015 at 4:56 PM, GaCuest wrote:
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
yeah that looks fantastic.
hmmmm, i have an idea for you. how about moving the EC onto the buttons PCB? that way you only need an absolute minimum of connections to it. USB, power, GND... maybe BOOT and RESET errr... that's all you'd really need.
that would be 6 wires, and i'm sure you could find some suitable spring-loaded connector for that. maybe even a SIM card holder (one without the "holder" bit - just the bare spring-loaded bits. as you'd be talking USB 1.0 or USB 1.1 that would hardly tickle any EMF.
If we put the STM32F in the second (or third) PCB, we need to connect the second with the third PCB (the same problem). Other problem is that we lost the USB ST-Link connection for FFC developers conector.
What do you think?
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
On Mon, Sep 21, 2015 at 6:03 PM, GaCuest gacuest@gmail.com wrote:
En 21 de septiembre de 2015 en 18:17:15, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Mon, Sep 21, 2015 at 4:56 PM, GaCuest wrote:
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
yeah that looks fantastic.
hmmmm, i have an idea for you. how about moving the EC onto the buttons PCB? that way you only need an absolute minimum of connections to it. USB, power, GND... maybe BOOT and RESET errr... that's all you'd really need.
that would be 6 wires, and i'm sure you could find some suitable spring-loaded connector for that. maybe even a SIM card holder (one without the "holder" bit - just the bare spring-loaded bits. as you'd be talking USB 1.0 or USB 1.1 that would hardly tickle any EMF.
If we put the STM32F in the second (or third) PCB, we need to connect the second with the third PCB (the same problem).
? why? rright right yes, got it. ok, so yes, put STM32F on 2nd (or 3rd) PCB, link 2nd to 3rd with FFC-20P, then you only have one FFC-20P, not two, the other is replaced with a simple 4 pin (or possibly 6 pin) cable / blah blah whatever.
Other problem is that we lost the USB ST-Link connection for FFC developers conector.
What do you think?
ideas occur to me...
(1) if someone wants to develop an alternative embedded controller PCB, if there's already one on the main PCB they are discouraged from adding another. it occupies the USB port... you can't really take that over unless you want to replace PCB1.
(2) if someone wants to develop an alternative joypad controller PCB... say... out of discrete ICs, they are again discouraged from doing so because there's an STM32F on the main PCB, esp. as it occupies an entire USB port.
(3) if the STM32F is on the joypad controller PCB, and it's pretty much "USB", you could actually consider making a *separate* joypad *product* out of it, sold for other markets.... *including* offering one for sale as a 2nd controller to be wired directly into the USB port of the games console.
(4) i don't see any problem with doing product development (of the joypad controller) by taking PCB2 and PCB3, testing them *entirely separately* as a stand-alone unit.
(5) i don't see any problem with doing product development (of the games console) by taking out PCB2 and PCB3, and connecting "alternative products" directly into the USB port provided for (normally) joypad control.
l.
En 21 de septiembre de 2015 en 21:50:23, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Mon, Sep 21, 2015 at 6:03 PM, GaCuest wrote:
En 21 de septiembre de 2015 en 18:17:15, Luke Kenneth Casson Leighton (lkcl@lkcl.net)
escrito:
On Mon, Sep 21, 2015 at 4:56 PM, GaCuest wrote:
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
yeah that looks fantastic.
hmmmm, i have an idea for you. how about moving the EC onto the buttons PCB? that way you only need an absolute minimum of connections to it. USB, power, GND... maybe BOOT and RESET errr... that's all you'd really need.
that would be 6 wires, and i'm sure you could find some suitable spring-loaded connector for that. maybe even a SIM card holder (one without the "holder" bit - just the bare spring-loaded bits. as you'd be talking USB 1.0 or USB 1.1 that would hardly tickle any EMF.
If we put the STM32F in the second (or third) PCB, we need to connect the second with the
third PCB (the same problem).
? why? rright right yes, got it. ok, so yes, put STM32F on 2nd (or 3rd) PCB, link 2nd to 3rd with FFC-20P, then you only have one FFC-20P, not two, the other is replaced with a simple 4 pin (or possibly 6 pin) cable / blah blah whatever.
Other problem is that we lost the USB ST-Link connection for FFC developers conector.
What do you think?
ideas occur to me...
(1) if someone wants to develop an alternative embedded controller PCB, if there's already one on the main PCB they are discouraged from adding another. it occupies the USB port... you can't really take that over unless you want to replace PCB1.
(2) if someone wants to develop an alternative joypad controller PCB... say... out of discrete ICs, they are again discouraged from doing so because there's an STM32F on the main PCB, esp. as it occupies an entire USB port.
(3) if the STM32F is on the joypad controller PCB, and it's pretty much "USB", you could actually consider making a *separate* joypad *product* out of it, sold for other markets.... *including* offering one for sale as a 2nd controller to be wired directly into the USB port of the games console.
(4) i don't see any problem with doing product development (of the joypad controller) by taking PCB2 and PCB3, testing them *entirely separately* as a stand-alone unit.
(5) i don't see any problem with doing product development (of the games console) by taking out PCB2 and PCB3, and connecting "alternative products" directly into the USB port provided for (normally) joypad control.
Yes, surely you are right and it is better that way.
But we have a problem with EINTs.
We have at least 5 IC they need EINT: * Touch panel * AXP209 * Headphone detect * Accelerometer * MicroSD
However EOMA-68 only has 4 EINTs.
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.
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
En 21 de septiembre de 2015 en 23:34:15, GaCuest (gacuest@gmail.com) escrito:
En 21 de septiembre de 2015 en 21:50:23, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Mon, Sep 21, 2015 at 6:03 PM, GaCuest wrote:
En 21 de septiembre de 2015 en 18:17:15, Luke Kenneth Casson Leighton (lkcl@lkcl.net)
escrito:
On Mon, Sep 21, 2015 at 4:56 PM, GaCuest wrote:
I have updated it: http://rhombus-tech.net/community_ideas/games_console/news/
I hope that I have done it well. Thanks!
yeah that looks fantastic.
hmmmm, i have an idea for you. how about moving the EC onto the buttons PCB? that way you only need an absolute minimum of connections to it. USB, power, GND... maybe BOOT and RESET errr... that's all you'd really need.
that would be 6 wires, and i'm sure you could find some suitable spring-loaded connector for that. maybe even a SIM card holder (one without the "holder" bit - just the bare spring-loaded bits. as you'd be talking USB 1.0 or USB 1.1 that would hardly tickle any EMF.
If we put the STM32F in the second (or third) PCB, we need to connect the second with the
third PCB (the same problem).
? why? rright right yes, got it. ok, so yes, put STM32F on 2nd (or 3rd) PCB, link 2nd to 3rd with FFC-20P, then you only have one FFC-20P, not two, the other is replaced with a simple 4 pin (or possibly 6 pin) cable / blah blah whatever.
Other problem is that we lost the USB ST-Link connection for FFC developers conector.
What do you think?
ideas occur to me...
(1) if someone wants to develop an alternative embedded controller PCB, if there's already one on the main PCB they are discouraged from adding another. it occupies the USB port... you can't really take that over unless you want to replace PCB1.
(2) if someone wants to develop an alternative joypad controller PCB... say... out of discrete ICs, they are again discouraged from doing so because there's an STM32F on the main PCB, esp. as it occupies an entire USB port.
(3) if the STM32F is on the joypad controller PCB, and it's pretty much "USB", you could actually consider making a *separate* joypad *product* out of it, sold for other markets.... *including* offering one for sale as a 2nd controller to be wired directly into the USB port of the games console.
(4) i don't see any problem with doing product development (of the joypad controller) by taking PCB2 and PCB3, testing them *entirely separately* as a stand-alone unit.
(5) i don't see any problem with doing product development (of the games console) by taking out PCB2 and PCB3, and connecting "alternative products" directly into the USB port provided for (normally) joypad control.
Yes, surely you are right and it is better that way.
But we have a problem with EINTs.
We have at least 5 IC they need EINT:
- Touch panel
- AXP209
- Headphone detect
- Accelerometer
- MicroSD
However EOMA-68 only has 4 EINTs.
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.
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?
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
On Tue, Sep 22, 2015 at 1:12 PM, GaCuest gacuest@gmail.com 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.
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.
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
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
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.
Hello everyone, I updated the block diagram. I would appreciate if someone can review it.
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Thanks!
On Tue, Sep 22, 2015 at 7:38 PM, GaCuest gacuest@gmail.com wrote:
Hello everyone, I updated the block diagram. I would appreciate if someone can review it.
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
ok so you liked the idea of being able to make a games controller from the same PCB, then? :) it would be really simple, a piece of plastic and a USB connector - done!
page 27: http://hands.com/~lkcl/eoma/kde_tablet/CM108_DataSheet_v1.6.pdf
i don't see a need for an EINT to the CM108AH.
ah, i see what it is: the EINT goes directly to the Audio Jack. it's the physical audio socket which has a "connection" which is broken/made by the physical insertion of a jack. that, in software, you would then notice.
actually what i've done in the hardware circuits i've made, is, although yes there is a connection there, i added in a resistor bridge into the circuit to bring the volume down when speakers are engaged. the CM108AH "normally" would drive the headphones (directly), but in "speaker" mode the L / R audio goes first to the headphones (where insertion of the jack would make it "cut out"), and from there (if no jack) it goes to the resistor-divider bridge to drop the voltage to 1/10th of its level, and *that* is fed into the TDA2822(s).
so actually, in the circuit that i have done, strictly speaking the EINT headphone is totally irrelevant... i just added it "just in case", also to be able to do user-alerts.
l.
En 22 de septiembre de 2015 en 22:57:20, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Tue, Sep 22, 2015 at 7:38 PM, GaCuest wrote:
Hello everyone, I updated the block diagram. I would appreciate if someone can review it.
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
ok so you liked the idea of being able to make a games controller from the same PCB, then? :) it would be really simple, a piece of plastic and a USB connector - done!
Yes, it's a good idea.
The problem is that we are not a professional team, so we can now focus only on the handheld games console. Daniel has very little free time, so for now we are progressing very slowly.
Another idea would be to create a EOMA-68 with FPGA (or similar) and use it as a pass-through card. For example, you can connect a PC Gamer to HDMI and USB of this EOMA-68, and you have a PC as a handheld games console.
page 27: http://hands.com/~lkcl/eoma/kde_tablet/CM108_DataSheet_v1.6.pdf
i don't see a need for an EINT to the CM108AH.
ah, i see what it is: the EINT goes directly to the Audio Jack. it's the physical audio socket which has a "connection" which is broken/made by the physical insertion of a jack. that, in software, you would then notice.
actually what i've done in the hardware circuits i've made, is, although yes there is a connection there, i added in a resistor bridge into the circuit to bring the volume down when speakers are engaged. the CM108AH "normally" would drive the headphones (directly), but in "speaker" mode the L / R audio goes first to the headphones (where insertion of the jack would make it "cut out"), and from there (if no jack) it goes to the resistor-divider bridge to drop the voltage to 1/10th of its level, and *that* is fed into the TDA2822(s).
so actually, in the circuit that i have done, strictly speaking the EINT headphone is totally irrelevant... i just added it "just in case", also to be able to do user-alerts.
So we have two options, put the EINT in the headphone jack, or put (this) second EINT in the FFC 40 pin connector in case we need it in the future on future screen. What is your recommendation?
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
On Tue, Sep 22, 2015 at 10:43 PM, GaCuest gacuest@gmail.com wrote:
En 22 de septiembre de 2015 en 22:57:20, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Tue, Sep 22, 2015 at 7:38 PM, GaCuest wrote:
Hello everyone, I updated the block diagram. I would appreciate if someone can review it.
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
ok so you liked the idea of being able to make a games controller from the same PCB, then? :) it would be really simple, a piece of plastic and a USB connector - done!
Yes, it's a good idea.
The problem is that we are not a professional team, so we can now focus only on the handheld games console. Daniel has very little free time, so for now we are progressing very slowly.
hey it was an easy idea... for another time, yes.
Another idea would be to create a EOMA-68 with FPGA (or similar) and use it as a pass-through card. For example, you can connect a PC Gamer to HDMI and USB of this EOMA-68, and you have a PC as a handheld games console.
ah yeah of course, i forgot about that :)
btw could you use plain-text editing, not a rich-text format, with paragraphs broken up at (appx) 70 chars per line, please?
So we have two options, put the EINT in the headphone jack, or put (this) second EINT in the FFC 40 pin connector in case we need it in the future on future screen. What is your recommendation?
i'd say keep it on the HP jack, just in case something needs to be altered (volume etc.) when switching between headphone and speaker mode.
l.
En 23 de septiembre de 2015 en 0:48:20, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Tue, Sep 22, 2015 at 10:43 PM, GaCuest wrote:
En 22 de septiembre de 2015 en 22:57:20, Luke Kenneth Casson Leighton (lkcl@lkcl.net)
escrito:
On Tue, Sep 22, 2015 at 7:38 PM, GaCuest wrote:
Hello everyone, I updated the block diagram. I would appreciate if someone can review it.
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
ok so you liked the idea of being able to make a games controller from the same PCB, then? :) it would be really simple, a piece of plastic and a USB connector - done!
Yes, it's a good idea.
The problem is that we are not a professional team, so we can now focus only on the handheld
games console. Daniel has very little free time, so for now we are progressing very slowly.
hey it was an easy idea... for another time, yes.
Another idea would be to create a EOMA-68 with FPGA (or similar) and use it as a pass-through
card. For example, you can connect a PC Gamer to HDMI and USB of this EOMA-68, and you have a PC as a handheld games console.
ah yeah of course, i forgot about that :)
btw could you use plain-text editing, not a rich-text format, with paragraphs broken up at (appx) 70 chars per line, please?
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
So we have two options, put the EINT in the headphone jack, or put (this) second EINT in
the FFC 40 pin connector in case we need it in the future on future screen. What is your recommendation?
i'd say keep it on the HP jack, just in case something needs to be altered (volume etc.) when switching between headphone and speaker mode.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
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
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest gacuest@gmail.com wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
l.
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
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
On Wed, Sep 23, 2015 at 4:07 PM, GaCuest gacuest@gmail.com wrote:
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
wiggle wiggle follow the lines with my finger pointing at the screen this time... :)
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
yes! :)
En 23 de septiembre de 2015 en 17:13:37, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 4:07 PM, GaCuest wrote:
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton (lkcl@lkcl.net)
escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
wiggle wiggle follow the lines with my finger pointing at the screen this time... :)
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
yes! :)
Then, anything to change?
Is this right?: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
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 Wed, Sep 23, 2015 at 4:31 PM, GaCuest gacuest@gmail.com wrote:
En 23 de septiembre de 2015 en 17:13:37, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 4:07 PM, GaCuest wrote:
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton (lkcl@lkcl.net)
escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram: http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
wiggle wiggle follow the lines with my finger pointing at the screen this time... :)
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
yes! :)
Then, anything to change?
no
Is this right?:
i did say yes
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
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
Hello there, sorry for not writing for so long. What would you recommend as the next step now? As I told Miguel privately, I was thinking of getting an STM32 evaluation board (they're really cheap, <15€ IIRC) and building the USB controller prototype. Once we have the STM32 reading all the values from the potentiometers, pushbuttons, etc. and reporting them over USB as a HID we would go ahead and design PCBs 2 and 3. How does this sound? Should we skip the eval board thing and go straight to designing the PCBs?
2015-09-23 19:44 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
On Wed, Sep 23, 2015 at 4:31 PM, GaCuest gacuest@gmail.com wrote:
En 23 de septiembre de 2015 en 17:13:37, Luke Kenneth Casson Leighton (
lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 4:07 PM, GaCuest wrote:
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton
(lkcl@lkcl.net)
escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
I’m using AirMail. It has plain text editing, but not line-wrap. I will do that manually.
appreciated.
I updated the block diagram:
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
wiggle wiggle follow the lines with my finger pointing at the screen this time... :)
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
yes! :)
Then, anything to change?
no
Is this right?:
i did say yes
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
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
En 28 de septiembre de 2015 en 9:52:43, Daniel Iglesias (daniel.iglesias@gmail.com) escrito:
Hello there, sorry for not writing for so long. What would you recommend as the next step now? As I told Miguel privately, I was thinking of getting an STM32 evaluation board (they're really cheap, <15€ IIRC) and building the USB controller prototype. Once we have the STM32 reading all the values from the potentiometers, pushbuttons, etc. and reporting them over USB as a HID we would go ahead and design PCBs 2 and 3. How does this sound? Should we skip the eval board thing and go straight to designing the PCBs?
Hello Daniel, Luke and everyone.
I want to introduce you to Peter Bouda.
He has contacted me because he liked the project.
He is a software developer ( http://www.ubrew.it/%C2%A0) and he has offered help to develop the software of the handheld games console.
He does not know a lot about hardware design, but he has told me he will try to learn more about this to help in the design of hardware. So maybe soon he can also help in the design of hardware.
Thanks!
2015-09-23 19:44 GMT+02:00 Luke Kenneth Casson Leighton :
On Wed, Sep 23, 2015 at 4:31 PM, GaCuest wrote:
En 23 de septiembre de 2015 en 17:13:37, Luke Kenneth Casson Leighton (
lkcl@lkcl.net) escrito:
On Wed, Sep 23, 2015 at 4:07 PM, GaCuest wrote:
En 23 de septiembre de 2015 en 16:55:18, Luke Kenneth Casson Leighton
(lkcl@lkcl.net)
escrito:
On Wed, Sep 23, 2015 at 2:59 PM, GaCuest wrote:
> I’m using AirMail. It has plain text editing, but not line-wrap. > I will do that manually.
appreciated.
> I updated the block diagram: >
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
> > Anything more to change?
yes, one thing that's important: 1st USB is mandated to be >= speed than 2nd USB. so you need to swap 1st USB with 2nd USB.
reason: the STM32F is connected to the port that may end up being 480mbit/sec and the USB Hub is connected to the port that may end up being only 11mbit/sec.
certainly, for the jz4775 CPU Card (which i am sending off very shortly), it *DEFINITELY* has USB 2.0 for the 1st port and *ONLY* USB 1.1 for the 2nd.
and i am certainly not going to increase the cost of the jz4775 CPU Card by an extra $2 worth of components to put in a USB2 Hub when the SOC itself is only $2.50!!!
I think that you have not properly seen the block diagram.
wiggle wiggle follow the lines with my finger pointing at the screen this time... :)
The STM32 is connected to the second USB, the USB HUB is connected to the first USB.
This right?
yes! :)
Then, anything to change?
no
Is this right?:
i did say yes
http://rhombus-tech.net/community_ideas/games_console/news/pcb_block_diagram...
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
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, Sep 28, 2015 at 10:09 AM, GaCuest gacuest@gmail.com wrote:
Hello Daniel, Luke and everyone.
I want to introduce you to Peter Bouda.
hi peter, welcome
He has contacted me because he liked the project.
He is a software developer ( http://www.ubrew.it/ ) and he has offered help to develop the software of the handheld games console.
great!
He does not know a lot about hardware design, but he has told me he will try to learn more about this to help in the design of hardware. So maybe soon he can also help in the design of hardware.
well there are a couple of main tasks, peter, software-wise. the first is integration of EOMA68 into the linux kernel, but i believe the team at your end decided that they won't support EOMA68 at a software level, only taking advantage of the hardware.
the second is, as daniel mentioned, the STM32F embedded controller. this i recommend using libopencm3 and i will help out by developing the firmware for the laptop_15in_pcb2 simultaneously. if you can send me an ssh public key i will arrange to add you to the git repository.
also i recommend joining the mailing list here, it will make life easier. or, you guys should probably set one up for the project: alain will almost certainly be happy to help there.
l.
well there are a couple of main tasks, peter, software-wise. the first is integration of EOMA68 into the linux kernel, but i believe the team at your end decided that they won't support EOMA68 at a software level, only taking advantage of the hardware.
the second is, as daniel mentioned, the STM32F embedded controller. this i recommend using libopencm3 and i will help out by developing the firmware for the laptop_15in_pcb2 simultaneously. if you can send me an ssh public key i will arrange to add you to the git repository.
also i recommend joining the mailing list here, it will make life easier. or, you guys should probably set one up for the project: alain will almost certainly be happy to help there.
l.
hi, first! this is really an awesome project, and I would be happy if I can contribute even some minor stuff. I will have a look at the libopencm3 and see what I can do (will send the public key). and probably order also order one of the STM32 boards and try to connect buttons...
what exactly would be the task of integrating EOMA68 into the linux kernel? for me this is mainly a way to learn about embedded system development, software and hardware side, so I am interested in anything related.
Best, Peter
On Mon, Sep 28, 2015 at 8:52 AM, Daniel Iglesias daniel.iglesias@gmail.com wrote:
Hello there, sorry for not writing for so long. What would you recommend as the next step now? As I told Miguel privately, I was thinking of getting an STM32 evaluation board (they're really cheap, <15€ IIRC)
i know, it's ridiculous! i bought one from reichhelt.de because they accept dutch iDEAL payment (no other reason!) and including shipping it was like... $EUR 12 or something silly. love it.
and building the USB controller prototype. Once we have the STM32 reading all the values from the potentiometers, pushbuttons, etc. and reporting them over USB as a HID we would go ahead and design PCBs 2 and 3. How does this sound?
great idea, i've done the same thing, bought an EVB, i have to do the software for the laptop_15in_pcb2 as well: that's going to be a 16x8 key-scan matrix and reading an I2C touchpanel, converting both to USB-HID.
Should we skip the eval board thing and go straight to designing the PCBs?
weeeellll, think about that for a moment: if there's a mistake in the design concept (STM32F072RBT6 isn't good enough for some reason) you just threw away the time and the money spent designing, assembling and then testing the PCBs.
if you're _really_ confident then go for it! i am merely... foolish / optimistic: i've designed and ordered the PCBs already (and have discovered missing components already *sigh*....)
btw miguel, daniel, one thing: you need to check if an FFC-6 can provide enough power to PCB2.
l.
En 28 de septiembre de 2015 en 12:37:53, Luke Kenneth Casson Leighton (lkcl@lkcl.net) escrito:
On Mon, Sep 28, 2015 at 8:52 AM, Daniel Iglesias wrote:
Hello there, sorry for not writing for so long. What would you recommend as the next step now? As I told Miguel privately, I was thinking of getting an STM32 evaluation board (they're really cheap, <15€ IIRC)
i know, it's ridiculous! i bought one from reichhelt.de because they accept dutch iDEAL payment (no other reason!) and including shipping it was like... $EUR 12 or something silly. love it.
and building the USB controller prototype. Once we have the STM32 reading all the values from the potentiometers, pushbuttons, etc. and reporting them over USB as a HID we would go ahead and design PCBs 2 and 3. How does this sound?
great idea, i've done the same thing, bought an EVB, i have to do the software for the laptop_15in_pcb2 as well: that's going to be a 16x8 key-scan matrix and reading an I2C touchpanel, converting both to USB-HID.
Should we skip the eval board thing and go straight to designing the PCBs?
weeeellll, think about that for a moment: if there's a mistake in the design concept (STM32F072RBT6 isn't good enough for some reason) you just threw away the time and the money spent designing, assembling and then testing the PCBs.
if you're _really_ confident then go for it! i am merely... foolish / optimistic: i've designed and ordered the PCBs already (and have discovered missing components already *sigh*....)
btw miguel, daniel, one thing: you need to check if an FFC-6 can provide enough power to PCB2.
What is the alternative?
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
On Mon, Sep 28, 2015 at 11:54 AM, GaCuest gacuest@gmail.com wrote:
btw miguel, daniel, one thing: you need to check if an FFC-6 can provide enough power to PCB2.
What is the alternative?
anything! wires, 6-pin 0.1 or 0.2mm pitch header, FPC, anything - just remember to check the current rating of whatever you decide to use, ok?
l.
On Mon, Sep 28, 2015 at 12:07 PM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 28, 2015 at 11:54 AM, GaCuest gacuest@gmail.com wrote:
btw miguel, daniel, one thing: you need to check if an FFC-6 can provide enough power to PCB2.
What is the alternative?
anything! wires, 6-pin 0.1 or 0.2mm pitch header, FPC, anything - just remember to check the current rating of whatever you decide to use, ok?
those SIM card holders i mentioned - absolutely anything. just check what current draw the STM32F072RBT6 is likely to use, it could be as low as 0.1A in which case you're fine... but you _need_ to check.
l.
2015-09-28 13:09 GMT+02:00, Luke Kenneth Casson Leighton lkcl@lkcl.net:
On Mon, Sep 28, 2015 at 12:07 PM, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
On Mon, Sep 28, 2015 at 11:54 AM, GaCuest gacuest@gmail.com wrote:
btw miguel, daniel, one thing: you need to check if an FFC-6 can provide enough power to PCB2.
What is the alternative?
anything! wires, 6-pin 0.1 or 0.2mm pitch header, FPC, anything - just remember to check the current rating of whatever you decide to use, ok?
those SIM card holders i mentioned - absolutely anything. just check what current draw the STM32F072RBT6 is likely to use, it could be as low as 0.1A in which case you're fine... but you _need_ to check.
Ok, thanks. That is something that Daniel has to check.
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@lists.phcomp.co.uk
-
Daniel Iglesias -
GaCuest -
Luke Kenneth Casson Leighton -
Miguel Garcia
-
Peter Bouda