This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

am335x linux-sdk source traceability?

Other Parts Discussed in Thread: TMDXEVM3358

Hi all,

We are currently working on an industrial application that needs to be certified as secure by an authority.

To be able to do so we need to track changes made to the u-boot and Linux kernel sources as to prove that no tampering has been done to the sources.

The problem is that the current distribution is in the form of source dumps without any history attached to it. And proofreading the diff between the SDK and say Linux src 3.2.0 is  We have dug into this but are unable to find one source of origin with history.

My question is, do there exist any source repository, git preferably then, that we can use that gives us complete traceability back to the fork from kernel.org?

If this isn't the case. In what shape is the latest stable kernel.org release with respect to am335x? The project complexity is somewhat in parity with the TMDXEVM3358 devkit. I.e. we need quite a lot of peripheral support which do exist in the linux ti sdk then.

Regards

/Tor

  • The release notes have the information: the url of the git repo, and git tag for the release.

    For example, http://processors.wiki.ti.com/index.php/AM335x-PSP_04.06.00.10_Release_Notes is the PSP release notes for for AMSDK 5.7.0.0, which has all the information.

  • Hi Bin,

    Thanks for the quick reply and the information.

    The big problem is that I can't get this to add up. If i diff u-boot git v2013.01.01 and the board-support/u-boot-2013.01.01-psp05.07.00.00 I get a ~370KB diff.

    If I do the same thing for the Linux kernel, linux-am33x and board-support/linux-3.2.0-psp04.06.00.10, with patches removed, things are manageable i get a mere 80K diff with mainly one added kernel config file.

    The question is what the difference is, especially in the u-boot case then.

    Regards

    /Tor

  • Tor,

    I don't think you get my point. The release notes have the information of where in the Arago project git repo the SDK was built from, following that you can check all the change histories in the Arago git repository - every patch.

    I don't think it is possible to figure out the changes from diff.

  • Hi Bin,

    Sorry for not reading the release notes thoroughly enough :( I stopped reading after the first mention of the references to upstream sources.

    Using the git.ti.com and arago repositories with mentioned tag/commit produces a much better result. I think we can work with this.

    Thx

    /Tor