-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A600 support #18
Comments
We're working on a A600 version of the hardware, and while it's still in the design phase, we can already now conclude it will only be able to support the Pi Zero form factor due to mechanical restrictions. More info will be posted once there is some real hardware produced. Probable time frame is Q1 2020. |
Update: A600 version is now actively being worked on. We can already now see that there will be a couple of differences compared to the A500 version:
|
If the A600 version can only support a Pi Zero due to physical limitations, could it alternatively support a CM3 compute module? |
It could, but it won't because we see it as a too big re-design for very little, if any, advantages. So the cost/performance ratio is not justifiable. |
The cost is exactly the same as being able to use a full Pi 3 B+. It's more than a Pi Zero, but then the design brief calls using a Pi Zero a "design limitation"... ;) The physical advantages are numerous. Being able to place the connectors exactly where they are best suited. Being able to place only the connectors required. Lower power footprint by not using devices that are not installed. Extremely compact form. I'd be happy to design this PCB. |
@plasticuser If you feel up to designing and building a version of A314 for A600 using a CM3 compute module then of course that would be a very positive development :) My initial thoughts about such a design is: how will you add back networking (wifi) and USB capabilities that are not available in CM3 (as compared to in Pi Zero)? And what is the combined cost of CM3 + additional chips? If the cost is not a lot more than a Pi3 then this sounds very interesting. |
I recognize it would cost a "little" more. I'm estimating about $7-$9. The fun bit is that I could supply the board with build time configuration options to lower the price point. Happy with ethernet? Cool! Want lots of I2C or SPI break outs on the board? Cool! 2MB SRAM? Yisss! It is worth $10 on the final product price to have the four cores, and the option of SSD or eMMC - which is MUCH faster and more reliable. The CM4 is going to have a different pinout, but it would be easy to adapt the design at that point for the new connector. So, yes, I'll happily do it, and I'd prefer to do it within your project than forking it and creating confusion and lots of extra work for myself ;) |
@plasticuser That sounds great! Let us know if you have any questions or need help with anything. |
I shall. |
Previously there was a separate branch for the A600 version of A314, but this functionality has now been merged into the master branch. A new revision, a314_600, has been added to the Quartus project. A macro, is_a600, is used to control the compilation in a few places, mostly in the top entity a314_top.v. A new SPI protocol command has been added, SPI_PROTOCOL_VERSION. On older HDL this command returns the default value zero, and this version returns one. The a314d uses this protocol version number to be able to communicate with both the current and older versions of the HDL. The firmware version number has been replaced with a firmware flags value, that consists of multiple bit flags that describes what capabilities the firmware has. Ideally this commit should probably have been multiple smaller commits, but to save time I didn't bother to split it up.
Fixed by commit c04a519. |
Would be nice to add support for Amiga 600, or if it is allready supported, validate it by test and clarify the support in documentation and description of the project.
The text was updated successfully, but these errors were encountered: