On 12/04/2013 08:53, Alison Wang wrote:
This series contains the support for vybrid CPU and vf600 tower board.
The Vybrid devices are a family of Freescale's latest Dual Single Core offering with ARM Cortex A5 and CM4 based processors for Advanced Connected Radio, Entry Infotainment, and Cluster as well as high end industrial and general purpose applications.
Hi Alison,
because there is not yet documentation about this family on Freescale's webiste, could you please mention something more about this processor ?
This helps to better understand where we can put support inside U-Boot.
More or less the following information are very valueable :
- Are there common part (peripheral, controller,..) with other
Freescale's processors ? I doubt there is no point of contact, at least with i.MX6.
[Alison Wang] This Vybird VF600 family is a heterogeneous dual-core eMPU family combining the ARM(r) Cortex(tm)-A5 and Cortex(tm)-M4 cores. The u-boot and kernel are implemented on the A5 core. So the core is different with current I.MX family. However, this SOC still shares some IPs with I.MX family, such as FEC,ESDHC,WATCHDOG,I2C,ASRC and ESAI.This SOC also shares some IPs with ColdFire platform, such as eDMA and DSPI. And this SOC still has its own IPs such as PIT, SAI, UART, QSPI and DCU.
More documents for this soc can be found at: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=VF6xx&fsr... http://www.freescale.com/webapp/sps/site/homepage.jsp?code=VYBRID
I will include this kind of descriptions in the next version patches.
Specially for the u-boot porting, the system clock settings such as the CCM and ANADIG, the timer and the iomux on this platform are not identical with the I.MX platform. More following discussions will be put on that. Thanks.
- Which peripheral are reused in this SOC ? I understand in your patchset
that ESDHC is reused, I think also FEC, I wonder that UART is not.
[Alison Wang] Yes, ESDHC and FEC could be reused with the current code. UART needs to be written as a new driver.
- Which image is produced ? I do not understand why you need a new type
if you reuse the same rule (mkimage for imx) we have.
[Alison Wang] There are still some differences with the I.MX family as described above, so I used different type in the last patch. I'm trying to align the vybrid with imx platform and this kind of reuse will be found in next version patches.
Thanks a lot!
Best Regards, Alison Wang