--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
Just think of the DM3730 as a die-shrink of the OMAP3530, that is what it boils down to.
Op 26 feb. 2011 om 19:17 heeft ZubairLK <zubair.l...@gmail.com> het volgende geschreven:
> Why didn't anyone say so earlier!?
>
> Thank-you.
>
> Ok.
>
> Based on your die-shrink statement and the following:
> "DM37x processors are software compatible with the OMAP35x generation
> of processors and pin-to-pin compatible with Sitara™ AM37x devices
> allowing for an easy product migration strategy to higher performing
> options. The differentiation between the DM3730 and DM3725 is that the
> DM3725 does not have a 3D graphics accelerator. Customers moving to
> the DM3730 from the OMAP3530 can look forward to a 50 percent increase
> in ARM performance, a 40 percent increase in DSP performance, double
> the graphics performance and uses approximately 40 percent less
> power." news release on ti for DM3730.
>
> A few clarifications please. Simple Answers are Yes most probably.
> But I'd like someone else to confirm as well.
>
> Can I use every single piece of code (DSP/BIOS link, DSPlib, SYS/Bios,
> etc) with the label OMAP3530 with DM3730?
>
yes
> To my knowledge, the one huge thing one should look out for is
> environment variable changes in uboot.
> Everything goes into boot.scr. No saveenv.
>
that isn't dependant on the omap, but the memory put on top
> Anything that comes to your mind that I should look out for?
> Like memory mapping changes. Device I/O Anything?
no, it's the same
> Especially related to GPIO, SPI driver, Angstrom/QT4-Embedded and the
> methods to establish a DSP-ARM link(DSP/BIOS link, C6run, etc)
> Cause I'll be using these in the project I'm working on.
Same again, no real changes
>
> To my knowledge, kernel is the code/thing that talks to the hardware.
> Can i use the SYS/BIOS kernel for OMAP3530 for DM3730?
> Are these two processors THAT compatible!?
>
Yes, thinking 3730 as a die shrink is the easiest way. The differences are:
updated a8 core
updated sgx core
updated dss block
updated musb block
'fast' dss pins moved
all of it, except the pins are just bugfixes for the silicon, no real changes.
From a sw point of view it's the same thing, just running faster. That's why you can share a single angstrom uSD card between a c4 and xm beagle
> On Feb 26, 1:34 pm, Koen Kooi <k...@beagleboard.org> wrote:
>> Op 26 feb 2011, om 08:24 heeft ZubairLK het volgende geschreven:
>>
>>> Is there a way to avoid C6run?
>>
>>> I can't seem to find a way to use dsp/bios link for the XM.
>>
>>> DM3730 isn't mentioned anywhere?
>>> In fact. I cant even find a DSP/Bios link release that says that the
>>> DM3730 is supported.
>>
>> Just think of the DM3730 as a die-shrink of the OMAP3530, that is what it boils down to.
>