If this is your first venture into the DaVinci development environment, I would strongly suggest staying within the distribution provided be TI. The package is reasonably complete and functional. I believe there are at least two significant issues to be concerned with when using the GIT kernel: The DM355 device comes in two version, 1.1 and 1.3. One of the differences is with how the device handles ECC. The early version only supported inline ECC, (512 + 16, 512 + 16, ...). The later version can handle either type of ECC. The TI package uses one form of ECC, the GIT package uses another. Google for DM35x_FlashAndBootUtils_1_50. This should lead you to a mirror site at the University of Kent. Unpacking and reading the readme files is pretty informative. I was unable to decompress the link on the Wiki page for these utils.

Camera Support: The TI package comes with sample drivers for the CCD and VPFE. I don't believe the GIT kernel provides these yet though I have seen a conversation discussing how best to add support for these devices.


Jean-Philippe François wrote:
Hi,

I have been looking at the wiki, and could not find what is the current status of support for DM355 EVM

Davinci git kernel tree seems to support some part of the DM355.
U-boot also as some support for davinci boards, but from the wiki I understood that for the DM355 there was some TI provided code I could not find a link too.

Here is the quote from the wiki :
DM355 and similar recent DaVinci chips aren't yet supported in mainline U-Boot; use the code supplied by TI.

Is there an online, updated version of this code, or should I use the DVSDK CD ?

Thank you in advance,
Jean-Philippe François


_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source




_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to