I'm curious about what motivated your design choice to use serial EEPROM instead of serial Flash? You could fit a 64 Mbit (2000x larger), 100 MHz (5x faster) Flash IC in the same package.
Downsides would be a few tens of microamps of standby power consumption (a rounding error given the other devices on the board/in the package), page-level erase and re-write (you have plenty of RAM to handle that hassle), and slightly reduced write endurance (but at a few hundred thousand cycles instead of a few thousand cycles, what applications would possibly notice the difference?).
The difference between 4kB (enough to store a serial number and a small bootloader) and 8 MB (large enough for small applications) is significant! The board could be half the size if it didn't need the uSD socket.
What is the EEPROM used for where Flash wouldn't be a better choice?
Some flash chips compensate by including a small amount of RAM to handle read-modify-write operations.
* faster writes
* lower peak power consumption
* lower flash wear
* less chance of data corruption should power fail mid-write
We're currently using Olimex's Am3352-SOM module in a product, and the Octavo SIP makes it simple enough to do a board down instead of a module... if only the SIPs were cheaper.
One other thing that I will mention is that the 21mm x 21mm form factor of the OSD335x-SM enables designs that would not be possible with other SOMs or discrete components since is 60% smaller than a discrete implementation.
How's this stock up to the BBB as far as power usage goes?
What's the supply chain look like for your silicon? Planning to maintain stock at the distributors?
Any plans for a non/through hole? Exposing the ethernet and MDIO pin headers for another SD card would be awesome. (Props for putting USB on the headers, and keeping the underside empty!)
Edit: Looks like you're planning more on using this as a demo-board for your chip. Does powering the chip from the LiPo handle the RTC, so I can stop dropping a DS1307 onboard? ;)
The OSD335x-SM uses the same power management solution as the BBB. The chip itself will consume less power than the BBB since it doesn't have all the additional peripherals.
We currently have stock as DigiKey and Mouser and will maintain stock. If you have additional questions on supply, feel free to contact us (https://octavosystems.com/contact/)
We do have other development boards for this processor (https://octavosystems.com/octavo_products/osd3358-sm-red/) more expensive, but more features.
There are still some issues around RTC. The PMIC that we use (TPS65217C) doesn't support RTC-only mode, so unfortunately, you will still probably want to use the discrete RTC to get the standby time you need.
[darth_vader_nooooo.gif]
Thanks for the responses Eric!
I used them to bit-bang MDIO (used by ethernet PHYs) and JTAG for debugging and burning fuses (strict timing requirements) in an IC.
It's cheap, easy to use, with good support, and much less of a barrier than an FPGA+ARM solution.
[1] http://elinux.org/images/d/da/Am335xPruReferenceGuide.pdf (page 14 for block diagram)
also wish it had some sort of networking option, e.g. esp8266 or wifi/BLE, kind of a standard need these days.
Wow. I've started to become mildly interested in chip manufacturing tech, and the fact that you can do that is really amazing. I'm very curious how this actually works!
Also is the U-Boot/Linux source between the PB and BBB the same? Namely due to the Octavo being more of a complete solution than the AM3358/PMIC/EEPROM setup the BBB has
The EEPROM identifier requires a small update to the bootloader and device tree.
I also noticed that the OSD335x-SM has got a EEPROM, which previous OSD335x module doesn't have. So basically OSD335x-SM is just a smaller and slightly better module than the previous one?
Yes. The OSD335x-SM is a smaller and more optimized module than the original OSD335x. Based on customer feedback from the OSD335x, we optimized the pin out to ease routing and reduced the size to enable more space constrained applications (The OSD335x-SM is 60% smaller than a discrete implementation: https://octavosystems.com/2017/08/30/smaller-cheaper-pcbs/)
How stable is the current chip design? I.e. will it be around for quite some time now?
Are you planning on letting clients customise the internal layout at some point?
What are your long-term goals and plans (that you can disclose)?
This is just the second device in what we see is a large space for System-in-Package devices. Please contact us (https://octavosystems.com/contact/) if you would like to discuss plans and goals in more detail.
https://octavosystems.com/app_notes/osd335x-power-applicatio...
https://octavosystems.com/app_notes/osd335x-software-control...
the power consumption numbers for the OSD335x-SM will be similar.
might want to notify your customer they have a typo in the first paragraph of their website
https://octavosystems.com/app_notes/osd335x-power-applicatio... https://octavosystems.com/app_notes/osd335x-software-control...