4 ms·
I'm working on a project right now that started pretty much the way you described. We took Freescale's SABRE SD schematics and DNIed the stuff that wasn't nece
by joezydeco 13y ago
I'm working on a project right now that started pretty much the way you described. We took Freescale's SABRE SD schematics and DNIed the stuff that wasn't necessary.
I will say that I like working with Freescale's reference material better than, say, TI's OMAP and AM series. Of course I work for a larger company that has easy access to their FAEs, but at least they have an online forum where you can get answers...sometimes.
You've sniffed out one big problem with the Cadence Orcad layout. Freescale recommends you just cut-and-paste the DDR3 lines directly from their layout. Partially because the timing is so hard to get right and partially because they don't have the bandwidth to help you debug your board layout. So that's probably the biggest hurdle in layout. TI went a different way with package-on-package RAM mounting, but that's another set of headaches when it's time to build boards.
Another nice part is that you can get working boards today if you want them. I'm a big fan of Boundary Devices (http://www.boundarydevices.com http://www.boundarydevices.com), you can get a SABRE-based board for $99. Pick up the kernel patches from FSL and you can have your own system building and running in an afternoon.
The i.MX6 is also a nice evolution of their SoC family, especially now that you can opt out of their power-management IC. But that means a bit more schematic and layout work if you choose to go that route. I'd leave the PMIC in, you also get some nice additional features if you use it.
- kabdib 13y agoFreescale's documentation was fantastic. TI's was mostly good, except for whole areas they left out. Marvell . . . hoo boy. Let's just say that everyone telling us "If you go with Marvell, you're in for a ride" was correct. Just enough detail to get you into trouble. Cheap, though. . . . :-)
- joezydeco 13y agoYeah thankfully I never got that far with Marvell. We had their eval platform while also looking at the iMX (well, we just bought a Nitrogen from Boundary. Much easier). The Marvell platform was just a trainwreck. Even simple questions were met with blank stares.
- kabdib 13y agoWe had to talk to the actual chip designers to get questions answered. After weeks of asking stuff that just got echo-chambered back. Us: "We want to know the delay period between freezing the timer and reading it. The documentation says 'three clocks', but we have strong evidence this is not accurate." Marvell: "We are happy to help with your question. You need to wait three clock cycles." Us: "That doesn't work. (insert mountain of evidence here)." Marvell: "Let us get back to you." (much later) Us: "Remember that question about the clock register?" Marvell: "What question?" (repeat above, several times) Much later, we get a phone session together. Obviously new Marvell chip designer: "It says three clock cycles here." Us: (lots more evidence that that is not the case) Slightly terrified (but still new) Marvell chip designer: "Let us get back to you." (much, much later ...) Marvell Chip designer, who clearly has his act together, but designed the circuit four years ago and can't remember, so he digs into the design files: "Oh yeah. Three clocks, but they're internal, so you can't see them. Use this clock over /here/ and write this, then read that, and you should be good." Repeat for each major chip feature, and don't get me started on DRAM controllers or USB PHY registers.
- joezydeco 13y agoWow, that's pretty bad. I've never had to go that deep with a chip manufacturer. Then again I've been using Motorola/Freescale for 30 years...