cdocutils.nodes document q)q}q(U nametypesq}q(XipcqX&amsdk to processor sdk migration guideqNXkernel-driversqXpasaq Xinstall-packagesq Xmigration-from-bios-mcsdk-c66xq Xmigration guideq NXkeystone_remoteprocq XroadmapqXcpsw-cpdma-descriptor-usageqX tool-chainqX.building-the-linux-sdk-mcsdk-to-procsdk-omapl1qX$directory-structure-mcsdk-to-procsdkqXprocessor sdk 04.xx releasesqNXcsl-1qXplatform-libraryqXprocessor sdk 02.00.00qNXprocessor sdk 02.00.01qNXprocessor sdk 02.00.02qNXu-boot-mcsdk-to-procsdk-omapl1qXcommand-line-installationqXdirectory-structure-1qX documentationqNXprocessor sdk 05.02qNXprocessor sdk 05.03qNXprocessor sdk 05.00qNXprocessor sdk 05.01q NXprocessor sdk 03.xx releasesq!NXqmssq"X&target-machine-mcsdk-to-procsdk-omapl1q#X!inter-processor-communication-ipcq$Xkeystone-2-featuresq%Xapplication developmentq&NX-migrating from amsdk 8.0 to processor sdk 1.0q'NX.common-migration-for-both-mcsdk-and-bios-mcsdkq(X8mcsdk1.1-to-processor-sdk-migration-for-omapl13x-devicesq)X+directory-structure-mcsdk-to-procsdk-omapl1q*Xhardware platformsq+NXprocessor sdk 03.01q,NXpruss-remoteproc-1q-X pci-endpointq.Xu-boot-rndis-bootq/Xprocessor sdk 05.xx releasesq0NXk2-serdes-driversq1X$linux-kernel-mcsdk-to-procsdk-omapl1q2X prueth-driverq3X netcp-driversq4X board portingq5NXtarget-machine-mcsdk-to-procsdkq6X pcie-driverq7Xprocessor sdk 06.03q8NXprocessor sdk 06.02q9NXprocessor sdk 06.01q:NXprocessor sdk 06.00q;NXDmcsdk1.1 to processor sdk linux migration guide for omapl13x devicesqXcppiq?X$installation-mcsdk-to-procsdk-omapl1q@X&mcsdk to processor sdk migration guideqANXgetting-startedqBX installationqCXprocessor sdk 03.02qDNXprocessor sdk 04.01qENXprocessor sdk 04.00qFNXprocessor sdk 04.03qGNXprocessor sdk 04.02qHNXhua-demonstrationqIXsummaryqJNXcslqKXprocessor sdk 02.xx releasesqLNXprocessor sdk 03.00qMNXipc-1qNXprocessor sdk 06.xx releasesqONXprocessor sdk 03.03qPNXpruss-remoteprocqQX'building-the-linux-sdk-mcsdk-to-procsdkqRXgui-developmentqSXdisplayqTXlinux-kernel-mcsdk-to-procsdkqUXu-boot-mcsdk-to-procsdkqVuUsubstitution_defsqW}qXUparse_messagesqY]qZUcurrent_sourceq[NU decorationq\NUautofootnote_startq]KUnameidsq^}q_(hUipcq`hU&amsdk-to-processor-sdk-migration-guideqahUkernel-driversqbh Upasaqch Uinstall-packagesqdh Umigration-from-bios-mcsdk-c66xqeh Umigration-guideqfh Ukeystone-remoteprocqghUroadmapqhhUcpsw-cpdma-descriptor-usageqihU tool-chainqjhU.building-the-linux-sdk-mcsdk-to-procsdk-omapl1qkhU$directory-structure-mcsdk-to-procsdkqlhUprocessor-sdk-04-xx-releasesqmhUcsl-1qnhUplatform-libraryqohUprocessor-sdk-02-00-00qphUprocessor-sdk-02-00-01qqhUprocessor-sdk-02-00-02qrhUu-boot-mcsdk-to-procsdk-omapl1qshUcommand-line-installationqthUdirectory-structure-1quhU documentationqvhUprocessor-sdk-05-02qwhUprocessor-sdk-05-03qxhUprocessor-sdk-05-00qyh Uprocessor-sdk-05-01qzh!Uprocessor-sdk-03-xx-releasesq{h"Uqmssq|h#U&target-machine-mcsdk-to-procsdk-omapl1q}h$U!inter-processor-communication-ipcq~h%Ukeystone-2-featuresqh&Uapplication-developmentqh'U-migrating-from-amsdk-8-0-to-processor-sdk-1-0qh(U.common-migration-for-both-mcsdk-and-bios-mcsdkqh)U8mcsdk1-1-to-processor-sdk-migration-for-omapl13x-devicesqh*U+directory-structure-mcsdk-to-procsdk-omapl1qh+Uhardware-platformsqh,Uprocessor-sdk-03-01qh-Upruss-remoteproc-1qh.U pci-endpointqh/Uu-boot-rndis-bootqh0Uprocessor-sdk-05-xx-releasesqh1Uk2-serdes-driversqh2U$linux-kernel-mcsdk-to-procsdk-omapl1qh3U prueth-driverqh4U netcp-driversqh5U board-portingqh6Utarget-machine-mcsdk-to-procsdkqh7U pcie-driverqh8Uprocessor-sdk-06-03qh9Uprocessor-sdk-06-02qh:Uprocessor-sdk-06-01qh;Uprocessor-sdk-06-00qhUgetting-started-1qh?Ucppiqh@U$installation-mcsdk-to-procsdk-omapl1qhAU&mcsdk-to-processor-sdk-migration-guideqhBUgetting-startedqhCU installationqhDUprocessor-sdk-03-02qhEUprocessor-sdk-04-01qhFUprocessor-sdk-04-00qhGUprocessor-sdk-04-03qhHUprocessor-sdk-04-02qhIUhua-demonstrationqhJUsummaryqhKUcslqhLUprocessor-sdk-02-xx-releasesqhMUprocessor-sdk-03-00qhNUipc-1qhOUprocessor-sdk-06-xx-releasesqhPUprocessor-sdk-03-03qhQUpruss-remoteprocqhRU'building-the-linux-sdk-mcsdk-to-procsdkqhSUgui-developmentqhTUdisplayqhUUlinux-kernel-mcsdk-to-procsdkqhVUu-boot-mcsdk-to-procsdkquUchildrenq]q(cdocutils.nodes comment q)q}q(U rawsourceqXKhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Migration_GuideUparentqhUsourceqcdocutils.nodes reprunicode qXIsource/linux/Release_Specific/Processor_SDK_Linux_Migration_Guide.rst.incqq}qbUtagnameqUcommentqU attributesq}q(U xml:spaceqUpreserveqUidsq]Ubackrefsq]Udupnamesq]Uclassesq]Unamesq]uUlineqKUdocumentqhh]qcdocutils.nodes Text qXKhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Migration_Guideq̅q}q(hUhhubaubcdocutils.nodes section q)q}q(hUhhhhhUsectionqh}q(h]h]h]h]qhfah]qh auhKhhh]q(cdocutils.nodes title q)q}q(hXMigration GuideqhhhhhUtitleqh}q(h]h]h]h]h]uhKhhh]qhXMigration Guideqޅq}q(hhhhubaubcdocutils.nodes rubric q)q}q(hXOverviewqhhhhhUrubricqh}q(h]h]h]h]h]uhKhhh]qhXOverviewq腁q}q(hhhhubaubcdocutils.nodes paragraph q)q}q(hXdThis page covers migration information for applications built on top of the Processor SDK for Linux.qhhhhhU paragraphqh}q(h]h]h]h]h]uhK hhh]qhXdThis page covers migration information for applications built on top of the Processor SDK for Linux.qq}q(hhhhubaubh)q}q(hUhhhhhhh}q(h]h]h]h]qhah]qhOauhK hhh]q(h)q}q(hXProcessor SDK 06.xx Releasesqhhhhhhh}q(h]h]h]h]h]uhK hhh]qhXProcessor SDK 06.xx Releasesrr}r(hhhhubaubh)r}r(hUhhhhhhh}r(h]h]h]h]rhah]rh8auhKhhh]r(h)r }r (hXProcessor SDK 06.03r hjhhhhh}r (h]h]h]h]h]uhKhhh]r hXProcessor SDK 06.03rr}r(hj hj ubaubcdocutils.nodes bullet_list r)r}r(hUhjhhhU bullet_listrh}r(UbulletrX-h]h]h]h]h]uhKhhh]r(cdocutils.nodes list_item r)r}r(hXWThis is a quarterly update release on 2019 LTS stream and final release on that stream.rhjhhhU list_itemrh}r(h]h]h]h]h]uhNhhh]rh)r}r (hjhjhhhhh}r!(h]h]h]h]h]uhKh]r"hXWThis is a quarterly update release on 2019 LTS stream and final release on that stream.r#r$}r%(hjhjubaubaubj)r&}r'(hXICSSM PRUETH: Network storm prevention enhancements. Please check 4.2.4.7 Network Storm Prevention section of user guide, for changes in user interface for configuring storm prevention. hjhhhjh}r((h]h]h]h]h]uhNhhh]r)h)r*}r+(hXICSSM PRUETH: Network storm prevention enhancements. Please check 4.2.4.7 Network Storm Prevention section of user guide, for changes in user interface for configuring storm prevention.r,hj&hhhhh}r-(h]h]h]h]h]uhKh]r.hXICSSM PRUETH: Network storm prevention enhancements. Please check 4.2.4.7 Network Storm Prevention section of user guide, for changes in user interface for configuring storm prevention.r/r0}r1(hj,hj*ubaubaubeubeubh)r2}r3(hUhhhhhhh}r4(h]h]h]h]r5hah]r6h9auhKhhh]r7(h)r8}r9(hXProcessor SDK 06.02r:hj2hhhhh}r;(h]h]h]h]h]uhKhhh]r<hXProcessor SDK 06.02r=r>}r?(hj:hj8ubaubj)r@}rA(hUhj2hhhjh}rB(jX-h]h]h]h]h]uhKhhh]rC(j)rD}rE(hX6This is a quarterly update release on 2019 LTS stream.rFhj@hhhjh}rG(h]h]h]h]h]uhNhhh]rHh)rI}rJ(hjFhjDhhhhh}rK(h]h]h]h]h]uhKh]rLhX6This is a quarterly update release on 2019 LTS stream.rMrN}rO(hjFhjIubaubaubj)rP}rQ(hXWNote that this version of Processor SDK updates only AM5 and AM6 platforms w/ Linux OS.rRhj@hhhjh}rS(h]h]h]h]h]uhNhhh]rTh)rU}rV(hjRhjPhhhhh}rW(h]h]h]h]h]uhKh]rXhXWNote that this version of Processor SDK updates only AM5 and AM6 platforms w/ Linux OS.rYrZ}r[(hjRhjUubaubaubj)r\}r](hXsThe SGX driver has been enhanced to replace IMG WSEGL with MESA-EGL which supports the essential EGL 1.5 extensions required by the latest versions of certain graphics applications such as Chromium browser. See `here `__ for more details about compatability hj@hhhjh}r^(h]h]h]h]h]uhNhhh]r_h)r`}ra(hXrThe SGX driver has been enhanced to replace IMG WSEGL with MESA-EGL which supports the essential EGL 1.5 extensions required by the latest versions of certain graphics applications such as Chromium browser. See `here `__ for more details about compatabilityhj\hhhhh}rb(h]h]h]h]h]uhKh]rc(hXThe SGX driver has been enhanced to replace IMG WSEGL with MESA-EGL which supports the essential EGL 1.5 extensions required by the latest versions of certain graphics applications such as Chromium browser. See rdre}rf(hXThe SGX driver has been enhanced to replace IMG WSEGL with MESA-EGL which supports the essential EGL 1.5 extensions required by the latest versions of certain graphics applications such as Chromium browser. See hj`ubcdocutils.nodes reference rg)rh}ri(hXz`here `__h}rj(UnameXhereUrefurirkXoFoundational_Components/Graphics/Migration_From_Prior_Releases.html#from-processor-sdk-6-1-to-6-2-for-am3-4-5-6h]h]h]h]h]uhj`h]rlhXherermrn}ro(hUhjhubahU referencerpubhX% for more details about compatabilityrqrr}rs(hX% for more details about compatabilityhj`ubeubaubeubeubh)rt}ru(hUhhhhhhh}rv(h]h]h]h]rwhah]rxh:auhKhhh]ry(h)rz}r{(hXProcessor SDK 06.01r|hjthhhhh}r}(h]h]h]h]h]uhKhhh]r~hXProcessor SDK 06.01rr}r(hj|hjzubaubj)r}r(hUhjthhhjh}r(jX-h]h]h]h]h]uhKhhh]r(j)r}r(hX6This is a quarterly update release on 2019 LTS stream.rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX6This is a quarterly update release on 2019 LTS stream.rr}r(hjhjubaubaubj)r}r(hXwEMAC firmware - PRP Firmware in EMAC mode can be obsolete, as EMAC firmware has been made to be feature parity for SAN hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXvEMAC firmware - PRP Firmware in EMAC mode can be obsolete, as EMAC firmware has been made to be feature parity for SANrhjhhhhh}r(h]h]h]h]h]uhKh]rhXvEMAC firmware - PRP Firmware in EMAC mode can be obsolete, as EMAC firmware has been made to be feature parity for SANrr}r(hjhjubaubaubeubeubh)r}r(hUhhhhhhh}r(h]h]h]h]rhah]rh;auhK!hhh]r(h)r}r(hXProcessor SDK 06.00rhjhhhhh}r(h]h]h]h]h]uhK!hhh]rhXProcessor SDK 06.00rr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhK"hhh]r(j)r}r(hXThis is the first release in 2019 LTS stream, with new versions of Kernel, U-boot, toolchain and Yocto branch. Please see `SDK Components & Versions `__.rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK"h]r(hXzThis is the first release in 2019 LTS stream, with new versions of Kernel, U-boot, toolchain and Yocto branch. Please see rr}r(hXzThis is the first release in 2019 LTS stream, with new versions of Kernel, U-boot, toolchain and Yocto branch. Please see hjubjg)r}r(hX[`SDK Components & Versions `__h}r(UnameXSDK Components & VersionsjkX;Release_Specific_Release_Notes.html#sdk-components-versionsh]h]h]h]h]uhjh]rhXSDK Components & Versionsrr}r(hUhjubahjpubhX.r}r(hX.hjubeubaubj)r}r(hX Toplevel Makefile: There are additional packages required on the host, such as flex, bison and libssl-dev, for the top-level Makefile to build successfully. You can find the complete list of required host packages in `this chapter `__rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK#h]r(hXToplevel Makefile: There are additional packages required on the host, such as flex, bison and libssl-dev, for the top-level Makefile to build successfully. You can find the complete list of required host packages in rr}r(hXToplevel Makefile: There are additional packages required on the host, such as flex, bison and libssl-dev, for the top-level Makefile to build successfully. You can find the complete list of required host packages in hjubjg)r}r(hX3`this chapter `__h}r(UnameX this chapterjkX Overview/Top_Level_Makefile.htmlh]h]h]h]h]uhjh]rhX this chapterrr}r(hUhjubahjpubeubaubj)r}r(hXResistive Touchscreen TSCADC (resistive touchscreen) wakeup control on AM335x and AM437x has moved from TSCADC MFD device node to TSC input device node. - Disable touchscreen as wakeup source use: echo disabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeup - Enable touchscreen as wakeup source use: echo enabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuphjhNhjh}r(h]h]h]h]h]uhNhhh]rcdocutils.nodes definition_list r)r}r(hUh}r(h]h]h]h]h]uhjh]rcdocutils.nodes definition_list_item r)r}r(hXResistive Touchscreen TSCADC (resistive touchscreen) wakeup control on AM335x and AM437x has moved from TSCADC MFD device node to TSC input device node. - Disable touchscreen as wakeup source use: echo disabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeup - Enable touchscreen as wakeup source use: echo enabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuphjhhhUdefinition_list_itemrh}r(h]h]h]h]h]uhK%h]r(cdocutils.nodes term r)r}r(hXResistive Touchscreen TSCADC (resistive touchscreen) wakeup control on AM335x and AM437x has moved from TSCADC MFD device node to TSC input device node.rhjhhhUtermrh}r(h]h]h]h]h]uhK%h]rhXResistive Touchscreen TSCADC (resistive touchscreen) wakeup control on AM335x and AM437x has moved from TSCADC MFD device node to TSC input device node.rr}r(hjhjubaubcdocutils.nodes definition r)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXDisable touchscreen as wakeup source use: echo disabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuprh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK%h]rhXDisable touchscreen as wakeup source use: echo disabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuprr}r(hjhjubaubahjubj)r}r(hXEnable touchscreen as wakeup source use: echo enabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuprh}r (h]h]h]h]h]uhjh]r h)r }r (hjhjhhhhh}r (h]h]h]h]h]uhK&h]rhXEnable touchscreen as wakeup source use: echo enabled > /sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc.0.auto/power/wakeuprr}r(hjhj ubaubahjubehjubahU definitionrubeubahUdefinition_listrubaubj)r}r(hXIPC - Remoteproc core - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels. - PRUSS remoteproc - The PRUSS remoteproc bindings and drivers have been split up into three separate folders - New bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txt - PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folder - pruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder. - Userspace - New IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00 hjhNhjh}r(h]h]h]h]h]uhNhhh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXIPC - Remoteproc core - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels. - PRUSS remoteproc - The PRUSS remoteproc bindings and drivers have been split up into three separate folders - New bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txt - PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folder - pruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder. - Userspace - New IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00 hjhhhjh}r(h]h]h]h]h]uhK0h]r(j)r }r!(hXIPCr"hjhhhjh}r#(h]h]h]h]h]uhK0h]r$hXIPCr%r&}r'(hj"hj ubaubj)r(}r)(hUh}r*(h]h]h]h]h]uhjh]r+j)r,}r-(hUh}r.(jX-h]h]h]h]h]uhj(h]r/(j)r0}r1(hXRemoteproc core - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels.h}r2(h]h]h]h]h]uhj,h]r3j)r4}r5(hUh}r6(h]h]h]h]h]uhj0h]r7j)r8}r9(hXRemoteproc core - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels.hj4hhhjh}r:(h]h]h]h]h]uhK(h]r;(j)r<}r=(hXRemoteproc corer>hj8hhhjh}r?(h]h]h]h]h]uhK(h]r@hXRemoteproc corerArB}rC(hj>hj<ubaubj)rD}rE(hUh}rF(h]h]h]h]h]uhj8h]rGj)rH}rI(hUh}rJ(jX-h]h]h]h]h]uhjDh]rKj)rL}rM(hXError recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels.rNh}rO(h]h]h]h]h]uhjHh]rPh)rQ}rR(hjNhjLhhhhh}rS(h]h]h]h]h]uhK)h]rThXError recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.19 kernel. Error recovery is supported only on TI kernels.rUrV}rW(hjNhjQubaubahjubahjubahjubeubahjubahjubj)rX}rY(hXPRUSS remoteproc - The PRUSS remoteproc bindings and drivers have been split up into three separate folders - New bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txt - PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folder - pruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder.h}rZ(h]h]h]h]h]uhj,h]r[j)r\}r](hUh}r^(h]h]h]h]h]uhjXh]r_j)r`}ra(hXPRUSS remoteproc - The PRUSS remoteproc bindings and drivers have been split up into three separate folders - New bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txt - PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folder - pruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder.hj\hhhjh}rb(h]h]h]h]h]uhK-h]rc(j)rd}re(hXPRUSS remoteprocrfhj`hhhjh}rg(h]h]h]h]h]uhK-h]rhhXPRUSS remoteprocrirj}rk(hjfhjdubaubj)rl}rm(hUh}rn(h]h]h]h]h]uhj`h]roj)rp}rq(hUh}rr(jX-h]h]h]h]h]uhjlh]rs(j)rt}ru(hXXThe PRUSS remoteproc bindings and drivers have been split up into three separate foldersrvh}rw(h]h]h]h]h]uhjph]rxh)ry}rz(hjvhjthhhhh}r{(h]h]h]h]h]uhK+h]r|hXXThe PRUSS remoteproc bindings and drivers have been split up into three separate foldersr}r~}r(hjvhjyubaubahjubj)r}r(hXNew bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txtrh}r(h]h]h]h]h]uhjph]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK,h]rhXNew bindings are defined in soc/ti/ti,pruss.txt, interrupt-controller/ti,pruss-intc.txt and remoteproc/ti,pru-rproc.txt under the Documentation/devicetree/bindings folder and replaces remoteproc/ti,pruss-remoteproc.txtrr}r(hjhjubaubahjubj)r}r(hX_PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folderrh}r(h]h]h]h]h]uhjph]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK-h]rhX_PRUSS INTC module pruss_intc.ko is now irq-pruss-intc.ko and is built in drivers/irqchip folderrr}r(hjhjubaubahjubj)r}r(hXPpruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder.rh}r(h]h]h]h]h]uhjph]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK.h]rhXPpruss_soc_bus and pruss platform drivers are now built in drivers/soc/ti folder.rr}r(hjhjubaubahjubehjubahjubeubahjubahjubj)r}r(hXUserspace - New IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00 h}r(h]h]h]h]h]uhj,h]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXUserspace - New IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00 hjhhhjh}r(h]h]h]h]h]uhK0h]r(j)r}r(hX Userspacerhjhhhjh}r(h]h]h]h]h]uhK0h]rhX Userspacerr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]rj)r}r(hXNew IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00 h}r(h]h]h]h]h]uhjh]rh)r}r(hXNew IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00rhjhhhhh}r(h]h]h]h]h]uhK0h]rhXNew IPC and CMEM releases are needed to use with 4.19 kernel due to difference in AF_RPMSG family number and other kernel API changes. Minimum required versions are IPC 3.50.03.05 and CMEM 4.16.00.00rr}r(hjhjubaubahjubahjubahjubeubahjubahjubehjubahjubeubahjubaubj)r}r(hXJPRUETH - On AM571x IDK boards, the naming of the PRUETH supported ethernet ports has changed. In previous releases, PRU-ICSS1 (J3, J5 on IDK) corresponded to eth4/5, and PRU-ICSS2 (J6, J8 on IDK) corresponded to eth2/3. As of 06.00, this has swapped, and now PRU-ICSS1 corresponds to eth2/3, and PRU-ICSS2 corresponds to eth4/5. hjhNhjh}r(h]h]h]h]h]uhNhhh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXIPRUETH - On AM571x IDK boards, the naming of the PRUETH supported ethernet ports has changed. In previous releases, PRU-ICSS1 (J3, J5 on IDK) corresponded to eth4/5, and PRU-ICSS2 (J6, J8 on IDK) corresponded to eth2/3. As of 06.00, this has swapped, and now PRU-ICSS1 corresponds to eth2/3, and PRU-ICSS2 corresponds to eth4/5. hjhhhjh}r(h]h]h]h]h]uhK3h]r(j)r}r(hXPRUETHrhjhhhjh}r(h]h]h]h]h]uhK3h]rhXPRUETHrr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]rj)r}r(hX@On AM571x IDK boards, the naming of the PRUETH supported ethernet ports has changed. In previous releases, PRU-ICSS1 (J3, J5 on IDK) corresponded to eth4/5, and PRU-ICSS2 (J6, J8 on IDK) corresponded to eth2/3. As of 06.00, this has swapped, and now PRU-ICSS1 corresponds to eth2/3, and PRU-ICSS2 corresponds to eth4/5. h}r(h]h]h]h]h]uhjh]rh)r}r(hX?On AM571x IDK boards, the naming of the PRUETH supported ethernet ports has changed. In previous releases, PRU-ICSS1 (J3, J5 on IDK) corresponded to eth4/5, and PRU-ICSS2 (J6, J8 on IDK) corresponded to eth2/3. As of 06.00, this has swapped, and now PRU-ICSS1 corresponds to eth2/3, and PRU-ICSS2 corresponds to eth4/5.rhjhhhhh}r(h]h]h]h]h]uhK3h]rhX?On AM571x IDK boards, the naming of the PRUETH supported ethernet ports has changed. In previous releases, PRU-ICSS1 (J3, J5 on IDK) corresponded to eth4/5, and PRU-ICSS2 (J6, J8 on IDK) corresponded to eth2/3. As of 06.00, this has swapped, and now PRU-ICSS1 corresponds to eth2/3, and PRU-ICSS2 corresponds to eth4/5.rr}r(hjhjubaubahjubahjubahjubeubahjubaubj)r}r(hXJailhouse AM57xx support rebased to v0.10 version - Added shared memory region between Linux, hypervisor, and inmate console - Startup code of the inmate library enables MMU. An inmate has to initialize its MMU table by itself. hjhNhjh}r(h]h]h]h]h]uhNhhh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXJailhouse AM57xx support rebased to v0.10 version - Added shared memory region between Linux, hypervisor, and inmate console - Startup code of the inmate library enables MMU. An inmate has to initialize its MMU table by itself. hjhhhjh}r(h]h]h]h]h]uhK9h]r(j)r}r(hX1Jailhouse AM57xx support rebased to v0.10 versionrhjhhhjh}r(h]h]h]h]h]uhK9h]rhX1Jailhouse AM57xx support rebased to v0.10 versionrr}r(hjhjubaubj)r}r (hUh}r (h]h]h]h]h]uhjh]r j)r }r (hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXHAdded shared memory region between Linux, hypervisor, and inmate consolerh}r(h]h]h]h]h]uhj h]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhK6h]rhXHAdded shared memory region between Linux, hypervisor, and inmate consolerr}r(hjhjubaubahjubj)r}r(hXgStartup code of the inmate library enables MMU. An inmate has to initialize its MMU table by itself. h}r(h]h]h]h]h]uhj h]rh)r }r!(hXdStartup code of the inmate library enables MMU. An inmate has to initialize its MMU table by itself.r"hjhhhhh}r#(h]h]h]h]h]uhK7h]r$hXdStartup code of the inmate library enables MMU. An inmate has to initialize its MMU table by itself.r%r&}r'(hj"hj ubaubahjubehjubahjubeubahjubaubeubeubeubh)r(}r)(hUhhhhhhh}r*(h]h]h]h]r+hah]r,h0auhKhj6hhhhh}r?(h]h]h]h]h]uhK?hhh]r@hXProcessor SDK 05.03rArB}rC(hj>hj<ubaubj)rD}rE(hUhj6hhhjh}rF(jX-h]h]h]h]h]uhKAhhh]rGj)rH}rI(hX:This release is backwards compatible with 05.02 release. hjDhhhjh}rJ(h]h]h]h]h]uhNhhh]rKh)rL}rM(hX8This release is backwards compatible with 05.02 release.rNhjHhhhhh}rO(h]h]h]h]h]uhKAh]rPhX8This release is backwards compatible with 05.02 release.rQrR}rS(hjNhjLubaubaubaubeubh)rT}rU(hUhj(hhhhh}rV(h]h]h]h]rWhwah]rXhauhKEhhh]rY(h)rZ}r[(hXProcessor SDK 05.02r\hjThhhhh}r](h]h]h]h]h]uhKEhhh]r^hXProcessor SDK 05.02r_r`}ra(hj\hjZubaubj)rb}rc(hUhjThhhjh}rd(jX-h]h]h]h]h]uhKGhhh]rej)rf}rg(hXoThe minimum SD card size is now 16GB when creating an SD card with the default images for Processor SDK Linux. hjbhhhjh}rh(h]h]h]h]h]uhNhhh]rih)rj}rk(hXnThe minimum SD card size is now 16GB when creating an SD card with the default images for Processor SDK Linux.rlhjfhhhhh}rm(h]h]h]h]h]uhKGh]rnhXnThe minimum SD card size is now 16GB when creating an SD card with the default images for Processor SDK Linux.rorp}rq(hjlhjjubaubaubaubh)rr}rs(hXMulticast Filtering MaskrthjThhhhh}ru(h]h]h]h]h]uhKJhhh]rvhXMulticast Filtering Maskrwrx}ry(hjthjrubaubj)rz}r{(hUhjThhhjh}r|(jX*h]h]h]h]h]uhKKhhh]r}j)r~}r(hXThe parameter for setting a multicast filtering mask is now 'pruss_port_mc_mask' instead of 'pruss_mc_mask' because support was added to enable per port multicast filtering for Dual EMAC. hjzhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXThe parameter for setting a multicast filtering mask is now 'pruss_port_mc_mask' instead of 'pruss_mc_mask' because support was added to enable per port multicast filtering for Dual EMAC.rhj~hhhhh}r(h]h]h]h]h]uhKKh]rhXThe parameter for setting a multicast filtering mask is now 'pruss_port_mc_mask' instead of 'pruss_mc_mask' because support was added to enable per port multicast filtering for Dual EMAC.rr}r(hjhjubaubaubaubh)r}r(hXip link commandrhjThhhhh}r(h]h]h]h]h]uhKNhhh]rhXip link commandrr}r(hjhjubaubj)r}r(hUhjThhhjh}r(jX*h]h]h]h]h]uhKOhhh]rj)r}r(hXTip link parameter for setting up VLAN tag for HSR/PRP, sv_cfi is renamed to sv_dei. hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXSip link parameter for setting up VLAN tag for HSR/PRP, sv_cfi is renamed to sv_dei.rhjhhhhh}r(h]h]h]h]h]uhKOh]rhXSip link parameter for setting up VLAN tag for HSR/PRP, sv_cfi is renamed to sv_dei.rr}r(hjhjubaubaubaubeubh)r}r(hUhj(hhhhh}r(h]h]h]h]rhzah]rh auhKRhhh]r(h)r}r(hXProcessor SDK 05.01rhjhhhhh}r(h]h]h]h]h]uhKRhhh]rhXProcessor SDK 05.01rr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhKThhh]rj)r}r(hXSIntroduced AM65x as a new platform. Please refer to release notes for more details hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXRIntroduced AM65x as a new platform. Please refer to release notes for more detailsrhjhhhhh}r(h]h]h]h]h]uhKTh]rhXRIntroduced AM65x as a new platform. Please refer to release notes for more detailsrr}r(hjhjubaubaubaubh)r}r(hX PRUETH Driverrhjhhhhh}r(h]h]h]h]h]uhKWhhh]rhX PRUETH Driverrr}r(hjhjubaubh)r}r(hX$**1. debugfs file path has changed**rhjhhhhh}r(h]h]h]h]h]uhKXhhh]rcdocutils.nodes strong r)r}r(hjh}r(h]h]h]h]h]uhjh]rhX 1. debugfs file path has changedrr}r(hUhjubahUstrongrubaubh)r}r(hXThe path for debugfs file has changed to include the PRU-ICSS ID as there could be upto two instances of offloaded hsr/prp prueth driver and so has to distictly identify which instance the debugfs file refers to.rhjhhhhh}r(h]h]h]h]h]uhKZhhh]rhXThe path for debugfs file has changed to include the PRU-ICSS ID as there could be upto two instances of offloaded hsr/prp prueth driver and so has to distictly identify which instance the debugfs file refers to.rr}r(hjhjubaubh)r}r(hX.For example, the path for hsr/prp changed fromrhjhhhhh}r(h]h]h]h]h]uhK\hhh]rhX.For example, the path for hsr/prp changed fromrr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhK^hhh]rj)r}r(hX$/sys/kernel/debug/prueth-/ hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX#/sys/kernel/debug/prueth-/rhjhhhhh}r(h]h]h]h]h]uhK^h]rhX#/sys/kernel/debug/prueth-/rr}r(hjhjubaubaubaubcdocutils.nodes block_quote r)r}r(hUhjhhhU block_quoterh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXtorhjhhhhh}r(h]h]h]h]h]uhK`h]rhXtorr}r(hjhjubaubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhKbhhh]rj)r}r (hX)/sys/kernel/debug/prueth--/ hjhhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX(/sys/kernel/debug/prueth--/rhjhhhhh}r(h]h]h]h]h]uhKbh]rhX(/sys/kernel/debug/prueth--/rr}r(hjhj ubaubaubaubh)r}r(hXCWhere ID is the PRU-ICSS ID as described in the HSR/PRP User Guide.rhjhhhhh}r(h]h]h]h]h]uhKdhhh]rhXCWhere ID is the PRU-ICSS ID as described in the HSR/PRP User Guide.rr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhKfhhh]r(j)r }r!(hXRFor HSR on PRU-ICSS2 of AM571x, path is changed to /sys/kernel/debug/prueth-hsr-2/r"hjhhhjh}r#(h]h]h]h]h]uhNhhh]r$h)r%}r&(hj"hj hhhhh}r'(h]h]h]h]h]uhKfh]r(hXRFor HSR on PRU-ICSS2 of AM571x, path is changed to /sys/kernel/debug/prueth-hsr-2/r)r*}r+(hj"hj%ubaubaubj)r,}r-(hXRFor HSR on PRU-ICSS1 of AM571x, path is changed to /sys/kernel/debug/prueth-hsr-1/r.hjhhhjh}r/(h]h]h]h]h]uhNhhh]r0h)r1}r2(hj.hj,hhhhh}r3(h]h]h]h]h]uhKgh]r4hXRFor HSR on PRU-ICSS1 of AM571x, path is changed to /sys/kernel/debug/prueth-hsr-1/r5r6}r7(hj.hj1ubaubaubj)r8}r9(hXOFor PRP on PRU-ICSS2 of AM571x, path is changed /sys/kernel/debug/prueth-prp-2/r:hjhhhjh}r;(h]h]h]h]h]uhNhhh]r<h)r=}r>(hj:hj8hhhhh}r?(h]h]h]h]h]uhKhh]r@hXOFor PRP on PRU-ICSS2 of AM571x, path is changed /sys/kernel/debug/prueth-prp-2/rArB}rC(hj:hj=ubaubaubj)rD}rE(hXSfor PRP on PRU-ICSS1 of AM571x, path is changed to /sys/kernel/debug/prueth-prp-1/ hjhhhjh}rF(h]h]h]h]h]uhNhhh]rGh)rH}rI(hXRfor PRP on PRU-ICSS1 of AM571x, path is changed to /sys/kernel/debug/prueth-prp-1/rJhjDhhhhh}rK(h]h]h]h]h]uhKih]rLhXRfor PRP on PRU-ICSS1 of AM571x, path is changed to /sys/kernel/debug/prueth-prp-1/rMrN}rO(hjJhjHubaubaubeubh)rP}rQ(hXAll of the existing debugfs files except prp_emac_mode have moved to the new location. prp_emac_mode is now changed to sysfs file as decribed in the below section. The files are not writeable anymore as it is meant only for showing debug information. The write functions are moved to the upper layer HSR/PRP driver and implemented though proc entries. See the Linux HSR/PRP driver section for more details.rRhjhhhhh}rS(h]h]h]h]h]uhKkhhh]rThXAll of the existing debugfs files except prp_emac_mode have moved to the new location. prp_emac_mode is now changed to sysfs file as decribed in the below section. The files are not writeable anymore as it is meant only for showing debug information. The write functions are moved to the upper layer HSR/PRP driver and implemented though proc entries. See the Linux HSR/PRP driver section for more details.rUrV}rW(hjRhjPubaubh)rX}rY(hX"**2. sysfs file path has changed**rZhjhhhhh}r[(h]h]h]h]h]uhKmhhh]r\j)r]}r^(hjZh}r_(h]h]h]h]h]uhjXh]r`hX2. sysfs file path has changedrarb}rc(hUhj]ubahjubaubh)rd}re(hX/The path for sysfs files have also changed fromrfhjhhhhh}rg(h]h]h]h]h]uhKohhh]rhhX/The path for sysfs files have also changed fromrirj}rk(hjfhjdubaubj)rl}rm(hUhjhhhjh}rn(jX-h]h]h]h]h]uhKqhhh]roj)rp}rq(hX*/sys/devices/platform/pruss_eth/eth2/ hjlhhhjh}rr(h]h]h]h]h]uhNhhh]rsh)rt}ru(hX)/sys/devices/platform/pruss_eth/eth2/rvhjphhhhh}rw(h]h]h]h]h]uhKqh]rxhX)/sys/devices/platform/pruss_eth/eth2/ryrz}r{(hjvhjtubaubaubaubj)r|}r}(hUhjhhhjh}r~(h]h]h]h]h]uhNhhh]rh)r}r(hXtorhj|hhhhh}r(h]h]h]h]h]uhKsh]rhXtorr}r(hjhjubaubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhKuhhh]rj)r}r(hX./sys/devices/platform/pruss_eth/net/eth2/ hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX-/sys/devices/platform/pruss_eth/net/eth2/rhjhhhhh}r(h]h]h]h]h]uhKuh]rhX-/sys/devices/platform/pruss_eth/net/eth2/rr}r(hjhjubaubaubaubh)r}r(hX;Where ID is the PRU-ICSS ID as described in the User Guide.rhjhhhhh}r(h]h]h]h]h]uhKwhhh]rhX;Where ID is the PRU-ICSS ID as described in the User Guide.rr}r(hjhjubaubh)r}r(hX5For example, nsp_credit sysfs file is now accessed atrhjhhhhh}r(h]h]h]h]h]uhKyhhh]rhX5For example, nsp_credit sysfs file is now accessed atrr}r(hjhjubaubj)r}r(hUhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX4/sys/devices/platform/pruss2_eth/net/eth2/nsp_creditrhjhhhhh}r(h]h]h]h]h]uhK{h]rhX4/sys/devices/platform/pruss2_eth/net/eth2/nsp_creditrr}r(hjhjubaubaubh)r}r(hXprp_emac_mode file is atrhjhhhhh}r(h]h]h]h]h]uhK}hhh]rhXprp_emac_mode file is atrr}r(hjhjubaubj)r}r(hUhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX7/sys/devices/platform/pruss2_eth/net/eth2/prp_emac_moderhjhhhhh}r(h]h]h]h]h]uhKh]rhX7/sys/devices/platform/pruss2_eth/net/eth2/prp_emac_moderr}r(hjhjubaubaubh)r}r(hXLinux HSR/PRP Driverrhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXLinux HSR/PRP Driverrr}r(hjhjubaubh)r}r(hX$**1. debugfs file path has changed**rhjhhhhh}r(h]h]h]h]h]uhKhhh]rj)r}r(hjh}r(h]h]h]h]h]uhjh]rhX 1. debugfs file path has changedrr}r(hUhjubahjubaubh)r}r(hXThe debugfs file directory created by the driver now uses the interface name so that multiple instances of the device can co-exist and each will have its own unique path names.rhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXThe debugfs file directory created by the driver now uses the interface name so that multiple instances of the device can co-exist and each will have its own unique path names.rr}r(hjhjubaubh)r}r(hXPath is now changed fromrhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXPath is now changed fromrr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhKhhh]rj)r}r(hX/sys/kernel/debug// hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX/sys/kernel/debug//rhjhhhhh}r(h]h]h]h]h]uhKh]rhX/sys/kernel/debug//rr}r(hjhjubaubaubaubj)r}r(hUhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXtorhjhhhhh}r(h]h]h]h]h]uhKh]rhXtorr}r(hjhjubaubaubj)r}r (hUhjhhhjh}r (jX-h]h]h]h]h]uhKhhh]r j)r }r (hX/sys/kernel/debug// hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX/sys/kernel/debug//rhj hhhhh}r(h]h]h]h]h]uhKh]rhX/sys/kernel/debug//rr}r(hjhjubaubaubaubh)r}r(hXVFor example, if hsr interface name is hsr0, the path will be - /sys/kernel/debug/hsr0/rhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXVFor example, if hsr interface name is hsr0, the path will be - /sys/kernel/debug/hsr0/rr}r(hjhjubaubh)r }r!(hX Write functions are now supported through proc entries. So similar functions are removed from debugfs. See below section for details of proc entries. stats file is renamed to lre_info which shows SV frame tx count along with additional debug information about the LRE.r"hjhhhhh}r#(h]h]h]h]h]uhKhhh]r$hX Write functions are now supported through proc entries. So similar functions are removed from debugfs. See below section for details of proc entries. stats file is renamed to lre_info which shows SV frame tx count along with additional debug information about the LRE.r%r&}r'(hj"hj ubaubh)r(}r)(hX**2. proc file paths**r*hjhhhhh}r+(h]h]h]h]h]uhKhhh]r,j)r-}r.(hj*h}r/(h]h]h]h]h]uhj(h]r0hX2. proc file pathsr1r2}r3(hUhj-ubahjubaubh)r4}r5(hXFollowing commands can be used for updating values at the prueth offloaded device which was earlier supported through debugfs files at the prueth device.r6hjhhhhh}r7(h]h]h]h]h]uhKhhh]r8hXFollowing commands can be used for updating values at the prueth offloaded device which was earlier supported through debugfs files at the prueth device.r9r:}r;(hj6hj4ubaubj)r<}r=(hUhjhhhjh}r>(jX-h]h]h]h]h]uhKhhh]r?(j)r@}rA(hXW/proc//clear-nt - Replaces /sys/kernel/debug/prueth-/node_table_clearrBhj<hhhjh}rC(h]h]h]h]h]uhNhhh]rDh)rE}rF(hjBhj@hhhhh}rG(h]h]h]h]h]uhKh]rHhXW/proc//clear-nt - Replaces /sys/kernel/debug/prueth-/node_table_clearrIrJ}rK(hjBhjEubaubaubj)rL}rM(hXO/proc//hsr-mode - Replaces /sys/kernel/debug/prueth-/hsr_moderNhj<hhhjh}rO(h]h]h]h]h]uhNhhh]rPh)rQ}rR(hjNhjLhhhhh}rS(h]h]h]h]h]uhKh]rThXO/proc//hsr-mode - Replaces /sys/kernel/debug/prueth-/hsr_moderUrV}rW(hjNhjQubaubaubj)rX}rY(hX\/proc//dlrmt - Replaces /sys/kernel/debug/prueth-/dup_list_reside_max_timerZhj<hhhjh}r[(h]h]h]h]h]uhNhhh]r\h)r]}r^(hjZhjXhhhhh}r_(h]h]h]h]h]uhKh]r`hX\/proc//dlrmt - Replaces /sys/kernel/debug/prueth-/dup_list_reside_max_timerarb}rc(hjZhj]ubaubaubj)rd}re(hXX/proc//dd-mode - Replaces /sys/kernel/debug/prueth-/duplicate_discardrfhj<hhhjh}rg(h]h]h]h]h]uhNhhh]rhh)ri}rj(hjfhjdhhhhh}rk(h]h]h]h]h]uhKh]rlhXX/proc//dd-mode - Replaces /sys/kernel/debug/prueth-/duplicate_discardrmrn}ro(hjfhjiubaubaubj)rp}rq(hXS/proc//prp-tr - Replaces /sys/kernel/debug/prueth/transparent_reception hj<hhhjh}rr(h]h]h]h]h]uhNhhh]rsh)rt}ru(hXQ/proc//prp-tr - Replaces /sys/kernel/debug/prueth/transparent_receptionrvhjphhhhh}rw(h]h]h]h]h]uhKh]rxhXQ/proc//prp-tr - Replaces /sys/kernel/debug/prueth/transparent_receptionryrz}r{(hjvhjtubaubaubeubeubh)r|}r}(hUhj(hhhhh}r~(h]h]h]h]rhyah]rhauhKhhh]r(h)r}r(hXProcessor SDK 05.00rhj|hhhhh}r(h]h]h]h]h]uhKhhh]rhXProcessor SDK 05.00rr}r(hjhjubaubj)r}r(hUhj|hhhjh}r(jX-h]h]h]h]h]uhKhhh]r(j)r}r(hXjThis is the first release for 2018 LTS (Kernel: 4.14, U-boot: 2018.01, gcc: 7.2.1 and Yocto: 2.4 (rocko)).rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXjThis is the first release for 2018 LTS (Kernel: 4.14, U-boot: 2018.01, gcc: 7.2.1 and Yocto: 2.4 (rocko)).rr}r(hjhjubaubaubj)r}r(hXCWith Yocto migration, several open source components (Qt, Wayland, Weston, GStreamer, iPerf, etc.) are all upgraded. For the exact versions of the new components, please refer to the Software Manifest., and for any migration issues, refer to the corresponding component's release notes, and Processor SDK Known Issues list.hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXCWith Yocto migration, several open source components (Qt, Wayland, Weston, GStreamer, iPerf, etc.) are all upgraded. For the exact versions of the new components, please refer to the Software Manifest., and for any migration issues, refer to the corresponding component's release notes, and Processor SDK Known Issues list.rhjhhhhh}r(h]h]h]h]h]uhKh]rhXCWith Yocto migration, several open source components (Qt, Wayland, Weston, GStreamer, iPerf, etc.) are all upgraded. For the exact versions of the new components, please refer to the Software Manifest., and for any migration issues, refer to the corresponding component's release notes, and Processor SDK Known Issues list.rr}r(hjhjubaubaubj)r}r(hXEFollowing are major compatability changes for TI drivers, components.rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXEFollowing are major compatability changes for TI drivers, components.rr}r(hjhjubaubaubj)r}r(hXTIPC - Remoteproc core - RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigs - The RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types. - Two new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteproc - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels. - PRUSS remoteproc - The PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node. - Client user API has changed to acquire and use a PRU core - Keystone_remoteproc - The "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc" - The "ti,sci-id" property for K2G DSP nodes is also dropped. - The keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings. - Userspace - New IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changeshjhNhjh}r(h]h]h]h]h]uhNhhh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hX@IPC - Remoteproc core - RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigs - The RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types. - Two new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteproc - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels. - PRUSS remoteproc - The PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node. - Client user API has changed to acquire and use a PRU core - Keystone_remoteproc - The "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc" - The "ti,sci-id" property for K2G DSP nodes is also dropped. - The keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings. - Userspace - New IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changeshjhhhjh}r(h]h]h]h]h]uhKh]r(j)r}r(hXIPCrhjhhhjh}r(h]h]h]h]h]uhKh]rhXIPCrr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXDRemoteproc core - RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigs - The RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types. - Two new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteproc - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels.h}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hX8Remoteproc core - RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigs - The RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types. - Two new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteproc - Error recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels.hjhhhjh}r(h]h]h]h]h]uhKh]r(j)r}r(hXRemoteproc corerhjhhhjh}r(h]h]h]h]h]uhKh]rhXRemoteproc corerr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hX}RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigsrh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX}RPMSG_VIRTIO is no longer automatically selected by remoteproc platform drivers, has to be enabled specifically in defconfigsrr}r(hjhjubaubahjubj)r}r(hXThe RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types.rh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXThe RSC_CUSTOM remoteproc custom resource type has been replaced with two new RSC_PRELOAD_VENDOR and RSC_POSTLOAD_VENDOR resource types.rr}r(hjhjubaubahjubj)r}r(hXTwo new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteprocrh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r (h]h]h]h]h]uhKh]r hXTwo new debugfs variables "resource_table" and "carveout_memories" are added to print the resource table and carveout memories used by a remoteprocr r }r (hjhjubaubahjubj)r}r(hXError recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels.rh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXError recovery with virtio-rpmsg-bus stack is broken on Upstream vanilla 4.14 kernel. Error recovery is supported only on TI kernels.rr}r(hjhjubaubahjubehjubahjubeubahjubahjubj)r}r(hXPRUSS remoteproc - The PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node. - Client user API has changed to acquire and use a PRU coreh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r (h]h]h]h]h]uhjh]r!j)r"}r#(hXPRUSS remoteproc - The PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node. - Client user API has changed to acquire and use a PRU corehjhhhjh}r$(h]h]h]h]h]uhKh]r%(j)r&}r'(hXPRUSS remoteprocr(hj"hhhjh}r)(h]h]h]h]h]uhKh]r*hXPRUSS remoteprocr+r,}r-(hj(hj&ubaubj)r.}r/(hUh}r0(h]h]h]h]h]uhj"h]r1j)r2}r3(hUh}r4(jX-h]h]h]h]h]uhj.h]r5(j)r6}r7(hXYThe PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node.h}r8(h]h]h]h]h]uhj2h]r9j)r:}r;(hUh}r<(h]h]h]h]h]uhj6h]r=j)r>}r?(hXGThe PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibility - New child nodes are added to represent the CFG, IEP and MII_RT sub-modules. - Default firmware names are moved from driver to DT - Client users will require a new "prus" mandatory property instead of the previous "pruss" property - "ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes. - "label" property is dropped from PRU nodes - "interrupts" and "interrupt-names" properties were moved from INTC node to their parent node.hj:hhhjh}r@(h]h]h]h]h]uhKh]rA(j)rB}rC(hXdThe PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibilityrDhj>hhhjh}rE(h]h]h]h]h]uhKh]rFhXdThe PRUSS remoteproc bindings have been revised significantly to improve scalability and flexibilityrGrH}rI(hjDhjBubaubj)rJ}rK(hUh}rL(h]h]h]h]h]uhj>h]rMj)rN}rO(hUh}rP(jX-h]h]h]h]h]uhjJh]rQ(j)rR}rS(hXKNew child nodes are added to represent the CFG, IEP and MII_RT sub-modules.rTh}rU(h]h]h]h]h]uhjNh]rVh)rW}rX(hjThjRhhhhh}rY(h]h]h]h]h]uhKh]rZhXKNew child nodes are added to represent the CFG, IEP and MII_RT sub-modules.r[r\}r](hjThjWubaubahjubj)r^}r_(hX2Default firmware names are moved from driver to DTr`h}ra(h]h]h]h]h]uhjNh]rbh)rc}rd(hj`hj^hhhhh}re(h]h]h]h]h]uhKh]rfhX2Default firmware names are moved from driver to DTrgrh}ri(hj`hjcubaubahjubj)rj}rk(hXbClient users will require a new "prus" mandatory property instead of the previous "pruss" propertyrlh}rm(h]h]h]h]h]uhjNh]rnh)ro}rp(hjlhjjhhhhh}rq(h]h]h]h]h]uhKh]rrhXbClient users will require a new "prus" mandatory property instead of the previous "pruss" propertyrsrt}ru(hjlhjoubaubahjubj)rv}rw(hXk"ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes.rxh}ry(h]h]h]h]h]uhjNh]rzh)r{}r|(hjxhjvhhhhh}r}(h]h]h]h]h]uhKh]r~hXk"ti,pruss-gp-mux-sel" property is removed from PRU nodes and added as an optional property to client nodes.rr}r(hjxhj{ubaubahjubj)r}r(hX*"label" property is dropped from PRU nodesrh}r(h]h]h]h]h]uhjNh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX*"label" property is dropped from PRU nodesrr}r(hjhjubaubahjubj)r}r(hX]"interrupts" and "interrupt-names" properties were moved from INTC node to their parent node.rh}r(h]h]h]h]h]uhjNh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX]"interrupts" and "interrupt-names" properties were moved from INTC node to their parent node.rr}r(hjhjubaubahjubehjubahjubeubahjubahjubj)r}r(hX9Client user API has changed to acquire and use a PRU corerh}r(h]h]h]h]h]uhj2h]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX9Client user API has changed to acquire and use a PRU corerr}r(hjhjubaubahjubehjubahjubeubahjubahjubj)r}r(hXmKeystone_remoteproc - The "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc" - The "ti,sci-id" property for K2G DSP nodes is also dropped. - The keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings.h}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXdKeystone_remoteproc - The "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc" - The "ti,sci-id" property for K2G DSP nodes is also dropped. - The keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings.hjhhhjh}r(h]h]h]h]h]uhKh]r(j)r}r(hXKeystone_remoteprocrhjhhhjh}r(h]h]h]h]h]uhKh]rhXKeystone_remoteprocrr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXvThe "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc"rh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXvThe "label" binding property is dropped from the driver bindings, and is replaced with an alias using the stem "rproc"rr}r(hjhjubaubahjubj)r}r(hX;The "ti,sci-id" property for K2G DSP nodes is also dropped.rh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX;The "ti,sci-id" property for K2G DSP nodes is also dropped.rr}r(hjhjubaubahjubj)r}r(hXThe keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings.rh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhXThe keystone-dsp-mem driver is converted to a regular module from a platform driver, so the dspmem nodes are dropped. The module uses revised bindings.rr}r(hjhjubaubahjubehjubahjubeubahjubahjubj)r}r(hXUserspace - New IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changesh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hXUserspace - New IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changeshjhhhjh}r(h]h]h]h]h]uhKh]r(j)r}r(hX Userspacerhjhhhjh}r(h]h]h]h]h]uhKh]rhX Userspacerr}r(hjhjubaubj)r}r(hUh}r(h]h]h]h]h]uhjh]rj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]rj)r}r(hXNew IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changesrh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhhhhh}r (h]h]h]h]h]uhKh]r hXNew IPC and CMEM releases are needed to use with 4.14 kernel due to difference in AF_RPMSG family number and other kernel API changesr r }r (hjhjubaubahjubahjubahjubeubahjubahjubehjubahjubeubahjubaubj)r}r(hX iperf2 is now replaced by iperf3rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhhhhh}r(h]h]h]h]h]uhKh]rhX iperf2 is now replaced by iperf3rr}r(hjhjubaubaubj)r}r(hX4Keystone-2: PA/PA2 is not supported in NetCP driver.rhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r (hjhjhhhhh}r!(h]h]h]h]h]uhKh]r"hX4Keystone-2: PA/PA2 is not supported in NetCP driver.r#r$}r%(hjhjubaubaubj)r&}r'(hX!Keystone-2: NWAL is not supportedr(hjhhhjh}r)(h]h]h]h]h]uhNhhh]r*h)r+}r,(hj(hj&hhhhh}r-(h]h]h]h]h]uhKh]r.hX!Keystone-2: NWAL is not supportedr/r0}r1(hj(hj+ubaubaubj)r2}r3(hXBMMC: AM57x uses sdhci-omap.c driver instead of omap_hsmmc.c driverr4hjhhhjh}r5(h]h]h]h]h]uhNhhh]r6h)r7}r8(hj4hj2hhhhh}r9(h]h]h]h]h]uhKh]r:hXBMMC: AM57x uses sdhci-omap.c driver instead of omap_hsmmc.c driverr;r<}r=(hj4hj7ubaubaubj)r>}r?(hXPCIe: The way in which PCIe endpoint is configured has changed. More details can be found from `PCIe End Point Driver `__.r@hjhhhjh}rA(h]h]h]h]h]uhNhhh]rBh)rC}rD(hj@hj>hhhhh}rE(h]h]h]h]h]uhKh]rF(hX_PCIe: The way in which PCIe endpoint is configured has changed. More details can be found from rGrH}rI(hX_PCIe: The way in which PCIe endpoint is configured has changed. More details can be found from hjCubjg)rJ}rK(hX}`PCIe End Point Driver `__h}rL(UnameXPCIe End Point DriverjkXaFoundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.html#pcie-end-point-4-14-kernelh]h]h]h]h]uhjCh]rMhXPCIe End Point DriverrNrO}rP(hUhjJubahjpubhX.rQ}rR(hX.hjCubeubaubj)rS}rT(hXAM335x ICE v2: A new DT file (am335x-ice-v2-prueth.dts) is added to support PRUSS Ethernet ports. The following configurations are supported. hjhhhjh}rU(h]h]h]h]h]uhNhhh]rVh)rW}rX(hXAM335x ICE v2: A new DT file (am335x-ice-v2-prueth.dts) is added to support PRUSS Ethernet ports. The following configurations are supported.rYhjShhhhh}rZ(h]h]h]h]h]uhKh]r[hXAM335x ICE v2: A new DT file (am335x-ice-v2-prueth.dts) is added to support PRUSS Ethernet ports. The following configurations are supported.r\r]}r^(hjYhjWubaubaubeubcdocutils.nodes literal_block r_)r`}ra(hXam335x-ice-v2.dts: Both ports are CPSW controlled (Board jumpers J18 and J19 at RMII). am335x-ice-v2-prueth.dts: Both ports are PRUSS controlled (Board jumpers J18 and J19 at MII). Also note that there is an update to the u-boot env script to select DTB file name based on jumper settings. So user needs to do following when upgrading to the latest u-boot from this release: >env default -a >saveenv >resethj|hhhU literal_blockrbh}rc(hhh]h]h]h]h]uhKhhh]rdhXam335x-ice-v2.dts: Both ports are CPSW controlled (Board jumpers J18 and J19 at RMII). am335x-ice-v2-prueth.dts: Both ports are PRUSS controlled (Board jumpers J18 and J19 at MII). Also note that there is an update to the u-boot env script to select DTB file name based on jumper settings. So user needs to do following when upgrading to the latest u-boot from this release: >env default -a >saveenv >resetrerf}rg(hUhj`ubaubeubeubh)rh}ri(hUhhhhhhh}rj(h]h]h]h]rkhmah]rlhauhKhhh]rm(h)rn}ro(hXProcessor SDK 04.xx Releasesrphjhhhhhh}rq(h]h]h]h]h]uhKhhh]rrhXProcessor SDK 04.xx Releasesrsrt}ru(hjphjnubaubh)rv}rw(hUhjhhhhhh}rx(h]h]h]h]ryhah]rzhGauhKhhh]r{(h)r|}r}(hXProcessor SDK 04.03r~hjvhhhhh}r(h]h]h]h]h]uhKhhh]rhXProcessor SDK 04.03rr}r(hj~hj|ubaubj)r}r(hUhjvhhhjh}r(jX-h]h]h]h]h]uhKhhh]r(j)r}r(hXAdded am572x-idk-pps.dts and am571x-idk-pps.dts which are extensions of the am572x-idk.dts abd an571x-idk.dts respectively. The new DTS enables the PPS IO pins (sync/latch) and PTP BC bindings at the modified AM572x-idk and AM571x-idks, where the USB/LCD Display are disabledhjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXAdded am572x-idk-pps.dts and am571x-idk-pps.dts which are extensions of the am572x-idk.dts abd an571x-idk.dts respectively. The new DTS enables the PPS IO pins (sync/latch) and PTP BC bindings at the modified AM572x-idk and AM571x-idks, where the USB/LCD Display are disabledrhjhhhhh}r(h]h]h]h]h]uhKh]rhXAdded am572x-idk-pps.dts and am571x-idk-pps.dts which are extensions of the am572x-idk.dts abd an571x-idk.dts respectively. The new DTS enables the PPS IO pins (sync/latch) and PTP BC bindings at the modified AM572x-idk and AM571x-idks, where the USB/LCD Display are disabledrr}r(hjhjubaubaubj)r}r(hXCamera support for AM572x GPEVM is not in the default DTB.Use am57xx-evm*-cam-mt9t111.dtb for mt9t111 camera, and am57xx-evm*-cam-ov10635.dtb for ov10635 camerahjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXCamera support for AM572x GPEVM is not in the default DTB.Use am57xx-evm*-cam-mt9t111.dtb for mt9t111 camera, and am57xx-evm*-cam-ov10635.dtb for ov10635 camerarhjhhhhh}r(h]h]h]h]h]uhKh]rhXCamera support for AM572x GPEVM is not in the default DTB.Use am57xx-evm*-cam-mt9t111.dtb for mt9t111 camera, and am57xx-evm*-cam-ov10635.dtb for ov10635 camerarr}r(hjhjubaubaubj)r}r(hXProcessor SDK documentation is now created from reStructuredText sources using Sphinx, and hosted on software-dl.ti.com instead of processors wikihjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXProcessor SDK documentation is now created from reStructuredText sources using Sphinx, and hosted on software-dl.ti.com instead of processors wikirhjhhhhh}r(h]h]h]h]h]uhKh]rhXProcessor SDK documentation is now created from reStructuredText sources using Sphinx, and hosted on software-dl.ti.com instead of processors wikirr}r(hjhjubaubaubj)r}r(hXFor AM57xx, with the addition of new components in the filesystem, the minimum SD-card size is 8 GB (4 GB SD cards no longer work).hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXFor AM57xx, with the addition of new components in the filesystem, the minimum SD-card size is 8 GB (4 GB SD cards no longer work).rhjhhhhh}r(h]h]h]h]h]uhKh]rhXFor AM57xx, with the addition of new components in the filesystem, the minimum SD-card size is 8 GB (4 GB SD cards no longer work).rr}r(hjhjubaubaubj)r}r(hX-For am57xx devices, the location of the saved U-Boot environment has moved from the external SD card to eMMC. Because of this change, the state of the U-Boot environment can no longer be guaranteed on a newly created SD card. The uEnv.txt file located on the boot partition of the SD card contains the logic to compensate for this change. Upon the initial boot, the environment will be reset to the default, and the empty file ".psdk_setup" will be created on the boot partition. Subsequent boots will detect this file and bypass resetting the environment. hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX,For am57xx devices, the location of the saved U-Boot environment has moved from the external SD card to eMMC. Because of this change, the state of the U-Boot environment can no longer be guaranteed on a newly created SD card. The uEnv.txt file located on the boot partition of the SD card contains the logic to compensate for this change. Upon the initial boot, the environment will be reset to the default, and the empty file ".psdk_setup" will be created on the boot partition. Subsequent boots will detect this file and bypass resetting the environment.rhjhhhhh}r(h]h]h]h]h]uhKh]rhX,For am57xx devices, the location of the saved U-Boot environment has moved from the external SD card to eMMC. Because of this change, the state of the U-Boot environment can no longer be guaranteed on a newly created SD card. The uEnv.txt file located on the boot partition of the SD card contains the logic to compensate for this change. Upon the initial boot, the environment will be reset to the default, and the empty file ".psdk_setup" will be created on the boot partition. Subsequent boots will detect this file and bypass resetting the environment.rr}r(hjhjubaubaubeubeubh)r}r(hUhjhhhhhh}r(h]h]h]h]rhah]rhHauhKhhh]r(h)r}r(hXProcessor SDK 04.02rhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXProcessor SDK 04.02rr}r(hjhjubaubh)r}r(hXLinuxrhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXLinuxrr}r(hjhjubaubh)r}r(hX PRUETH Driverrhjhhhhh}r(h]rhah]h]h]h]rh3auhNhhh]rhX PRUETH Driverrr}r(hjhjubaubcdocutils.nodes line_block r)r}r(hUhjhhhU line_blockrh}r(h]h]h]h]h]uhKhhh]rcdocutils.nodes line r)r}r(hXThe module parameter syntax has changed from "prueth.pruss1\_ethtype" and "prueth.pruss2\_ethtype" in older release to "ti\_prueth.pruss1\_ethtype" and "ti\_prueth.pruss2\_ethtype".UindentrKhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXThe module parameter syntax has changed from "prueth.pruss1_ethtype" and "prueth.pruss2_ethtype" in older release to "ti_prueth.pruss1_ethtype" and "ti_prueth.pruss2_ethtype".rr}r(hXThe module parameter syntax has changed from "prueth.pruss1\_ethtype" and "prueth.pruss2\_ethtype" in older release to "ti\_prueth.pruss1\_ethtype" and "ti\_prueth.pruss2\_ethtype".hjubaubaubj)r}r(hUhjhhhjh}r(h]h]h]h]h]uhKhhh]rj)r}r(hUjKhjhhhhh}r(h]h]h]h]h]uhKhhh]ubaubeubh)r}r(hUhjhhhhhh}r(h]h]h]h]rhah]rhEauhKhhh]r(h)r}r(hXProcessor SDK 04.01rhjhhhhh}r(h]h]h]h]h]uhKhhh]rhXProcessor SDK 04.01rr}r(hjhjubaubh)r}r (hXIPCr hjhhhhh}r (h]r h`ah]h]h]h]r hauhNhhh]rhXIPCrr}r(hj hjubaubh)r}r(hXPRUSS remoteprocrhjhhhhh}r(h]rhah]h]h]h]rhQauhNhhh]rhXPRUSS remoteprocrr}r(hjhjubaubj)r}r(hUhjhhhjh}r(jX-h]h]h]h]h]uhMhhh]r(j)r }r!(hXPRUs are no longer automatically booted (remoteproc 'auto\_boot' is set to false) by remoteproc core. A PRU has to be booted either by PRU Client Drivers or a PRU applications in userspace. The kernel-space boot is triggered using the rproc\_boot() kernel API, and the user-space applications can use the sysfs to start and stop the corresponding remoteproc. Please see Documentation/ABI/testing/sysfs-class-remoteproc file in kernel for sysfs usage details.hjhhhjh}r"(h]h]h]h]h]uhNhhh]r#h)r$}r%(hXPRUs are no longer automatically booted (remoteproc 'auto\_boot' is set to false) by remoteproc core. A PRU has to be booted either by PRU Client Drivers or a PRU applications in userspace. The kernel-space boot is triggered using the rproc\_boot() kernel API, and the user-space applications can use the sysfs to start and stop the corresponding remoteproc. Please see Documentation/ABI/testing/sysfs-class-remoteproc file in kernel for sysfs usage details.hj hhhhh}r&(h]h]h]h]h]uhMh]r'hXPRUs are no longer automatically booted (remoteproc 'auto_boot' is set to false) by remoteproc core. A PRU has to be booted either by PRU Client Drivers or a PRU applications in userspace. The kernel-space boot is triggered using the rproc_boot() kernel API, and the user-space applications can use the sysfs to start and stop the corresponding remoteproc. Please see Documentation/ABI/testing/sysfs-class-remoteproc file in kernel for sysfs usage details.r(r)}r*(hXPRUs are no longer automatically booted (remoteproc 'auto\_boot' is set to false) by remoteproc core. A PRU has to be booted either by PRU Client Drivers or a PRU applications in userspace. The kernel-space boot is triggered using the rproc\_boot() kernel API, and the user-space applications can use the sysfs to start and stop the corresponding remoteproc. Please see Documentation/ABI/testing/sysfs-class-remoteproc file in kernel for sysfs usage details.hj$ubaubaubj)r+}r,(hXPRU remoteproc driver no longer configures the PRU Ethernet firmwares automatically using board-machine compatibles. The needed firmware names are configured by the PRU Ethernet driver now using the rproc\_set\_firmware() function.hjhhhjh}r-(h]h]h]h]h]uhNhhh]r.h)r/}r0(hXPRU remoteproc driver no longer configures the PRU Ethernet firmwares automatically using board-machine compatibles. The needed firmware names are configured by the PRU Ethernet driver now using the rproc\_set\_firmware() function.hj+hhhhh}r1(h]h]h]h]h]uhM h]r2hXPRU remoteproc driver no longer configures the PRU Ethernet firmwares automatically using board-machine compatibles. The needed firmware names are configured by the PRU Ethernet driver now using the rproc_set_firmware() function.r3r4}r5(hXPRU remoteproc driver no longer configures the PRU Ethernet firmwares automatically using board-machine compatibles. The needed firmware names are configured by the PRU Ethernet driver now using the rproc\_set\_firmware() function.hj/ubaubaubj)r6}r7(hXUserspace PRU applications have to make sure to unload any existing PRU client drivers using a specific PRU, and set their firmware using sysfs before starting and using a PRU hjhhhjh}r8(h]h]h]h]h]uhNhhh]r9h)r:}r;(hXUserspace PRU applications have to make sure to unload any existing PRU client drivers using a specific PRU, and set their firmware using sysfs before starting and using a PRUr<hj6hhhhh}r=(h]h]h]h]h]uhMh]r>hXUserspace PRU applications have to make sure to unload any existing PRU client drivers using a specific PRU, and set their firmware using sysfs before starting and using a PRUr?r@}rA(hj<hj:ubaubaubeubj)rB}rC(hUhjhhhjh}rD(h]h]h]h]h]uhMhhh]rEj)rF}rG(hUjKhjBhhhhh}rH(h]h]h]h]h]uhKhhh]ubaubeubh)rI}rJ(hUhjhhhhhh}rK(h]h]h]h]rLhah]rMhFauhMhhh]rN(h)rO}rP(hXProcessor SDK 04.00rQhjIhhhhh}rR(h]h]h]h]h]uhMhhh]rShXProcessor SDK 04.00rTrU}rV(hjQhjOubaubj)rW}rX(hUhjIhhhjh}rY(jX-h]h]h]h]h]uhMhhh]rZj)r[}r\(hXThis is the first release for 2017 LTS (Kernel: 4.9, U-boot: 2017.01, gcc: 6.2.1 and Yocto: 2.2 (morty)), with following major changes. hjWhhhjh}r](h]h]h]h]h]uhNhhh]r^h)r_}r`(hXThis is the first release for 2017 LTS (Kernel: 4.9, U-boot: 2017.01, gcc: 6.2.1 and Yocto: 2.2 (morty)), with following major changes.rahj[hhhhh}rb(h]h]h]h]h]uhMh]rchXThis is the first release for 2017 LTS (Kernel: 4.9, U-boot: 2017.01, gcc: 6.2.1 and Yocto: 2.2 (morty)), with following major changes.rdre}rf(hjahj_ubaubaubaubh)rg}rh(hXIPCrihjIhhhhh}rj(h]rkhah]h]h]h]rlhNauhNhhh]rmhXIPCrnro}rp(hjihjgubaubh)rq}rr(hX remoteprocrshjIhhhhh}rt(h]h]h]h]h]uhMhhh]ruhX remoteprocrvrw}rx(hjshjqubaubj)ry}rz(hUhjIhhhjh}r{(jX-h]h]h]h]h]uhMhhh]r|(j)r}}r~(hXThe debugfs 'state' variable is replaced with a sysfs 'state' variable accepting 'start' and 'stop' to boot and shutdown a remote processor from userspacehjyhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXThe debugfs 'state' variable is replaced with a sysfs 'state' variable accepting 'start' and 'stop' to boot and shutdown a remote processor from userspacerhj}hhhhh}r(h]h]h]h]h]uhMh]rhXThe debugfs 'state' variable is replaced with a sysfs 'state' variable accepting 'start' and 'stop' to boot and shutdown a remote processor from userspacerr}r(hjhjubaubaubj)r}r(hXA new sysfs variable 'firmware' is also added to set a new firmware. remoteprocs need to be in stopped state before a firmware can be set. New firmwares still need to reside in /lib/firmwarehjyhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXA new sysfs variable 'firmware' is also added to set a new firmware. remoteprocs need to be in stopped state before a firmware can be set. New firmwares still need to reside in /lib/firmwarerhjhhhhh}r(h]h]h]h]h]uhM"h]rhXA new sysfs variable 'firmware' is also added to set a new firmware. remoteprocs need to be in stopped state before a firmware can be set. New firmwares still need to reside in /lib/firmwarerr}r(hjhjubaubaubj)r}r(hXBooting a remote processor is now triggered by the insertion of the respective remoteproc platform driver. On 4.4, with virtio-rpmsg enabled firmwares, this only happened when both the remoteproc platform driver and virtio\_rpmsg\_bus module were installed.hjyhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXBooting a remote processor is now triggered by the insertion of the respective remoteproc platform driver. On 4.4, with virtio-rpmsg enabled firmwares, this only happened when both the remoteproc platform driver and virtio\_rpmsg\_bus module were installed.hjhhhhh}r(h]h]h]h]h]uhM%h]rhXBooting a remote processor is now triggered by the insertion of the respective remoteproc platform driver. On 4.4, with virtio-rpmsg enabled firmwares, this only happened when both the remoteproc platform driver and virtio_rpmsg_bus module were installed.rr}r(hXBooting a remote processor is now triggered by the insertion of the respective remoteproc platform driver. On 4.4, with virtio-rpmsg enabled firmwares, this only happened when both the remoteproc platform driver and virtio\_rpmsg\_bus module were installed.hjubaubaubj)r}r(hXUpstream 4.9 remoteproc and rpmsg cores are not suitable for TI platforms. A minimum of 4.10-rc4 (or the required remoteproc/rpmsg patches from 4.10-rc4) is needed if porting TI remoteproc drivers onto upstream. hjyhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXUpstream 4.9 remoteproc and rpmsg cores are not suitable for TI platforms. A minimum of 4.10-rc4 (or the required remoteproc/rpmsg patches from 4.10-rc4) is needed if porting TI remoteproc drivers onto upstream.rhjhhhhh}r(h]h]h]h]h]uhM)h]rhXUpstream 4.9 remoteproc and rpmsg cores are not suitable for TI platforms. A minimum of 4.10-rc4 (or the required remoteproc/rpmsg patches from 4.10-rc4) is needed if porting TI remoteproc drivers onto upstream.rr}r(hjhjubaubaubeubh)r}r(hXrpmsgrhjIhhhhh}r(h]h]h]h]h]uhM/hhh]rhXrpmsgrr}r(hjhjubaubj)r}r(hUhjIhhhjh}r(jX-h]h]h]h]h]uhM0hhh]r(j)r}r(hXvvirtio\_rpmsg\_bus module split into a 'rpmsg\_core' and virtio-rpmsg transport specific 'virtio\_rpmsg\_bus' modules.hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXvvirtio\_rpmsg\_bus module split into a 'rpmsg\_core' and virtio-rpmsg transport specific 'virtio\_rpmsg\_bus' modules.hjhhhhh}r(h]h]h]h]h]uhM0h]rhXqvirtio_rpmsg_bus module split into a 'rpmsg_core' and virtio-rpmsg transport specific 'virtio_rpmsg_bus' modules.rr}r(hXvvirtio\_rpmsg\_bus module split into a 'rpmsg\_core' and virtio-rpmsg transport specific 'virtio\_rpmsg\_bus' modules.hjubaubaubj)r}r(hXRemoval of virtio\_rpmsg\_bus no longer stops a remote processor and should be avoided if a remote processor is running. \* If removed and installed again, the rpmsg communication devices will not be reprobed. hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXRemoval of virtio\_rpmsg\_bus no longer stops a remote processor and should be avoided if a remote processor is running. \* If removed and installed again, the rpmsg communication devices will not be reprobed.hjhhhhh}r(h]h]h]h]h]uhM2h]rhXRemoval of virtio_rpmsg_bus no longer stops a remote processor and should be avoided if a remote processor is running. * If removed and installed again, the rpmsg communication devices will not be reprobed.rr}r(hXRemoval of virtio\_rpmsg\_bus no longer stops a remote processor and should be avoided if a remote processor is running. \* If removed and installed again, the rpmsg communication devices will not be reprobed.hjubaubaubeubh)r}r(hXKeystone\_remoteprochjIhhhhh}r(h]rhgah]h]h]h]rh auhNhhh]rhXKeystone_remoteprocrr}r(hXKeystone\_remoteprochjubaubj)r}r(hUhjIhhhjh}r(jX-h]h]h]h]h]uhM:hhh]r(j)r}r(hXA new 'label' binding property is now mandatory. It will have the string names for the DSPs in the format "dsp" (eg: dsp0, dsp7 etc)hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXA new 'label' binding property is now mandatory. It will have the string names for the DSPs in the format "dsp" (eg: dsp0, dsp7 etc)rhjhhhhh}r(h]h]h]h]h]uhM:h]rhXA new 'label' binding property is now mandatory. It will have the string names for the DSPs in the format "dsp" (eg: dsp0, dsp7 etc)rr}r(hjhjubaubaubj)r}r(hXK2G DSP nodes will require a new "ti,sci-id" property, and a different value for "power-domains" property (this is generic to all K2G devices) hjhhhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXK2G DSP nodes will require a new "ti,sci-id" property, and a different value for "power-domains" property (this is generic to all K2G devices)rhjhhhhh}r(h]h]h]h]h]uhM<h]rhXK2G DSP nodes will require a new "ti,sci-id" property, and a different value for "power-domains" property (this is generic to all K2G devices)rr}r(hjhjubaubaubeubh)r}r(hXPRUSS remoteprocrhjIhhhhh}r(h]rhah]h]h]h]rh-auhNhhh]rhXPRUSS remoteprocrr}r(hjhjubaubj)r}r(hUhjIhhhjh}r(jX-h]h]h]h]h]uhMChhh]r (j)r }r (hXThe AM437x specific am437x\_pruss\_wrapper module has been replaced with a generic pruss\_soc\_bus module, and is required to be installed on all SoCs.hjhhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXThe AM437x specific am437x\_pruss\_wrapper module has been replaced with a generic pruss\_soc\_bus module, and is required to be installed on all SoCs.hj hhhhh}r (h]h]h]h]h]uhMCh]r hXThe AM437x specific am437x_pruss_wrapper module has been replaced with a generic pruss_soc_bus module, and is required to be installed on all SoCs.r r }r (hXThe AM437x specific am437x\_pruss\_wrapper module has been replaced with a generic pruss\_soc\_bus module, and is required to be installed on all SoCs.hj ubaubaubj)r }r (hX.New compatibles on AM335x and AM437x SoCs - The previous 'am3352-xxx' and 'am4372-xxx' have been replaced with a 'am3356-xxx' and 'am4376-xxx' compatibles since PRUSS are not present on AM3352 and AM4372 SoCs. The PRU nodes are also not enabled by default in base 'am33xx.dtsi' and 'am4372.dtsi' files.hjhhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX.New compatibles on AM335x and AM437x SoCs - The previous 'am3352-xxx' and 'am4372-xxx' have been replaced with a 'am3356-xxx' and 'am4376-xxx' compatibles since PRUSS are not present on AM3352 and AM4372 SoCs. The PRU nodes are also not enabled by default in base 'am33xx.dtsi' and 'am4372.dtsi' files.r hj hhhhh}r (h]h]h]h]h]uhMFh]r hX.New compatibles on AM335x and AM437x SoCs - The previous 'am3352-xxx' and 'am4372-xxx' have been replaced with a 'am3356-xxx' and 'am4376-xxx' compatibles since PRUSS are not present on AM3352 and AM4372 SoCs. The PRU nodes are also not enabled by default in base 'am33xx.dtsi' and 'am4372.dtsi' files.r r }r (hj hj ubaubaubj)r }r (hXNew device hierarchy structure - The PRUSS node hierarchy from 4.4 is moved one-level down under a new parent pruss\_soc\_bus node. hjhhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXNew device hierarchy structure - The PRUSS node hierarchy from 4.4 is moved one-level down under a new parent pruss\_soc\_bus node.hj hhhhh}r (h]h]h]h]h]uhMKh]r hXNew device hierarchy structure - The PRUSS node hierarchy from 4.4 is moved one-level down under a new parent pruss_soc_bus node.r r! }r" (hXNew device hierarchy structure - The PRUSS node hierarchy from 4.4 is moved one-level down under a new parent pruss\_soc\_bus node.hj ubaubaubeubh)r# }r$ (hXCPSW CPDMA Descriptor Usager% hjIhhhhh}r& (h]r' hiah]h]h]h]r( hauhNhhh]r) hXCPSW CPDMA Descriptor Usager* r+ }r, (hj% hj# ubaubh)r- }r. (hXThere is a notable change in how to place cpsw cpdma descriptors in DDR and configure descs number: **TI K4.4** device tree property was used "descs\_pool\_size" - descs\_pool\_size : total number of CPDMA CPPI descriptors to be used for both ingress/egress packets processing. if not specified the default value 256 will be used which will allow to place descriptors pool into the internal CPPI RAM.hjIhhhhh}r/ (h]h]h]h]h]uhMQhhh]r0 (hXdThere is a notable change in how to place cpsw cpdma descriptors in DDR and configure descs number: r1 r2 }r3 (hXdThere is a notable change in how to place cpsw cpdma descriptors in DDR and configure descs number: hj- ubj)r4 }r5 (hX **TI K4.4**h}r6 (h]h]h]h]h]uhj- h]r7 hXTI K4.4r8 r9 }r: (hUhj4 ubahjubhX device tree property was used "descs_pool_size" - descs_pool_size : total number of CPDMA CPPI descriptors to be used for both ingress/egress packets processing. if not specified the default value 256 will be used which will allow to place descriptors pool into the internal CPPI RAM.r; r< }r= (hX! device tree property was used "descs\_pool\_size" - descs\_pool\_size : total number of CPDMA CPPI descriptors to be used for both ingress/egress packets processing. if not specified the default value 256 will be used which will allow to place descriptors pool into the internal CPPI RAM.hj- ubeubh)r> }r? (hX**New approach** http://processors.wiki.ti.com/index.php/Linux_Core_CPSW_User%27s_Guide#Configure_number_of_TX.2FRX_descriptorshjIhhhhh}r@ (h]h]h]h]h]uhMXhhh]rA (j)rB }rC (hX**New approach**h}rD (h]h]h]h]h]uhj> h]rE hX New approachrF rG }rH (hUhjB ubahjubhX rI }rJ (hX hj> ubjg)rK }rL (hXnhttp://processors.wiki.ti.com/index.php/Linux_Core_CPSW_User%27s_Guide#Configure_number_of_TX.2FRX_descriptorsrM h}rN (UrefurijM h]h]h]h]h]uhj> h]rO hXnhttp://processors.wiki.ti.com/index.php/Linux_Core_CPSW_User%27s_Guide#Configure_number_of_TX.2FRX_descriptorsrP rQ }rR (hUhjK ubahjpubeubh)rS }rT (hX PCI ENDPOINTrU hjIhhhhh}rV (h]rW hah]h]h]h]rX h.auhNhhh]rY hX PCI ENDPOINTrZ r[ }r\ (hjU hjS ubaubh)r] }r^ (hXThe usage of 'pci-ep' configfs directory to configure PCI Endpoint has been changed in accordance with upstream review comments. Please see http://processors.wiki.ti.com/index.php/Linux_Core_PCIe_EP_User%27s_Guide#4.9_Kernel, for additional detailshjIhhhhh}r_ (h]h]h]h]h]uhM^hhh]r` (hXThe usage of 'pci-ep' configfs directory to configure PCI Endpoint has been changed in accordance with upstream review comments. Please see ra rb }rc (hXThe usage of 'pci-ep' configfs directory to configure PCI Endpoint has been changed in accordance with upstream review comments. Please see hj] ubjg)rd }re (hXThttp://processors.wiki.ti.com/index.php/Linux_Core_PCIe_EP_User%27s_Guide#4.9_Kernelrf h}rg (Urefurijf h]h]h]h]h]uhj] h]rh hXThttp://processors.wiki.ti.com/index.php/Linux_Core_PCIe_EP_User%27s_Guide#4.9_Kernelri rj }rk (hUhjd ubahjpubhX, for additional detailsrl rm }rn (hX, for additional detailshj] ubeubh)ro }rp (hXDisplayrq hjIhhhhh}rr (h]rs hah]h]h]h]rt hTauhNhhh]ru hXDisplayrv rw }rx (hjq hjo ubaubh)ry }rz (hXfbdev is only set up for the primary display, instead of all displays. This results in the secondary displays to be left disabled by the kernel, until an userspace application enables the displays.r{ hjIhhhhh}r| (h]h]h]h]h]uhMfhhh]r} hXfbdev is only set up for the primary display, instead of all displays. This results in the secondary displays to be left disabled by the kernel, until an userspace application enables the displays.r~ r }r (hj{ hjy ubaubh)r }r (hXU-Boot RNDIS bootr hjIhhhhh}r (h]r hah]h]h]h]r h/auhNhhh]r hXU-Boot RNDIS bootr r }r (hj hj ubaubh)r }r (hX AM335x USB client (RNDIS) boot and Ethernet boot modes are now supported using default defconfig (am335x\_evm\_defconfig). Similarly AM437x USB client (RNDIS) boot is now supported by am43xx\_evm\_defconfig. Separate defconfigs for above boot modes no longer exist.hjIhhhhh}r (h]h]h]h]h]uhMmhhh]r hXAM335x USB client (RNDIS) boot and Ethernet boot modes are now supported using default defconfig (am335x_evm_defconfig). Similarly AM437x USB client (RNDIS) boot is now supported by am43xx_evm_defconfig. Separate defconfigs for above boot modes no longer exist.r r }r (hX AM335x USB client (RNDIS) boot and Ethernet boot modes are now supported using default defconfig (am335x\_evm\_defconfig). Similarly AM437x USB client (RNDIS) boot is now supported by am43xx\_evm\_defconfig. Separate defconfigs for above boot modes no longer exist.hj ubaubh)r }r (hXKeystone-2 featuresr hjIhhhhh}r (h]r hah]h]h]h]r h%auhNhhh]r hXKeystone-2 featuresr r }r (hj hj ubaubh)r }r (hX1The following features are not ported to 2017 LTSr hjIhhhhh}r (h]h]h]h]h]uhMuhhh]r hX1The following features are not ported to 2017 LTSr r }r (hj hj ubaubj)r }r (hUhjIhhhjh}r (jX-h]h]h]h]h]uhMwhhh]r (j)r }r (hXSRIO Kernel driverr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMwh]r hXSRIO Kernel driverr r }r (hj hj ubaubaubj)r }r (hX 10G Ubootr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMxh]r hX 10G Ubootr r }r (hj hj ubaubaubj)r }r (hXIPSec sideband and inflow moder hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMyh]r hXIPSec sideband and inflow moder r }r (hj hj ubaubaubj)r }r (hXQoS hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXQoSr hj hhhhh}r (h]h]h]h]h]uhMzh]r hXQoSr r }r (hj hj ubaubaubeubj)r }r (hUhjIhhhjh}r (h]h]h]h]h]uhM|hhh]r j)r }r (hUjKhj hhhhh}r (h]h]h]h]h]uhKhhh]ubaubeubeubh)r }r (hUhhhhhhh}r (h]h]h]h]r h{ah]r h!auhMhhh]r (h)r }r (hXProcessor SDK 03.xx Releasesr hj hhhhh}r (h]h]h]h]h]uhMhhh]r hXProcessor SDK 03.xx Releasesr r }r (hj hj ubaubh)r }r (hUhj hhhhh}r (h]h]h]h]r hah]r hPauhMhhh]r (h)r }r (hXProcessor SDK 03.03r hj hhhhh}r (h]h]h]h]h]uhMhhh]r hXProcessor SDK 03.03r r }r (hj hj ubaubj)r }r (hUhj hhhjh}r (jX-h]h]h]h]h]uhMhhh]r (j)r }r (hXqHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrixhj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXqHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrixr hj hhhhh}r (h]h]h]h]h]uhMh]r hXqHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrixr r }r (hj hj ubaubaubj)r }r (hXSee the `Release Notes `__ for full list of modifications. hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXSee the `Release Notes `__ for full list of modifications.hj hhhhh}r (h]h]h]h]h]uhMh]r (hXSee the r r }r (hXSee the hj ubjg)r }r (hX]`Release Notes `__h}r (UnameX Release NotesjkXIhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Release_Notesh]h]h]h]h]uhj h]r hX Release Notesr r }r (hUhj ubahjpubhX for full list of modifications.r r }r (hX for full list of modifications.hj ubeubaubeubj)r }r! (hUhj hhhjh}r" (h]h]h]h]h]uhMhhh]r# j)r$ }r% (hUjKhj hhhhh}r& (h]h]h]h]h]uhKhhh]ubaubeubh)r' }r( (hUhj hhhhh}r) (h]h]h]h]r* hah]r+ hDauhMhhh]r, (h)r- }r. (hXProcessor SDK 03.02r/ hj' hhhhh}r0 (h]h]h]h]h]uhMhhh]r1 hXProcessor SDK 03.02r2 r3 }r4 (hj/ hj- ubaubj)r5 }r6 (hUhj' hhhjh}r7 (jX-h]h]h]h]h]uhMhhh]r8 (j)r9 }r: (hX@The QT QPA eglfs\_kms, which supports multiple screens, has been enabled and used as the default eglfs platform plugin. For more information, see `QT and Graphics Migration `__hj5 hhhjh}r; (h]h]h]h]h]uhNhhh]r< h)r= }r> (hX@The QT QPA eglfs\_kms, which supports multiple screens, has been enabled and used as the default eglfs platform plugin. For more information, see `QT and Graphics Migration `__hj9 hhhhh}r? (h]h]h]h]h]uhMh]r@ (hXThe QT QPA eglfs_kms, which supports multiple screens, has been enabled and used as the default eglfs platform plugin. For more information, see rA rB }rC (hXThe QT QPA eglfs\_kms, which supports multiple screens, has been enabled and used as the default eglfs platform plugin. For more information, see hj= ubjg)rD }rE (hX`QT and Graphics Migration `__h}rF (UnameXQT and Graphics MigrationjkXhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_Graphics_and_Display#Migration_Guide_from_Processor_SDK_3.1_to_3.x_for_AM3.2F4.2F5h]h]h]h]h]uhj= h]rG hXQT and Graphics MigrationrH rI }rJ (hUhjD ubahjpubeubaubj)rK }rL (hXbootmonitor now goes thru mkimage and as a result the load address changed. Users should manually execute following commands in their u-boot environment to properly install the secure monitor on k2 platforms: hj5 hhhjh}rM (h]h]h]h]h]uhNhhh]rN h)rO }rP (hXbootmonitor now goes thru mkimage and as a result the load address changed. Users should manually execute following commands in their u-boot environment to properly install the secure monitor on k2 platforms:rQ hjK hhhhh}rR (h]h]h]h]h]uhMh]rS hXbootmonitor now goes thru mkimage and as a result the load address changed. Users should manually execute following commands in their u-boot environment to properly install the secure monitor on k2 platforms:rT rU }rV (hjQ hjO ubaubaubeubj_)rW }rX (hXsetenv addr_mon 0xc08000 setenv addr_mon_mkimg 0xc07ffc0 setenv mon_size 0x1210 setenv sec_bm_install 'go ${addr_mon}4 0xc084000 ${mon_size}; mon_install ${addr_mon_mkimg}' run sec_bm_installhj' hhhjbh}rY (hhh]h]h]h]h]uhMhhh]rZ hXsetenv addr_mon 0xc08000 setenv addr_mon_mkimg 0xc07ffc0 setenv mon_size 0x1210 setenv sec_bm_install 'go ${addr_mon}4 0xc084000 ${mon_size}; mon_install ${addr_mon_mkimg}' run sec_bm_installr[ r\ }r] (hUhjW ubaubj)r^ }r_ (hUhj' hhhjh}r` (jX-h]h]h]h]h]uhMhhh]ra j)rb }rc (hXrHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrix hj^ hhhjh}rd (h]h]h]h]h]uhNhhh]re h)rf }rg (hXqHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrixrh hjb hhhhh}ri (h]h]h]h]h]uhMh]rj hXqHDMI-connected monitor no longer takes precedence over built-in LCD as a default graphics display for e.g. Matrixrk rl }rm (hjh hjf ubaubaubaubj)rn }ro (hUhj' hhhjh}rp (h]h]h]h]h]uhMhhh]rq j)rr }rs (hUjKhjn hhhhh}rt (h]h]h]h]h]uhKhhh]ubaubeubh)ru }rv (hUhj hhhhh}rw (h]h]h]h]rx hah]ry h,auhMhhh]rz (h)r{ }r| (hXProcessor SDK 03.01r} hju hhhhh}r~ (h]h]h]h]h]uhMhhh]r hXProcessor SDK 03.01r r }r (hj} hj{ ubaubj)r }r (hUhju hhhjh}r (jX-h]h]h]h]h]uhMhhh]r (j)r }r (hXDdefconfig\_builder is now used to generate working kernel defconfigsr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hXCdefconfig_builder is now used to generate working kernel defconfigsr r }r (hXDdefconfig\_builder is now used to generate working kernel defconfigshj ubaubaubj)r }r (hX(In K2 U-Boot, added multi slave support.r hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX(In K2 U-Boot, added multi slave support.r r }r (hj hj ubaubaubj)r }r (hXIn K2 Linux PA driver, added pre-classification support. So explicit lut rules for broadcast and multicast are removed and the same is achieved through this feature in PAhj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXIn K2 Linux PA driver, added pre-classification support. So explicit lut rules for broadcast and multicast are removed and the same is achieved through this feature in PAr hj hhhhh}r (h]h]h]h]h]uhMh]r hXIn K2 Linux PA driver, added pre-classification support. So explicit lut rules for broadcast and multicast are removed and the same is achieved through this feature in PAr r }r (hj hj ubaubaubj)r }r (hX10G Ethernet driver now supports auto configuration using MCU firmware (a.k.a 10G KR firmware). The firmware file name is ks2\_xgbe\_serdes\_mcu\_fw.bin which is available at the same location as other serdes firmwares.hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX10G Ethernet driver now supports auto configuration using MCU firmware (a.k.a 10G KR firmware). The firmware file name is ks2\_xgbe\_serdes\_mcu\_fw.bin which is available at the same location as other serdes firmwares.hj hhhhh}r (h]h]h]h]h]uhMh]r hX10G Ethernet driver now supports auto configuration using MCU firmware (a.k.a 10G KR firmware). The firmware file name is ks2_xgbe_serdes_mcu_fw.bin which is available at the same location as other serdes firmwares.r r }r (hX10G Ethernet driver now supports auto configuration using MCU firmware (a.k.a 10G KR firmware). The firmware file name is ks2\_xgbe\_serdes\_mcu\_fw.bin which is available at the same location as other serdes firmwares.hj ubaubaubj)r }r (hXThe current version of the serdes firmware is 03.03.00.02C and the same is not backward compatible with the firmware in the previous SDK release (03.00.00) hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXThe current version of the serdes firmware is 03.03.00.02C and the same is not backward compatible with the firmware in the previous SDK release (03.00.00)r hj hhhhh}r (h]h]h]h]h]uhMh]r hXThe current version of the serdes firmware is 03.03.00.02C and the same is not backward compatible with the firmware in the previous SDK release (03.00.00)r r }r (hj hj ubaubaubeubj)r }r (hUhju hhhjh}r (h]h]h]h]h]uhMhhh]r j)r }r (hUjKhj hhhhh}r (h]h]h]h]h]uhKhhh]ubaubeubh)r }r (hUhj hhhhh}r (h]h]h]h]r hah]r hMauhMhhh]r (h)r }r (hXProcessor SDK 03.00r hj hhhhh}r (h]h]h]h]h]uhMhhh]r hXProcessor SDK 03.00r r }r (hj hj ubaubj)r }r (hUhj hhhjh}r (jX-h]h]h]h]h]uhMhhh]r (j)r }r (hXOFirst 2016 LTS Release (Linux Kernel: 4.4, U-Boot: 2016.05, GCC 5.3, Yocto 2.1)hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXOFirst 2016 LTS Release (Linux Kernel: 4.4, U-Boot: 2016.05, GCC 5.3, Yocto 2.1)r hj hhhhh}r (h]h]h]h]h]uhMh]r hXOFirst 2016 LTS Release (Linux Kernel: 4.4, U-Boot: 2016.05, GCC 5.3, Yocto 2.1)r r }r (hj hj ubaubaubj)r }r (hX:Unified kernel configuration based on multi\_v7\_defconfigr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX8Unified kernel configuration based on multi_v7_defconfigr r }r (hX:Unified kernel configuration based on multi\_v7\_defconfighj ubaubaubj)r }r (hX@Migrated from SysVinit to systemd for user space initialization.r hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX@Migrated from SysVinit to systemd for user space initialization.r r }r (hj hj ubaubaubj)r }r (hX7U-Boot drivers now uses DT, but is transparent to usersr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX7U-Boot drivers now uses DT, but is transparent to usersr r }r (hj hj ubaubaubj)r }r (hX*The content of --sdk-arago-src-.tar.gz on the download page changed from sources to a fetcher script that obtains the sources. This is to efficiently share the sources between different platforms and OSes supported by Processor SDK. See the README inside the tar-ball for instructionshj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX*The content of --sdk-arago-src-.tar.gz on the download page changed from sources to a fetcher script that obtains the sources. This is to efficiently share the sources between different platforms and OSes supported by Processor SDK. See the README inside the tar-ball for instructionsr hj hhhhh}r (h]h]h]h]h]uhMh]r hX*The content of --sdk-arago-src-.tar.gz on the download page changed from sources to a fetcher script that obtains the sources. This is to efficiently share the sources between different platforms and OSes supported by Processor SDK. See the README inside the tar-ball for instructionsr r }r (hj hj ubaubaubj)r }r (hXBThis release adds support for RT Linux on AM335x ICE and K2G GPEVMr hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hXBThis release adds support for RT Linux on AM335x ICE and K2G GPEVMr r! }r" (hj hj ubaubaubj)r# }r$ (hXIn K2 U-Boot, multi slave support is currently missing. To use multiple interfaces, please disable CONFIG\_DM\_ET option in u-boot .config and build.hj hhhjh}r% (h]h]h]h]h]uhNhhh]r& h)r' }r( (hXIn K2 U-Boot, multi slave support is currently missing. To use multiple interfaces, please disable CONFIG\_DM\_ET option in u-boot .config and build.hj# hhhhh}r) (h]h]h]h]h]uhMh]r* hXIn K2 U-Boot, multi slave support is currently missing. To use multiple interfaces, please disable CONFIG_DM_ET option in u-boot .config and build.r+ r, }r- (hXIn K2 U-Boot, multi slave support is currently missing. To use multiple interfaces, please disable CONFIG\_DM\_ET option in u-boot .config and build.hj' ubaubaubj)r. }r/ (hX5See the Release Notes for full list of modifications.r0 hj hhhjh}r1 (h]h]h]h]h]uhNhhh]r2 h)r3 }r4 (hj0 hj. hhhhh}r5 (h]h]h]h]h]uhMh]r6 hX5See the Release Notes for full list of modifications.r7 r8 }r9 (hj0 hj3 ubaubaubj)r: }r; (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__. hj hhhjh}r< (h]h]h]h]h]uhNhhh]r= h)r> }r? (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__.hj: hhhhh}r@ (h]h]h]h]h]uhMh]rA (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see rB rC }rD (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see hj> ubjg)rE }rF (hX?`this migration page `__h}rG (UnameXthis migration pagejkX%MCSDK_to_Processor_SDK_Migration.htmlh]h]h]h]h]uhj> h]rH hXthis migration pagerI rJ }rK (hUhjE ubahjpubhX.rL }rM (hX.hj> ubeubaubeubj)rN }rO (hUhj hhhjh}rP (h]h]h]h]h]uhMhhh]rQ j)rR }rS (hUjKhjN hhhhh}rT (h]h]h]h]h]uhKhhh]ubaubeubeubh)rU }rV (hUhhhhhhh}rW (h]h]h]h]rX hah]rY hLauhMhhh]rZ (h)r[ }r\ (hXProcessor SDK 02.xx Releasesr] hjU hhhhh}r^ (h]h]h]h]h]uhMhhh]r_ hXProcessor SDK 02.xx Releasesr` ra }rb (hj] hj[ ubaubh)rc }rd (hUhjU hhhhh}re (h]h]h]h]rf hrah]rg hauhMhhh]rh (h)ri }rj (hXProcessor SDK 02.00.02rk hjc hhhhh}rl (h]h]h]h]h]uhMhhh]rm hXProcessor SDK 02.00.02rn ro }rp (hjk hji ubaubj)rq }rr (hUhjc hhhjh}rs (jX-h]h]h]h]h]uhMhhh]rt (j)ru }rv (hX=This release adds RT Linux support on AM335x, K2H/K, K2E, K2Lrw hjq hhhjh}rx (h]h]h]h]h]uhNhhh]ry h)rz }r{ (hjw hju hhhhh}r| (h]h]h]h]h]uhMh]r} hX=This release adds RT Linux support on AM335x, K2H/K, K2E, K2Lr~ r }r (hjw hjz ubaubaubj)r }r (hX,This release supports AM572x IDK and K2G EVMr hjq hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX,This release supports AM572x IDK and K2G EVMr r }r (hj hj ubaubaubj)r }r (hXuOpenCV now uses OpenCL under the hood, to offload compute tasks to C66x cores. This is transparent to the applicationhjq hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXuOpenCV now uses OpenCL under the hood, to offload compute tasks to C66x cores. This is transparent to the applicationr hj hhhhh}r (h]h]h]h]h]uhMh]r hXuOpenCV now uses OpenCL under the hood, to offload compute tasks to C66x cores. This is transparent to the applicationr r }r (hj hj ubaubaubj)r }r (hX The SGX driver for AM335x has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see `AM3 Graphics Migration `__hjq hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX The SGX driver for AM335x has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see `AM3 Graphics Migration `__hj hhhhh}r (h]h]h]h]h]uhMh]r (hXyThe SGX driver for AM335x has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see r r }r (hXyThe SGX driver for AM335x has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see hj ubjg)r }r (hX`AM3 Graphics Migration `__h}r (UnameXAM3 Graphics MigrationjkXhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_Graphics_and_Display#Migration_Guide_from_Processor_SDK_2.0.0_to_2.0.x_for_AM4h]h]h]h]h]uhj h]r hXAM3 Graphics Migrationr r }r (hUhj ubahjpubeubaubj)r }r (hXSee the `Release Notes `__ for full list of modifications.hjq hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXSee the `Release Notes `__ for full list of modifications.hj hhhhh}r (h]h]h]h]h]uhMh]r (hXSee the r r }r (hXSee the hj ubjg)r }r (hXn`Release Notes `__h}r (UnameX Release NotesjkXZhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Release_Notes#Release_02.00.02h]h]h]h]h]uhj h]r hX Release Notesr r }r (hUhj ubahjpubhX for full list of modifications.r r }r (hX for full list of modifications.hj ubeubaubj)r }r (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__. hjq hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__.hj hhhhh}r (h]h]h]h]h]uhMh]r (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see r r }r (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see hj ubjg)r }r (hX?`this migration page `__h}r (UnameXthis migration pagejkX%MCSDK_to_Processor_SDK_Migration.htmlh]h]h]h]h]uhj h]r hXthis migration pager r }r (hUhj ubahjpubhX.r }r (hX.hj ubeubaubeubj)r }r (hUhjc hhhjh}r (h]h]h]h]h]uhMhhh]r j)r }r (hUjKhj hhhhh}r (h]h]h]h]h]uhKhhh]ubaubeubh)r }r (hUhjU hhhhh}r (h]h]h]h]r hqah]r hauhMhhh]r (h)r }r (hXProcessor SDK 02.00.01r hj hhhhh}r (h]h]h]h]h]uhMhhh]r hXProcessor SDK 02.00.01r r }r (hj hj ubaubj)r }r (hUhj hhhjh}r (jX-h]h]h]h]h]uhMhhh]r (j)r }r (hXYThis release adds support for devices from the KeyStone architecture: K2E, K2H/K, and K2Lhj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXYThis release adds support for devices from the KeyStone architecture: K2E, K2H/K, and K2Lr hj hhhhh}r (h]h]h]h]h]uhMh]r hXYThis release adds support for devices from the KeyStone architecture: K2E, K2H/K, and K2Lr r }r (hj hj ubaubaubj)r }r (hXFThis release also supports RT Linux is supported on AM4 and AM5 devicehj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXFThis release also supports RT Linux is supported on AM4 and AM5 devicer hj hhhhh}r (h]h]h]h]h]uhMh]r hXFThis release also supports RT Linux is supported on AM4 and AM5 devicer r }r (hj hj ubaubaubj)r }r (hXThe SGX driver for AM4 has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see `AM4 Graphics Migration `__hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXThe SGX driver for AM4 has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see `AM4 Graphics Migration `__hj hhhhh}r (h]h]h]h]h]uhMh]r (hXvThe SGX driver for AM4 has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see r r }r (hXvThe SGX driver for AM4 has been enhanced to support DRM/WAYLAND based Multi-Window Display. For more information, see hj ubjg)r }r (hX`AM4 Graphics Migration `__h}r (UnameXAM4 Graphics MigrationjkXhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_Graphics_and_Display#Migration_Guide_from_Processor_SDK_2.0.0_to_2.0.x_for_AM4h]h]h]h]h]uhj h]r hXAM4 Graphics Migrationr r }r (hUhj ubahjpubeubaubj)r }r (hX=There is no migration impact to customers using AM3, and AM5.r hj hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hj hj hhhhh}r (h]h]h]h]h]uhMh]r hX=There is no migration impact to customers using AM3, and AM5.r r! }r" (hj hj ubaubaubj)r# }r$ (hXSee the `Release Notes `__ for full list of modifications.hj hhhjh}r% (h]h]h]h]h]uhNhhh]r& h)r' }r( (hXSee the `Release Notes `__ for full list of modifications.hj# hhhhh}r) (h]h]h]h]h]uhMh]r* (hXSee the r+ r, }r- (hXSee the hj' ubjg)r. }r/ (hXn`Release Notes `__h}r0 (UnameX Release NotesjkXZhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Release_Notes#Release_02.00.01h]h]h]h]h]uhj' h]r1 hX Release Notesr2 r3 }r4 (hUhj. ubahjpubhX for full list of modifications.r5 r6 }r7 (hX for full list of modifications.hj' ubeubaubj)r8 }r9 (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__. hj hhhjh}r: (h]h]h]h]h]uhNhhh]r; h)r< }r= (hXFor information on migrating from MCSDK (K2x) to Processor SDK, see `this migration page `__.hj8 hhhhh}r> (h]h]h]h]h]uhMh]r? (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see r@ rA }rB (hXDFor information on migrating from MCSDK (K2x) to Processor SDK, see hj< ubjg)rC }rD (hX?`this migration page `__h}rE (UnameXthis migration pagejkX%MCSDK_to_Processor_SDK_Migration.htmlh]h]h]h]h]uhj< h]rF hXthis migration pagerG rH }rI (hUhjC ubahjpubhX.rJ }rK (hX.hj< ubeubaubeubj)rL }rM (hUhj hhhjh}rN (h]h]h]h]h]uhMhhh]rO j)rP }rQ (hUjKhjL hhhhh}rR (h]h]h]h]h]uhKhhh]ubaubeubh)rS }rT (hUhjU hhhhh}rU (h]h]h]h]rV hpah]rW hauhMhhh]rX (h)rY }rZ (hXProcessor SDK 02.00.00r[ hjS hhhhh}r\ (h]h]h]h]h]uhMhhh]r] hXProcessor SDK 02.00.00r^ r_ }r` (hj[ hjY ubaubj)ra }rb (hUhjS hhhjh}rc (jX-h]h]h]h]h]uhMhhh]rd (j)re }rf (hX#This release adds support for AM57xrg hja hhhjh}rh (h]h]h]h]h]uhNhhh]ri h)rj }rk (hjg hje hhhhh}rl (h]h]h]h]h]uhMh]rm hX#This release adds support for AM57xrn ro }rp (hjg hjj ubaubaubj)rq }rr (hX3First 2015 LTS (Kernel 4.1, U-boot 2015.07) Releasers hja hhhjh}rt (h]h]h]h]h]uhNhhh]ru h)rv }rw (hjs hjq hhhhh}rx (h]h]h]h]h]uhMh]ry hX3First 2015 LTS (Kernel 4.1, U-boot 2015.07) Releaserz r{ }r| (hjs hjv ubaubaubj)r} }r~ (hXStarting this release, Processor SDK Installer is 64-bit, and installs only on 64-bit host machine. Support for 32-bit host is dropped as Linaro toolchain is available only for 64-bit machineshja hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXStarting this release, Processor SDK Installer is 64-bit, and installs only on 64-bit host machine. Support for 32-bit host is dropped as Linaro toolchain is available only for 64-bit machinesr hj} hhhhh}r (h]h]h]h]h]uhMh]r hXStarting this release, Processor SDK Installer is 64-bit, and installs only on 64-bit host machine. Support for 32-bit host is dropped as Linaro toolchain is available only for 64-bit machinesr r }r (hj hj ubaubaubj)r }r (hXdFor AM3, AM4, Graphics SDK is now obsolete and Graphics stack is integrated into Processor SDK, and supports null DRM based Full Window, with Front and Flip modes. For more information, see `Graphics Migration `__hja hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXdFor AM3, AM4, Graphics SDK is now obsolete and Graphics stack is integrated into Processor SDK, and supports null DRM based Full Window, with Front and Flip modes. For more information, see `Graphics Migration `__hj hhhhh}r (h]h]h]h]h]uhMh]r (hXFor AM3, AM4, Graphics SDK is now obsolete and Graphics stack is integrated into Processor SDK, and supports null DRM based Full Window, with Front and Flip modes. For more information, see r r }r (hXFor AM3, AM4, Graphics SDK is now obsolete and Graphics stack is integrated into Processor SDK, and supports null DRM based Full Window, with Front and Flip modes. For more information, see hj ubjg)r }r (hX`Graphics Migration `__h}r (UnameXGraphics MigrationjkXhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_Graphics_and_Display#Migration_Guide_from_Processor_SDK_1.x_to_2.x_for_AM3.2C_AM4h]h]h]h]h]uhj h]r hXGraphics Migrationr r }r (hUhj ubahjpubeubaubj)r }r (hXTEthernet performance degraded ~10% on am335x-evm due to move from preempt\_voluntaryhja hhhjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXTEthernet performance degraded ~10% on am335x-evm due to move from preempt\_voluntaryhj hhhhh}r (h]h]h]h]h]uhMh]r hXSEthernet performance degraded ~10% on am335x-evm due to move from preempt_voluntaryr r }r (hXTEthernet performance degraded ~10% on am335x-evm due to move from preempt\_voluntaryhj ubaubaubj)r }r (hXSee the `Release Notes `__ for full list of modifications. hja hX`internal padding after source/linux/Release_Specific/Processor_SDK_Linux_Migration_Guide.rst.incr hjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXSee the `Release Notes `__ for full list of modifications.hj hhhhh}r (h]h]h]h]h]uhMh]r (hXSee the r r }r (hXSee the hj ubjg)r }r (hX`Release Notes `__h}r (UnameX Release NotesjkXvhttp://processors.wiki.ti.com/index.php?title=Processor_SDK_Linux_Release_Notes%26oldid%3D207973&action=edit&redlink=1h]h]h]h]h]uhj h]r hX Release Notesr r }r (hUhj ubahjpubhX for full list of modifications.r r }r (hX for full list of modifications.hj ubeubaubeubh)r }r (hXHhttp://processors.wiki.ti.com/index.php/MCSDK_to_Processor_SDK_MigrationhjS hhXGsource/common/Release_Specific/MCSDK_to_Processor_SDK_Migration.rst.incr r }r bhhh}r (hhh]h]h]h]h]uhKhhh]r hXHhttp://processors.wiki.ti.com/index.php/MCSDK_to_Processor_SDK_Migrationr r }r (hUhj ubaubeubeubh)r }r (hUhhhj hhh}r (h]h]h]h]r hah]r hAauhKhhh]r (h)r }r (hX&MCSDK to Processor SDK Migration Guider hj hj hhh}r (h]h]h]h]h]uhKhhh]r hX&MCSDK to Processor SDK Migration Guider r }r (hj hj ubaubh)r }r (hX Introductionr hj hj hhh}r (h]h]h]h]h]uhKhhh]r hX Introductionr r }r (hj hj ubaubh)r }r (hXFor many years, the MCSDK has been a great way to get started with Embedded Software development on TI's KeyStone architecture processors (C66x, K2x). If you go by "what's in a name?", you can easily see the connection. The "MC" of MCSDK stands for Multi-Core and The "SDK" refers to Software Development Kit. The MCSDK encapsulated a collection of software elements and tools and was designed to provide a great starting point for developing embedded applications on ARM running Linux and C66x cores running TI-RTOS, on KeyStone processors. One of the goals of the MCSDK was to enable a developer to quickly explore and evaluate the possibilities as well as start development on a customized Linux/TI-RTOS software platform.r hj hj hhh}r (h]h]h]h]h]uhKhhh]r hXFor many years, the MCSDK has been a great way to get started with Embedded Software development on TI's KeyStone architecture processors (C66x, K2x). If you go by "what's in a name?", you can easily see the connection. The "MC" of MCSDK stands for Multi-Core and The "SDK" refers to Software Development Kit. The MCSDK encapsulated a collection of software elements and tools and was designed to provide a great starting point for developing embedded applications on ARM running Linux and C66x cores running TI-RTOS, on KeyStone processors. One of the goals of the MCSDK was to enable a developer to quickly explore and evaluate the possibilities as well as start development on a customized Linux/TI-RTOS software platform.r r }r (hj hj ubaubh)r }r (hXLike the Linux kernel itself, which evolves every 77 days or so with a new release, it's time for the MCSDK to evolve, without departing from it's heritage. TI has a rich offering of microprocessors from multicore ARMs to tiny, power-efficient DSPs, and different combinations of ARM, DSP, and specialized cores to provide the broad market a variety of solutions. Since many developers will touch several of these devices from project to project, it is beneficial to standardize the experience to maximize the benefit of learning. The limited time developers have in today's time-to-market driven environment is very important and shouldn't be wasted.r hj hj hhh}r (h]h]h]h]h]uhKhhh]r hXLike the Linux kernel itself, which evolves every 77 days or so with a new release, it's time for the MCSDK to evolve, without departing from it's heritage. TI has a rich offering of microprocessors from multicore ARMs to tiny, power-efficient DSPs, and different combinations of ARM, DSP, and specialized cores to provide the broad market a variety of solutions. Since many developers will touch several of these devices from project to project, it is beneficial to standardize the experience to maximize the benefit of learning. The limited time developers have in today's time-to-market driven environment is very important and shouldn't be wasted.r r }r (hj hj ubaubh)r }r (hXTo this end, the KeyStone devices will be actively supported in the Processor SDK, the unified SDK for TI processors. This allows suport for both C66x and K2x in the same SDK, as well as the other AMx processor. Each developer that uses the Processor SDK from project to project can leverage that experience and know with confidence what they can expect. The Processor SDK is more than a collection of components, the aim is that applications can switch processors with minimal modifications.r hj hj hhh}r (h]h]h]h]h]uhKhhh]r hXTo this end, the KeyStone devices will be actively supported in the Processor SDK, the unified SDK for TI processors. This allows suport for both C66x and K2x in the same SDK, as well as the other AMx processor. Each developer that uses the Processor SDK from project to project can leverage that experience and know with confidence what they can expect. The Processor SDK is more than a collection of components, the aim is that applications can switch processors with minimal modifications.r r }r (hj hj ubaubh)r }r (hX>Further, we are seeing different use cases for Linux and RTOS:r hj hj hhh}r (h]h]h]h]h]uhK'hhh]r hX>Further, we are seeing different use cases for Linux and RTOS:r r }r (hj hj ubaubj)r }r (hUhj hj hjh}r (jX-h]h]h]h]h]uhK)hhh]r (j)r }r (hX[A fully RTOS based solution with RTOS on Cortex-A cores in addition to the C66/M4 cores andhj hj hjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX[A fully RTOS based solution with RTOS on Cortex-A cores in addition to the C66/M4 cores andr hj hj hhh}r (h]h]h]h]h]uhK)h]r hX[A fully RTOS based solution with RTOS on Cortex-A cores in addition to the C66/M4 cores andr r }r (hj hj ubaubaubj)r }r (hX)Linux based solutions that need acceleration, but doesn't really need to get into the programming details of the non Cortex-A cores, and would just need open programming paradigms such as OpenCL, OpenGL, GStreamer to accelerate the Linux applications, leveraging TI's optimized libraries or codecshj hj hjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hX)Linux based solutions that need acceleration, but doesn't really need to get into the programming details of the non Cortex-A cores, and would just need open programming paradigms such as OpenCL, OpenGL, GStreamer to accelerate the Linux applications, leveraging TI's optimized libraries or codecsr hj hj hhh}r (h]h]h]h]h]uhK+h]r hX)Linux based solutions that need acceleration, but doesn't really need to get into the programming details of the non Cortex-A cores, and would just need open programming paradigms such as OpenCL, OpenGL, GStreamer to accelerate the Linux applications, leveraging TI's optimized libraries or codecsr r }r (hj hj ubaubaubj)r }r (hXWA heterogenous solution of Coretex-A cores running Linux and C66/M4 cores running RTOS hj hj hjh}r (h]h]h]h]h]uhNhhh]r h)r }r (hXVA heterogenous solution of Coretex-A cores running Linux and C66/M4 cores running RTOSr hj hj hhh}r (h]h]h]h]h]uhK0h]r hXVA heterogenous solution of Coretex-A cores running Linux and C66/M4 cores running RTOSr! r" }r# (hj hj ubaubaubeubh)r$ }r% (hX`To this end, the Processor SDK is split into Processor SDK for RTOS and Processor SDK for Linux.r& hj hj hhh}r' (h]h]h]h]h]uhK3hhh]r( hX`To this end, the Processor SDK is split into Processor SDK for RTOS and Processor SDK for Linux.r) r* }r+ (hj& hj$ ubaubh)r, }r- (hXTo further customize the experience for developers who typically work on one device we split the SDK to be a separate installer per device, per OS. In summary, the contents of MCSDK is now split into Processor SDK (Linux, RTOS) for K2H/K2K, K2E, and K2L. The devices without ARM processors, C665x and C667x, only support RTOS. With this background in place, let's dig into more specifics.r. hj hj hhh}r/ (h]h]h]h]h]uhK6hhh]r0 hXTo further customize the experience for developers who typically work on one device we split the SDK to be a separate installer per device, per OS. In summary, the contents of MCSDK is now split into Processor SDK (Linux, RTOS) for K2H/K2K, K2E, and K2L. The devices without ARM processors, C665x and C667x, only support RTOS. With this background in place, let's dig into more specifics.r1 r2 }r3 (hj. hj, ubaubh)r4 }r5 (hXmProcessor-SDK 2.0.1 adds support for KeyStone devices from previous SDKs that are no longer being maintained:r6 hj hj hhh}r7 (h]h]h]h]h]uhK=hhh]r8 hXmProcessor-SDK 2.0.1 adds support for KeyStone devices from previous SDKs that are no longer being maintained:r9 r: }r; (hj6 hj4 ubaubj)r< }r= (hUhj hj hjh}r> (jX-h]h]h]h]h]uhK@hhh]r? (j)r@ }rA (hX;**MCSDK**: K2H, K2K, K2E, K2L *(last release: MCSDK 3.1.4)*rB hj< hj hjh}rC (h]h]h]h]h]uhNhhh]rD h)rE }rF (hjB hj@ hj hhh}rG (h]h]h]h]h]uhK@h]rH (j)rI }rJ (hX **MCSDK**h}rK (h]h]h]h]h]uhjE h]rL hXMCSDKrM rN }rO (hUhjI ubahjubhX: K2H, K2K, K2E, K2L rP rQ }rR (hX: K2H, K2K, K2E, K2L hjE ubcdocutils.nodes emphasis rS )rT }rU (hX*(last release: MCSDK 3.1.4)*h}rV (h]h]h]h]h]uhjE h]rW hX(last release: MCSDK 3.1.4)rX rY }rZ (hUhjT ubahUemphasisr[ ubeubaubj)r\ }r] (hX@**BIOS-MCSDK**: C665x, C667x *(last release: BIOS-MCSDK 2.1.2)* hj< hj hjh}r^ (h]h]h]h]h]uhNhhh]r_ h)r` }ra (hX?**BIOS-MCSDK**: C665x, C667x *(last release: BIOS-MCSDK 2.1.2)*hj\ hj hhh}rb (h]h]h]h]h]uhKAh]rc (j)rd }re (hX**BIOS-MCSDK**h}rf (h]h]h]h]h]uhj` h]rg hX BIOS-MCSDKrh ri }rj (hUhjd ubahjubhX: C665x, C667x rk rl }rm (hX: C665x, C667x hj` ubjS )rn }ro (hX"*(last release: BIOS-MCSDK 2.1.2)*h}rp (h]h]h]h]h]uhj` h]rq hX (last release: BIOS-MCSDK 2.1.2)rr rs }rt (hUhjn ubahj[ ubeubaubeubh)ru }rv (hXcIf you are migrating from these SDKs, the notes below will highlight any changes that are required.rw hj hj hhh}rx (h]h]h]h]h]uhKChhh]ry hXcIf you are migrating from these SDKs, the notes below will highlight any changes that are required.rz r{ }r| (hjw hju ubaubj)r} }r~ (hUhj hj hjh}r (h]h]h]h]h]uhKFhhh]r j)r }r (hUjKhj} hj hhh}r (h]h]h]h]h]uhKhhh]ubaubh)r }r (hX Installationr hj hj hhh}r (h]r hah]h]h]h]r hCauhNhhh]r hX Installationr r }r (hj hj ubaubh)r }r (hXVAs with MCSDK, Processor SDK is also available as an installer on ti.com for download.r hj hj hhh}r (h]h]h]h]h]uhKKhhh]r hXVAs with MCSDK, Processor SDK is also available as an installer on ti.com for download.r r }r (hj hj ubaubh)r }r (hXTarget Machiner hj hj hhh}r (h]r hah]h]h]h]r h6auhNhhh]r hXTarget Machiner r }r (hj hj ubaubh)r }r (hXThe Processor SDK Linux installer is available only for host machines running Linux, where as the Processor SDK RTOS installer is available for both Windows and Linux host machines. Please note that the Processor SDK Linux Installer can be installed only on 64-bit host machines and the support for 32-bit machines is dropped, primarily due to the Linaro toolchain not supporting 32-bit anymore.r hj hj hhh}r (h]h]h]h]h]uhKQhhh]r hXThe Processor SDK Linux installer is available only for host machines running Linux, where as the Processor SDK RTOS installer is available for both Windows and Linux host machines. Please note that the Processor SDK Linux Installer can be installed only on 64-bit host machines and the support for 32-bit machines is dropped, primarily due to the Linaro toolchain not supporting 32-bit anymore.r r }r (hj hj ubaubh)r }r (hXInstall Packagesr hj hj hhh}r (h]r hdah]h]h]h]r h auhNhhh]r hXInstall Packagesr r }r (hj hj ubaubh)r }r (hXAs noted earlier, the installer is now available per device, per OS. If you work on multiple devices or work on both RTOS and Linux, you'd have to download multiple installers.r hj hj hhh}r (h]h]h]h]h]uhK[hhh]r hXAs noted earlier, the installer is now available per device, per OS. If you work on multiple devices or work on both RTOS and Linux, you'd have to download multiple installers.r r }r (hj hj ubaubh)r }r (hXCommand Line Installationr hj hj hhh}r (h]r htah]h]h]h]r hauhNhhh]r hXCommand Line Installationr r }r (hj hj ubaubh)r }r (hXThe tool to create the installer was changed from *InstallJammer*, which was an unsupported open source project, to *InstallBuilder*. If installing on the command line without any user interaction, the command option changed fromhj hj hhh}r (h]h]h]h]h]uhKbhhh]r (hX2The tool to create the installer was changed from r r }r (hX2The tool to create the installer was changed from hj ubjS )r }r (hX*InstallJammer*h}r (h]h]h]h]h]uhj h]r hX InstallJammerr r }r (hUhj ubahj[ ubhX3, which was an unsupported open source project, to r r }r (hX3, which was an unsupported open source project, to hj ubjS )r }r (hX*InstallBuilder*h}r (h]h]h]h]h]uhj h]r hXInstallBuilderr r }r (hUhj ubahj[ ubhXa. If installing on the command line without any user interaction, the command option changed fromr r }r (hXa. If installing on the command line without any user interaction, the command option changed fromhj ubeubj_)r }r (hX)--prefix [INSTALL_PATH] --mode unattendedhj hj hjbh}r (hhh]h]h]h]h]uhMxhhh]r hX)--prefix [INSTALL_PATH] --mode unattendedr r }r (hUhj ubaubh)r }r (hXtor hj hj hhh}r (h]h]h]h]h]uhKkhhh]r hXtor r }r (hj hj ubaubj_)r }r (hX%--prefix [INSTALL_PATH] --mode silenthj hj hjbh}r (hhh]h]h]h]h]uhM~hhh]r hX%--prefix [INSTALL_PATH] --mode silentr r }r (hUhj ubaubh)r }r (hXProcessor SDK Linuxr hj hj hhh}r (h]h]h]h]h]uhKrhhh]r hXProcessor SDK Linuxr r }r (hj hj ubaubh)r }r (hXlThis chapter describes what's changed from a Linux point of view, when migrating from MCSDK to Processor SDKr hj hj hhh}r(h]h]h]h]h]uhKshhh]rhXlThis chapter describes what's changed from a Linux point of view, when migrating from MCSDK to Processor SDKrr}r(hj hj ubaubh)r}r(hXDirectory Structurerhj hj hhh}r(h]r hlah]h]h]h]r hauhNhhh]r hXDirectory Structurer r }r(hjhjubaubh)r}r(hX In addition to the pre-built images and the filesystem, the installer now contains a copy of the Linux Kernel and U-Boot GIT repositories, and the sources for Kernel Modules, which'll be quite handy for reference or further development. There are additional helper/setup scripts to help with getting started with the EVMs. For an overview of the directory structure and a brief description of the contents of the folders, refer to `Processor\_SDK\_Linux\_Directory\_Structure `__.hj hj hhh}r(h]h]h]h]h]uhKyhhh]r(hXIn addition to the pre-built images and the filesystem, the installer now contains a copy of the Linux Kernel and U-Boot GIT repositories, and the sources for Kernel Modules, which'll be quite handy for reference or further development. There are additional helper/setup scripts to help with getting started with the EVMs. For an overview of the directory structure and a brief description of the contents of the folders, refer to rr}r(hXIn addition to the pre-built images and the filesystem, the installer now contains a copy of the Linux Kernel and U-Boot GIT repositories, and the sources for Kernel Modules, which'll be quite handy for reference or further development. There are additional helper/setup scripts to help with getting started with the EVMs. For an overview of the directory structure and a brief description of the contents of the folders, refer to hjubjg)r}r(hX\`Processor\_SDK\_Linux\_Directory\_Structure `__h}r(UnameX'Processor_SDK_Linux_Directory_StructurejkX*Overview_Directory_Structure_Overview.htmlh]h]h]h]h]uhjh]rhX'Processor_SDK_Linux_Directory_Structurerr}r(hUhjubahjpubhX.r}r(hX.hjubeubh)r}r (hXGetting Startedr!hj hj hhh}r"(h]r#hah]h]h]h]r$hBauhNhhh]r%hXGetting Startedr&r'}r((hj!hjubaubh)r)}r*(hXpThe Getting Started Guide for Processor SDK Linux is `here `__ Processor SDK Linux includes a set up script that scripts the necessary steps to setup the development environment on the host machine. The setup script verifies that the Linux host is the recommended Ubuntu LTS version, installs any required host packages, sets up the target FileSystem installation, NFS setup, TFTP setup, Minicom setup, uboot setup, Load uboot script and boots the EVM to Linux Prompt. After installation of the SDK on the Linux host, the setup script should be run to prepare the host for software development. Some of the tasks require administrator privileges. The script will prompt you when these administrator privileges are required. For more details, see `Processor\_SDK\_Linux\_Setup\_Script `__.hj hj hhh}r+(h]h]h]h]h]uhKhhh]r,(hX5The Getting Started Guide for Processor SDK Linux is r-r.}r/(hX5The Getting Started Guide for Processor SDK Linux is hj)ubjg)r0}r1(hX.`here `__h}r2(UnameXherejkX#Overview_Getting_Started_Guide.htmlh]h]h]h]h]uhj)h]r3hXherer4r5}r6(hUhj0ubahjpubhX Processor SDK Linux includes a set up script that scripts the necessary steps to setup the development environment on the host machine. The setup script verifies that the Linux host is the recommended Ubuntu LTS version, installs any required host packages, sets up the target FileSystem installation, NFS setup, TFTP setup, Minicom setup, uboot setup, Load uboot script and boots the EVM to Linux Prompt. After installation of the SDK on the Linux host, the setup script should be run to prepare the host for software development. Some of the tasks require administrator privileges. The script will prompt you when these administrator privileges are required. For more details, see r7r8}r9(hX Processor SDK Linux includes a set up script that scripts the necessary steps to setup the development environment on the host machine. The setup script verifies that the Linux host is the recommended Ubuntu LTS version, installs any required host packages, sets up the target FileSystem installation, NFS setup, TFTP setup, Minicom setup, uboot setup, Load uboot script and boots the EVM to Linux Prompt. After installation of the SDK on the Linux host, the setup script should be run to prepare the host for software development. Some of the tasks require administrator privileges. The script will prompt you when these administrator privileges are required. For more details, see hj)ubjg)r:}r;(hX``Processor\_SDK\_Linux\_Setup\_Script `__h}r<(UnameX Processor_SDK_Linux_Setup_ScriptjkX5Overview_Getting_Started_Guide.html#run-setup-scriptsh]h]h]h]h]uhj)h]r=hX Processor_SDK_Linux_Setup_Scriptr>r?}r@(hUhj:ubahjpubhX.rA}rB(hX.hj)ubeubh)rC}rD(hXThe procedure to flash the U-Boot, Kernel and filesystem into the flash memory on EVM, also known-as program\_evm, is still available, and documented `here `__.hj hj hhh}rE(h]h]h]h]h]uhKhhh]rF(hXThe procedure to flash the U-Boot, Kernel and filesystem into the flash memory on EVM, also known-as program_evm, is still available, and documented rGrH}rI(hXThe procedure to flash the U-Boot, Kernel and filesystem into the flash memory on EVM, also known-as program\_evm, is still available, and documented hjCubjg)rJ}rK(hXE`here `__h}rL(UnameXherejkX:Overview_Getting_Started_Guide.html#program-evm-user-guideh]h]h]h]h]uhjCh]rMhXhererNrO}rP(hUhjJubahjpubhX.rQ}rR(hX.hjCubeubh)rS}rT(hXU-BootrUhj hj hhh}rV(h]rWhah]h]h]h]rXhVauhNhhh]rYhXU-BootrZr[}r\(hjUhjSubaubh)r]}r^(hX_U-Boot is upgraded to be based on 2015.07. Listed below are a few major differences from MCSDK.r_hj hj hhh}r`(h]h]h]h]h]uhKhhh]rahX_U-Boot is upgraded to be based on 2015.07. Listed below are a few major differences from MCSDK.rbrc}rd(hj_hj]ubaubj)re}rf(hUhj hj hjh}rg(jX-h]h]h]h]h]uhKhhh]rh(j)ri}rj(hXTo Flash u-boot image onto NOR flash, u-boot upgrade command is changed from burn\_uboot to burn\_uboot\_spi (for SPI NOR boot) and burn\_uboot\_nand (for NAND boot)hjehj hjh}rk(h]h]h]h]h]uhNhhh]rlh)rm}rn(hXTo Flash u-boot image onto NOR flash, u-boot upgrade command is changed from burn\_uboot to burn\_uboot\_spi (for SPI NOR boot) and burn\_uboot\_nand (for NAND boot)hjihj hhh}ro(h]h]h]h]h]uhKh]rphXTo Flash u-boot image onto NOR flash, u-boot upgrade command is changed from burn_uboot to burn_uboot_spi (for SPI NOR boot) and burn_uboot_nand (for NAND boot)rqrr}rs(hXTo Flash u-boot image onto NOR flash, u-boot upgrade command is changed from burn\_uboot to burn\_uboot\_spi (for SPI NOR boot) and burn\_uboot\_nand (for NAND boot)hjmubaubaubj)rt}ru(hXMU-Boot starting address is now at 0x0c00 0000 instead of 0x0c00 1000 in MCSDKhjehj hjh}rv(h]h]h]h]h]uhNhhh]rwh)rx}ry(hXMU-Boot starting address is now at 0x0c00 0000 instead of 0x0c00 1000 in MCSDKrzhjthj hhh}r{(h]h]h]h]h]uhKh]r|hXMU-Boot starting address is now at 0x0c00 0000 instead of 0x0c00 1000 in MCSDKr}r~}r(hjzhjxubaubaubj)r}r(hX;bootz is enabled in u-boot. So use zImage instead of uImagerhjehj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhKh]rhX;bootz is enabled in u-boot. So use zImage instead of uImagerr}r(hjhjubaubaubj)r}r(hXFollowing default env variable have been updated. - **name\_mon** from skern--evm.bin to skern-.bin - **name\_fdt** from uImage--evm.dtb to -evm.dtb - **name\_kern** from keystone-evm.bin to zImage - **debug\_options** to **ks2\_debug**. This is set to 1 as before to allow CCS to be connected to DSP core. When the device boots to Linux, the DSP needs to be loaded with the image and run using mpmcl command first before the CCS can be connected to DSP cores. The ks2\_debug is not needed in this case. hjehNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hX1Following default env variable have been updated.rhjhj hhh}r(h]h]h]h]h]uhKh]rhX1Following default env variable have been updated.rr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hX9**name\_mon** from skern--evm.bin to skern-.binrh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhKh]r(j)r}r(hX **name\_mon**h}r(h]h]h]h]h]uhjh]rhXname_monrr}r(hUhjubahjubhX, from skern--evm.bin to skern-.binrr}r(hX, from skern--evm.bin to skern-.binhjubeubahjubj)r}r(hX8**name\_fdt** from uImage--evm.dtb to -evm.dtbrh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhKh]r(j)r}r(hX **name\_fdt**h}r(h]h]h]h]h]uhjh]rhXname_fdtrr}r(hUhjubahjubhX+ from uImage--evm.dtb to -evm.dtbrr}r(hX+ from uImage--evm.dtb to -evm.dtbhjubeubahjubj)r}r(hX.**name\_kern** from keystone-evm.bin to zImagerh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhKh]r(j)r}r(hX**name\_kern**h}r(h]h]h]h]h]uhjh]rhX name_kernrr}r(hUhjubahjubhX from keystone-evm.bin to zImagerr}r(hX from keystone-evm.bin to zImagehjubeubahjubj)r}r(hX0**debug\_options** to **ks2\_debug**. This is set to 1 as before to allow CCS to be connected to DSP core. When the device boots to Linux, the DSP needs to be loaded with the image and run using mpmcl command first before the CCS can be connected to DSP cores. The ks2\_debug is not needed in this case. h}r(h]h]h]h]h]uhjh]rh)r}r(hX/**debug\_options** to **ks2\_debug**. This is set to 1 as before to allow CCS to be connected to DSP core. When the device boots to Linux, the DSP needs to be loaded with the image and run using mpmcl command first before the CCS can be connected to DSP cores. The ks2\_debug is not needed in this case.hjhj hhh}r(h]h]h]h]h]uhKh]r(j)r}r(hX**debug\_options**h}r(h]h]h]h]h]uhjh]rhX debug_optionsrr}r(hUhjubahjubhX to rr}r(hX to hjubj)r}r(hX**ks2\_debug**h}r(h]h]h]h]h]uhjh]rhX ks2_debugrr}r(hUhjubahjubhX . This is set to 1 as before to allow CCS to be connected to DSP core. When the device boots to Linux, the DSP needs to be loaded with the image and run using mpmcl command first before the CCS can be connected to DSP cores. The ks2_debug is not needed in this case.rr}r(hX . This is set to 1 as before to allow CCS to be connected to DSP core. When the device boots to Linux, the DSP needs to be loaded with the image and run using mpmcl command first before the CCS can be connected to DSP cores. The ks2\_debug is not needed in this case.hjubeubahjubehjubeubj)r}r(hX<Following new env variables are introduced to allow use of a firmware initramfs image so that Linux drivers that requires firmware can get it from this before rootfs is mounted during the boot up. This is needed to support NFS for example. - **name\_fw\_rd** is set to k2-fw-initrd.cpio.gz - This image is supplied in the release package and contains K2 SerDes and QMSS Accumulator firmwares that are required by NetCP and PCIe drivers - init scripts are modified to include this firmware during boot and pass it to kernel using 2nd argument of bootz command. hjehNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hXFollowing new env variables are introduced to allow use of a firmware initramfs image so that Linux drivers that requires firmware can get it from this before rootfs is mounted during the boot up. This is needed to support NFS for example.rhjhj hhh}r(h]h]h]h]h]uhKh]rhXFollowing new env variables are introduced to allow use of a firmware initramfs image so that Linux drivers that requires firmware can get it from this before rootfs is mounted during the boot up. This is needed to support NFS for example.rr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hX**name\_fw\_rd** is set to k2-fw-initrd.cpio.gz - This image is supplied in the release package and contains K2 SerDes and QMSS Accumulator firmwares that are required by NetCP and PCIe driversh}r(h]h]h]h]h]uhjh]rh)r}r(hX**name\_fw\_rd** is set to k2-fw-initrd.cpio.gz - This image is supplied in the release package and contains K2 SerDes and QMSS Accumulator firmwares that are required by NetCP and PCIe drivershjhj hhh}r(h]h]h]h]h]uhKh]r(j)r }r (hX**name\_fw\_rd**h}r (h]h]h]h]h]uhjh]r hX name_fw_rdr r}r(hUhj ubahjubhX is set to k2-fw-initrd.cpio.gz - This image is supplied in the release package and contains K2 SerDes and QMSS Accumulator firmwares that are required by NetCP and PCIe driversrr}r(hX is set to k2-fw-initrd.cpio.gz - This image is supplied in the release package and contains K2 SerDes and QMSS Accumulator firmwares that are required by NetCP and PCIe drivershjubeubahjubj)r}r(hXzinit scripts are modified to include this firmware during boot and pass it to kernel using 2nd argument of bootz command. h}r(h]h]h]h]h]uhjh]rh)r}r(hXyinit scripts are modified to include this firmware during boot and pass it to kernel using 2nd argument of bootz command.rhjhj hhh}r(h]h]h]h]h]uhKh]rhXyinit scripts are modified to include this firmware during boot and pass it to kernel using 2nd argument of bootz command.rr}r(hjhjubaubahjubehjubeubj)r}r (hXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK Installationhjehj hjh}r!(h]h]h]h]h]uhNhhh]r"h)r#}r$(hXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK Installationr%hjhj hhh}r&(h]h]h]h]h]uhKh]r'hXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK Installationr(r)}r*(hj%hj#ubaubaubj)r+}r,(hXFor more details, refer to the `Processor\_SDK\_Linux\_U-Boot\_Release\_Notes `__ hjehj hjh}r-(h]h]h]h]h]uhNhhh]r.h)r/}r0(hXFor more details, refer to the `Processor\_SDK\_Linux\_U-Boot\_Release\_Notes `__hj+hj hhh}r1(h]h]h]h]h]uhKh]r2(hXFor more details, refer to the r3r4}r5(hXFor more details, refer to the hj/ubjg)r6}r7(hXl`Processor\_SDK\_Linux\_U-Boot\_Release\_Notes `__h}r8(UnameX(Processor_SDK_Linux_U-Boot_Release_NotesjkX8Foundational_Components_U-Boot.html#u-boot-release-notesh]h]h]h]h]uhj/h]r9hX(Processor_SDK_Linux_U-Boot_Release_Notesr:r;}r<(hUhj6ubahjpubeubaubeubh)r=}r>(hX Linux Kernelr?hj hj hhh}r@(h]rAhah]h]h]h]rBhUauhNhhh]rChX Linux KernelrDrE}rF(hj?hj=ubaubh)rG}rH(hXrThe Linux Kernel is upgraded to 4.1 (2015 LTS). Listed below are a few major differences from MCSDK (3.10 Kernel).rIhj hj hhh}rJ(h]h]h]h]h]uhKhhh]rKhXrThe Linux Kernel is upgraded to 4.1 (2015 LTS). Listed below are a few major differences from MCSDK (3.10 Kernel).rLrM}rN(hjIhjGubaubj)rO}rP(hUhj hj hjh}rQ(jX-h]h]h]h]h]uhKhhh]rR(j)rS}rT(hXFirmware is now not built into the Kernel. Instead they are available in the k2-fw-initrd.cpio.gz initramfs which are passed from u-boot to kernel as part of the bootz command for drivers that requires them very early in the boot up before the final rootfs is available.hjOhj hjh}rU(h]h]h]h]h]uhNhhh]rVh)rW}rX(hXFirmware is now not built into the Kernel. Instead they are available in the k2-fw-initrd.cpio.gz initramfs which are passed from u-boot to kernel as part of the bootz command for drivers that requires them very early in the boot up before the final rootfs is available.rYhjShj hhh}rZ(h]h]h]h]h]uhKh]r[hXFirmware is now not built into the Kernel. Instead they are available in the k2-fw-initrd.cpio.gz initramfs which are passed from u-boot to kernel as part of the bootz command for drivers that requires them very early in the boot up before the final rootfs is available.r\r]}r^(hjYhjWubaubaubj)r_}r`(hXOther firmwares that are used by dynamic modules are available in lib/firmware folder of the supplied file system images (for ubifs, initramfs etc) so that they are loaded and used by the driver from the user space.hjOhj hjh}ra(h]h]h]h]h]uhNhhh]rbh)rc}rd(hXOther firmwares that are used by dynamic modules are available in lib/firmware folder of the supplied file system images (for ubifs, initramfs etc) so that they are loaded and used by the driver from the user space.rehj_hj hhh}rf(h]h]h]h]h]uhKh]rghXOther firmwares that are used by dynamic modules are available in lib/firmware folder of the supplied file system images (for ubifs, initramfs etc) so that they are loaded and used by the driver from the user space.rhri}rj(hjehjcubaubaubj)rk}rl(hXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK InstallationhjOhj hjh}rm(h]h]h]h]h]uhNhhh]rnh)ro}rp(hXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK Installationrqhjkhj hhh}rr(h]h]h]h]h]uhKh]rshXeA copy of Kernel GIT repo is included in the "board-support" folder of the Processor SDK Installationrtru}rv(hjqhjoubaubaubj)rw}rx(hXFor more details, refer to the `Processor\_SDK\_Linux\_Kernel\_Release\_Notes `__ and `Processor\_SDK\_Linux\_Kernel\_Performance\_Guide `__ hjOhj hjh}ry(h]h]h]h]h]uhNhhh]rzh)r{}r|(hXFor more details, refer to the `Processor\_SDK\_Linux\_Kernel\_Release\_Notes `__ and `Processor\_SDK\_Linux\_Kernel\_Performance\_Guide `__hjwhj hhh}r}(h]h]h]h]h]uhKh]r~(hXFor more details, refer to the rr}r(hXFor more details, refer to the hj{ubjg)r}r(hXe`Processor\_SDK\_Linux\_Kernel\_Release\_Notes `__h}r(UnameX(Processor_SDK_Linux_Kernel_Release_NotesjkX1Foundational_Components_Kernel_Release_Notes.htmlh]h]h]h]h]uhj{h]rhX(Processor_SDK_Linux_Kernel_Release_Notesrr}r(hUhjubahjpubhX and rr}r(hX and hj{ubjg)r}r(hX_`Processor\_SDK\_Linux\_Kernel\_Performance\_Guide `__h}r(UnameX,Processor_SDK_Linux_Kernel_Performance_GuidejkX'Release_Specific_Performance_Guide.htmlh]h]h]h]h]uhj{h]rhX,Processor_SDK_Linux_Kernel_Performance_Guiderr}r(hUhjubahjpubeubaubeubh)r}r(hXRoadmaprhj hj hhh}r(h]rhhah]h]h]h]rhauhNhhh]rhXRoadmaprr}r(hjhjubaubh)r}r(hXFollowing features supported in MCSDK are not supported in Processor SDK 02.00.02 Release, and will get added in future Processor SDK releasesrhj hj hhh}r(h]h]h]h]h]uhKhhh]rhXFollowing features supported in MCSDK are not supported in Processor SDK 02.00.02 Release, and will get added in future Processor SDK releasesrr}r(hjhjubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhKhhh]rj)r}r(hXEDrivers: UDMA, 10G-KR firmware, IPSec inflow, kexec, network bonding hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXDDrivers: UDMA, 10G-KR firmware, IPSec inflow, kexec, network bondingrhjhj hhh}r(h]h]h]h]h]uhKh]rhXDDrivers: UDMA, 10G-KR firmware, IPSec inflow, kexec, network bondingrr}r(hjhjubaubaubaubj)r}r(hUhj hj hjh}r(h]h]h]h]h]uhKhhh]rj)r}r(hUjKhjhj hhh}r(h]h]h]h]h]uhKhhh]ubaubh)r}r(hXKernel Driversrhj hj hhh}r(h]rhbah]h]h]h]rhauhNhhh]rhXKernel Driversrr}r(hjhjubaubh)r}r(hXBListed below are a few major differences from MCSDK (3.10 Kernel).rhj hj hhh}r(h]h]h]h]h]uhKhhh]rhXBListed below are a few major differences from MCSDK (3.10 Kernel).rr}r(hjhjubaubh)r}r(hX NetCP Driversrhj hj hhh}r(h]rhah]h]h]h]rh4auhNhhh]rhX NetCP Driversrr}r(hjhjubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhKhhh]r(j)r}r(hX0Netcp qmss and pkt dma drivers at drivers/soc/tirhjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhKh]rhX0Netcp qmss and pkt dma drivers at drivers/soc/tirr}r(hjhjubaubaubj)r}r(hXIn older kernel, firmwares used to be built into the kernel as an ihex file which is not right thing to do due to licensing issues. Per community accepted practice, the right thing to do is to have the firmware images in a file system and use request\_firmware() API in kernel to load it from the file system and use. So with this kernel release, this is how firmware files are used in kernel drivers.hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXIn older kernel, firmwares used to be built into the kernel as an ihex file which is not right thing to do due to licensing issues. Per community accepted practice, the right thing to do is to have the firmware images in a file system and use request\_firmware() API in kernel to load it from the file system and use. So with this kernel release, this is how firmware files are used in kernel drivers.hjhj hhh}r(h]h]h]h]h]uhKh]rhXIn older kernel, firmwares used to be built into the kernel as an ihex file which is not right thing to do due to licensing issues. Per community accepted practice, the right thing to do is to have the firmware images in a file system and use request_firmware() API in kernel to load it from the file system and use. So with this kernel release, this is how firmware files are used in kernel drivers.rr}r(hXIn older kernel, firmwares used to be built into the kernel as an ihex file which is not right thing to do due to licensing issues. Per community accepted practice, the right thing to do is to have the firmware images in a file system and use request\_firmware() API in kernel to load it from the file system and use. So with this kernel release, this is how firmware files are used in kernel drivers.hjubaubaubj)r}r(hXThe Accumulator channels requires the QMSS Accumulator firmware (ks2\_qmss\_pdsp\_acc48.bin) that is located in the k2-fw-initrd.cpio.gz.hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXThe Accumulator channels requires the QMSS Accumulator firmware (ks2\_qmss\_pdsp\_acc48.bin) that is located in the k2-fw-initrd.cpio.gz.hjhj hhh}r(h]h]h]h]h]uhKh]rhXThe Accumulator channels requires the QMSS Accumulator firmware (ks2_qmss_pdsp_acc48.bin) that is located in the k2-fw-initrd.cpio.gz.rr}r(hXThe Accumulator channels requires the QMSS Accumulator firmware (ks2\_qmss\_pdsp\_acc48.bin) that is located in the k2-fw-initrd.cpio.gz.hjubaubaubj)r}r(hXvNetcp net driver at the same location as before at drivers/net/ethernet/ti/, but files are renamed with netcp\_ prefixhjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXvNetcp net driver at the same location as before at drivers/net/ethernet/ti/, but files are renamed with netcp\_ prefixhjhj hhh}r(h]h]h]h]h]uhKh]rhXuNetcp net driver at the same location as before at drivers/net/ethernet/ti/, but files are renamed with netcp_ prefixrr}r(hXvNetcp net driver at the same location as before at drivers/net/ethernet/ti/, but files are renamed with netcp\_ prefixhjubaubaubj)r }r (hXZDT documentation for the above drivers is under Documentation/devicetree/bindings/ folder.hjhj hjh}r (h]h]h]h]h]uhNhhh]r h)r }r(hXZDT documentation for the above drivers is under Documentation/devicetree/bindings/ folder.rhj hj hhh}r(h]h]h]h]h]uhKh]rhXZDT documentation for the above drivers is under Documentation/devicetree/bindings/ folder.rr}r(hjhj ubaubaubj)r}r(hXPA firmwares are now part of the k2-fw-initrd.cpio.g image that is used for early boot. PA firmwares in Linux includes a header + Firmware bloab from the PA LLD package. See kernel source directory Documentation/arm/keystone/netcp-pa.txt for details of the header format.hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXPA firmwares are now part of the k2-fw-initrd.cpio.g image that is used for early boot. PA firmwares in Linux includes a header + Firmware bloab from the PA LLD package. See kernel source directory Documentation/arm/keystone/netcp-pa.txt for details of the header format.rhjhj hhh}r(h]h]h]h]h]uhKh]rhXPA firmwares are now part of the k2-fw-initrd.cpio.g image that is used for early boot. PA firmwares in Linux includes a header + Firmware bloab from the PA LLD package. See kernel source directory Documentation/arm/keystone/netcp-pa.txt for details of the header format.rr}r (hjhjubaubaubj)r!}r"(hXjSysfs command file name paths have changed in this release. Please refer the NetCP User Guide for details.hjhj hjh}r#(h]h]h]h]h]uhNhhh]r$h)r%}r&(hXjSysfs command file name paths have changed in this release. Please refer the NetCP User Guide for details.r'hj!hj hhh}r((h]h]h]h]h]uhKh]r)hXjSysfs command file name paths have changed in this release. Please refer the NetCP User Guide for details.r*r+}r,(hj'hj%ubaubaubj)r-}r.(hX-QoS firmware is part of k2-fw-initrd.cpio.gz.r/hjhj hjh}r0(h]h]h]h]h]uhNhhh]r1h)r2}r3(hj/hj-hj hhh}r4(h]h]h]h]h]uhKh]r5hX-QoS firmware is part of k2-fw-initrd.cpio.gz.r6r7}r8(hj/hj2ubaubaubj)r9}r:(hXCQoS qmss driver is implemented in drivers/soc/ti/knav\_qmss\_qos.c.r;hjhj hjh}r<(h]h]h]h]h]uhNhhh]r=h)r>}r?(hj;hj9hj hhh}r@(h]h]h]h]h]uhKh]rAhXAQoS qmss driver is implemented in drivers/soc/ti/knav_qmss_qos.c.rBrC}rD(hXCQoS qmss driver is implemented in drivers/soc/ti/knav\_qmss\_qos.c.hj>ubaubaubj)rE}rF(hXCpts driver for Keystone is implemented in drivers/net/ethernet/ti/netcp\_cpts.c, which corresponds to the cpts.c in MCSDK release.hjhj hjh}rG(h]h]h]h]h]uhNhhh]rHh)rI}rJ(hXCpts driver for Keystone is implemented in drivers/net/ethernet/ti/netcp\_cpts.c, which corresponds to the cpts.c in MCSDK release.hjEhj hhh}rK(h]h]h]h]h]uhMh]rLhXCpts driver for Keystone is implemented in drivers/net/ethernet/ti/netcp_cpts.c, which corresponds to the cpts.c in MCSDK release.rMrN}rO(hXCpts driver for Keystone is implemented in drivers/net/ethernet/ti/netcp\_cpts.c, which corresponds to the cpts.c in MCSDK release.hjIubaubaubj)rP}rQ(hXWKeystone sideband crypto driver uses the firmware file: sa\_mci.fw which is different from that on older kernels. In older kernel, there is an array named sa\_eng\_aes\_enc\_mci\_tbl, which contains a set of micro instructions per algorithm for the SA hardware. This is now captured in a firmware file called sa\_mci.fw and used in the driver.hjhj hjh}rR(h]h]h]h]h]uhNhhh]rSh)rT}rU(hXWKeystone sideband crypto driver uses the firmware file: sa\_mci.fw which is different from that on older kernels. In older kernel, there is an array named sa\_eng\_aes\_enc\_mci\_tbl, which contains a set of micro instructions per algorithm for the SA hardware. This is now captured in a firmware file called sa\_mci.fw and used in the driver.hjPhj hhh}rV(h]h]h]h]h]uhMh]rWhXPKeystone sideband crypto driver uses the firmware file: sa_mci.fw which is different from that on older kernels. In older kernel, there is an array named sa_eng_aes_enc_mci_tbl, which contains a set of micro instructions per algorithm for the SA hardware. This is now captured in a firmware file called sa_mci.fw and used in the driver.rXrY}rZ(hXWKeystone sideband crypto driver uses the firmware file: sa\_mci.fw which is different from that on older kernels. In older kernel, there is an array named sa\_eng\_aes\_enc\_mci\_tbl, which contains a set of micro instructions per algorithm for the SA hardware. This is now captured in a firmware file called sa\_mci.fw and used in the driver.hjTubaubaubj)r[}r\(hXMulticast filters for special handling of multicast packets to avoid duplication are now not enabled through DT as in MCSDK. Instead a sysfs entry is provided for the same. See Documentation/networking/keystone-netcp.txt for details. hjhj hjh}r](h]h]h]h]h]uhNhhh]r^h)r_}r`(hXMulticast filters for special handling of multicast packets to avoid duplication are now not enabled through DT as in MCSDK. Instead a sysfs entry is provided for the same. See Documentation/networking/keystone-netcp.txt for details.rahj[hj hhh}rb(h]h]h]h]h]uhMh]rchXMulticast filters for special handling of multicast packets to avoid duplication are now not enabled through DT as in MCSDK. Instead a sysfs entry is provided for the same. See Documentation/networking/keystone-netcp.txt for details.rdre}rf(hjahj_ubaubaubeubh)rg}rh(hXK2 SerDes driversrihj hj hhh}rj(h]rkhah]h]h]h]rlh1auhNhhh]rmhXK2 SerDes driversrnro}rp(hjihjgubaubj)rq}rr(hUhj hj hjh}rs(jX-h]h]h]h]h]uhMhhh]rt(j)ru}rv(hXoK2 SerDes driver is located at drivers/phy/phy-keystone-serdes.c. It supports 3 serdes modes. PCIe, 1G and 10G.hjqhj hjh}rw(h]h]h]h]h]uhNhhh]rxh)ry}rz(hXoK2 SerDes driver is located at drivers/phy/phy-keystone-serdes.c. It supports 3 serdes modes. PCIe, 1G and 10G.r{hjuhj hhh}r|(h]h]h]h]h]uhMh]r}hXoK2 SerDes driver is located at drivers/phy/phy-keystone-serdes.c. It supports 3 serdes modes. PCIe, 1G and 10G.r~r}r(hj{hjyubaubaubj)r}r(hXThe following firmwares are required for proper functioning of the driver: - ks2\_gbe\_serdes.bin - for 1G - ks2\_xgbe\_serdes.bin - for 10G - ks2\_pcie\_serdes.bin - for PCIe hjqhNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hXJThe following firmwares are required for proper functioning of the driver:rhjhj hhh}r(h]h]h]h]h]uhMh]rhXJThe following firmwares are required for proper functioning of the driver:rr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXks2\_gbe\_serdes.bin - for 1Grh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhMh]rhXks2_gbe_serdes.bin - for 1Grr}r(hXks2\_gbe\_serdes.bin - for 1Ghjubaubahjubj)r}r(hXks2\_xgbe\_serdes.bin - for 10Grh}r(h]h]h]h]h]uhjh]rh)r}r(hjhjhj hhh}r(h]h]h]h]h]uhMh]rhXks2_xgbe_serdes.bin - for 10Grr}r(hXks2\_xgbe\_serdes.bin - for 10Ghjubaubahjubj)r}r(hX!ks2\_pcie\_serdes.bin - for PCIe h}r(h]h]h]h]h]uhjh]rh)r}r(hX ks2\_pcie\_serdes.bin - for PCIehjhj hhh}r(h]h]h]h]h]uhMh]rhXks2_pcie_serdes.bin - for PCIerr}r(hX ks2\_pcie\_serdes.bin - for PCIehjubaubahjubehjubeubj)r}r(hX{These firmwares have configuration values which otherwise were embedded in the driver code in v3.10.x based kernel releaseshjqhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX{These firmwares have configuration values which otherwise were embedded in the driver code in v3.10.x based kernel releasesrhjhj hhh}r(h]h]h]h]h]uhMh]rhX{These firmwares have configuration values which otherwise were embedded in the driver code in v3.10.x based kernel releasesrr}r(hjhjubaubaubj)r}r(hXThese firmwares are available in the file systems and k2-fw-initrd.cpio.gz file supplied in the release package and referred in the u-boot section of this document hjqhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXThese firmwares are available in the file systems and k2-fw-initrd.cpio.gz file supplied in the release package and referred in the u-boot section of this documentrhjhj hhh}r(h]h]h]h]h]uhMh]rhXThese firmwares are available in the file systems and k2-fw-initrd.cpio.gz file supplied in the release package and referred in the u-boot section of this documentrr}r(hjhjubaubaubeubj)r}r(hUhj hj hjh}r(h]h]h]h]h]uhMhhh]rj)r}r(hUjKhjhj hhh}r(h]h]h]h]h]uhKhhh]ubaubh)r}r(hX PCIe driverrhj hj hhh}r(h]rhah]h]h]h]rh7auhNhhh]rhX PCIe driverrr}r(hjhjubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhM$hhh]rj)r}r(hXPCIe RC mode was set in Kernel in MCSDK but moved to U-boot in ProcSDK for upstreaming reason. U-boot needs to be the same release version as Kernel. If not, PCIe mode initialization needs to be added in the older version of u-boot. hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXPCIe RC mode was set in Kernel in MCSDK but moved to U-boot in ProcSDK for upstreaming reason. U-boot needs to be the same release version as Kernel. If not, PCIe mode initialization needs to be added in the older version of u-boot.rhjhj hhh}r(h]h]h]h]h]uhM$h]rhXPCIe RC mode was set in Kernel in MCSDK but moved to U-boot in ProcSDK for upstreaming reason. U-boot needs to be the same release version as Kernel. If not, PCIe mode initialization needs to be added in the older version of u-boot.rr}r(hjhjubaubaubaubh)r}r(hXBuilding the Linux SDKrhj hj hhh}r(h]rhah]h]h]h]rhRauhNhhh]rhXBuilding the Linux SDKrr}r(hjhjubaubh)r}r(hX]As with MCSDK, the Processor SDK Linux can be fully assembled from sources, via Yocto. This gives the ability for customers to easily add or remove components from the default filesystem(s) provided in the Processor SDK Linux Installer. The instructions on how to build the Processor SDK Linux are available `here `__hj hj hhh}r(h]h]h]h]h]uhM-hhh]r(hX4As with MCSDK, the Processor SDK Linux can be fully assembled from sources, via Yocto. This gives the ability for customers to easily add or remove components from the default filesystem(s) provided in the Processor SDK Linux Installer. The instructions on how to build the Processor SDK Linux are available rr}r(hX4As with MCSDK, the Processor SDK Linux can be fully assembled from sources, via Yocto. This gives the ability for customers to easily add or remove components from the default filesystem(s) provided in the Processor SDK Linux Installer. The instructions on how to build the Processor SDK Linux are available hjubjg)r}r(hX)`here `__h}r(UnameXherejkXOverview_Building_the_SDK.htmlh]h]h]h]h]uhjh]rhXhererr}r(hUhjubahjpubeubj)r}r(hUhj hj hjh}r(h]h]h]h]h]uhM4hhh]rj)r }r (hUjKhjhj hhh}r (h]h]h]h]h]uhKhhh]ubaubh)r }r (hXProcessor SDK RTOSrhj hj hhh}r(h]h]h]h]h]uhM7hhh]rhXProcessor SDK RTOSrr}r(hjhj ubaubh)r}r(hXDirectory Structurerhj hj hhh}r(h]rhuah]h]h]h]rhauhNhhh]rhXDirectory Structurerr}r(hjhjubaubh)r}r(hXInformation on the Processor-SDK RTOS directory structre is `here `__. Some modifications were made to be consistent across all devices:hj hj hhh}r (h]h]h]h]h]uhM;hhh]r!(hX<Information on the Processor-SDK RTOS directory structre is r"r#}r$(hX<Information on the Processor-SDK RTOS directory structre is hjubjg)r%}r&(hX`here `__h}r'(UnameXherejkXhttp://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_overview.html?highlight=directory%20structure#directory-structureh]h]h]h]h]uhjh]r(hXherer)r*}r+(hUhj%ubahjpubhXC. Some modifications were made to be consistent across all devices:r,r-}r.(hXC. Some modifications were made to be consistent across all devices:hjubeubh)r/}r0(hXC66xr1hj hj hhh}r2(h]h]h]h]h]uhM?hhh]r3hXC66xr4r5}r6(hj1hj/ubaubj)r7}r8(hUhj hj hjh}r9(jX-h]h]h]h]h]uhMAhhh]r:(j)r;}r<(hXK**SDK folder** is per device. So, there is one for C665x and one for C667x.hj7hj hjh}r=(h]h]h]h]h]uhNhhh]r>h)r?}r@(hXK**SDK folder** is per device. So, there is one for C665x and one for C667x.hj;hj hhh}rA(h]h]h]h]h]uhMAh]rB(j)rC}rD(hX**SDK folder**h}rE(h]h]h]h]h]uhj?h]rFhX SDK folderrGrH}rI(hUhjCubahjubhX= is per device. So, there is one for C665x and one for C667x.rJrK}rL(hX= is per device. So, there is one for C665x and one for C667x.hj?ubeubaubj)rM}rN(hXl**IBL**, **POST**, and **boot utilities** moved from SDK folder ``tools`` to PDK folder ``packages/ti/boot``hj7hj hjh}rO(h]h]h]h]h]uhNhhh]rPh)rQ}rR(hXl**IBL**, **POST**, and **boot utilities** moved from SDK folder ``tools`` to PDK folder ``packages/ti/boot``hjMhj hhh}rS(h]h]h]h]h]uhMCh]rT(j)rU}rV(hX**IBL**h}rW(h]h]h]h]h]uhjQh]rXhXIBLrYrZ}r[(hUhjUubahjubhX, r\r]}r^(hX, hjQubj)r_}r`(hX**POST**h}ra(h]h]h]h]h]uhjQh]rbhXPOSTrcrd}re(hUhj_ubahjubhX, and rfrg}rh(hX, and hjQubj)ri}rj(hX**boot utilities**h}rk(h]h]h]h]h]uhjQh]rlhXboot utilitiesrmrn}ro(hUhjiubahjubhX moved from SDK folder rprq}rr(hX moved from SDK folder hjQubcdocutils.nodes literal rs)rt}ru(hX ``tools``h}rv(h]h]h]h]h]uhjQh]rwhXtoolsrxry}rz(hUhjtubahUliteralr{ubhX to PDK folder r|r}}r~(hX to PDK folder hjQubjs)r}r(hX``packages/ti/boot``h}r(h]h]h]h]h]uhjQh]rhXpackages/ti/bootrr}r(hUhjubahj{ubeubaubj)r}r(hXp**NDK examples** moved from SDK folder ``examples/ndk`` to PDK folder ``packages/ti/transport/ndk/nimu/example``hj7hj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXp**NDK examples** moved from SDK folder ``examples/ndk`` to PDK folder ``packages/ti/transport/ndk/nimu/example``hjhj hhh}r(h]h]h]h]h]uhMEh]r(j)r}r(hX**NDK examples**h}r(h]h]h]h]h]uhjh]rhX NDK examplesrr}r(hUhjubahjubhX moved from SDK folder rr}r(hX moved from SDK folder hjubjs)r}r(hX``examples/ndk``h}r(h]h]h]h]h]uhjh]rhX examples/ndkrr}r(hUhjubahj{ubhX to PDK folder rr}r(hX to PDK folder hjubjs)r}r(hX*``packages/ti/transport/ndk/nimu/example``h}r(h]h]h]h]h]uhjh]rhX&packages/ti/transport/ndk/nimu/examplerr}r(hUhjubahj{ubeubaubj)r}r(hXa**program\_evm** flash utility moved from SDK folder ``tools/program_evm`` to SDK folder ``bin`` hj7hj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX`**program\_evm** flash utility moved from SDK folder ``tools/program_evm`` to SDK folder ``bin``hjhj hhh}r(h]h]h]h]h]uhMGh]r(j)r}r(hX**program\_evm**h}r(h]h]h]h]h]uhjh]rhX program_evmrr}r(hUhjubahjubhX% flash utility moved from SDK folder rr}r(hX% flash utility moved from SDK folder hjubjs)r}r(hX``tools/program_evm``h}r(h]h]h]h]h]uhjh]rhXtools/program_evmrr}r(hUhjubahj{ubhX to SDK folder rr}r(hX to SDK folder hjubjs)r}r(hX``bin``h}r(h]h]h]h]h]uhjh]rhXbinrr}r(hUhjubahj{ubeubaubeubh)r}r(hXK2xrhj hj hhh}r(h]h]h]h]h]uhMJhhh]rhXK2xrr}r(hjhjubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhMLhhh]r(j)r}r(hX^**SDK and PDK folders** are per device. So, there are separate ones for K2E, K2H/K2K, and K2L.hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hX^**SDK and PDK folders** are per device. So, there are separate ones for K2E, K2H/K2K, and K2L.hjhj hhh}r(h]h]h]h]h]uhMLh]r(j)r}r(hX**SDK and PDK folders**h}r(h]h]h]h]h]uhjh]rhXSDK and PDK foldersrr}r(hUhjubahjubhXG are per device. So, there are separate ones for K2E, K2H/K2K, and K2L.rr}r(hXG are per device. So, there are separate ones for K2E, K2H/K2K, and K2L.hjubeubaubj)r}r(hXq**NDK examples** moved from SDK folder ``examples/ndk`` to PDK folder ``packages/ti/transport/ndk/nimu/example`` hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXp**NDK examples** moved from SDK folder ``examples/ndk`` to PDK folder ``packages/ti/transport/ndk/nimu/example``hjhj hhh}r(h]h]h]h]h]uhMNh]r(j)r}r(hX**NDK examples**h}r(h]h]h]h]h]uhjh]rhX NDK examplesrr}r(hUhjubahjubhX moved from SDK folder rr}r(hX moved from SDK folder hjubjs)r}r(hX``examples/ndk``h}r(h]h]h]h]h]uhjh]rhX examples/ndkrr}r(hUhjubahj{ubhX to PDK folder rr}r(hX to PDK folder hjubjs)r}r(hX*``packages/ti/transport/ndk/nimu/example``h}r(h]h]h]h]h]uhjh]r hX&packages/ti/transport/ndk/nimu/exampler r }r (hUhjubahj{ubeubaubeubh)r }r(hXGetting Startedrhj hj hhh}r(h]rhah]h]h]h]rh>auhNhhh]rhXGetting Startedrr}r(hjhj ubaubh)r}r(hXOThe Processor-SDK RTOS Getting Started Guide is located `here `__. As in MCSDK, this is the page to quickly find links for software and information on setting up hardware. Further information can be found in the `Developer Guide `__. This will look different from the MCSDK documentation since we are now focusing on how to use the SDK software to quickly create an embedded application rather than the design of the software.hj hj hhh}r(h]h]h]h]h]uhMThhh]r(hX8The Processor-SDK RTOS Getting Started Guide is located rr}r(hX8The Processor-SDK RTOS Getting Started Guide is located hjubjg)r}r(hX``here `__h}r (UnameXherejkXUhttp://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_overview.htmlh]h]h]h]h]uhjh]r!hXherer"r#}r$(hUhjubahjpubhX. As in MCSDK, this is the page to quickly find links for software and information on setting up hardware. Further information can be found in the r%r&}r'(hX. As in MCSDK, this is the page to quickly find links for software and information on setting up hardware. Further information can be found in the hjubjg)r(}r)(hXb`Developer Guide `__h}r*(UnameXDeveloper GuidejkXLhttp://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index.htmlh]h]h]h]h]uhjh]r+hXDeveloper Guider,r-}r.(hUhj(ubahjpubhX. This will look different from the MCSDK documentation since we are now focusing on how to use the SDK software to quickly create an embedded application rather than the design of the software.r/r0}r1(hX. This will look different from the MCSDK documentation since we are now focusing on how to use the SDK software to quickly create an embedded application rather than the design of the software.hjubeubh)r2}r3(hXMigration from MCSDK (K2x)r4hj hj hhh}r5(h]r6hah]h]h]h]r7h=auhNhhh]r8hXMigration from MCSDK (K2x)r9r:}r;(hj4hj2ubaubh)r<}r=(hXCSLr>hj hj hhh}r?(h]r@hah]h]h]h]rAhKauhNhhh]rBhXCSLrCrD}rE(hj>hj<ubaubj)rF}rG(hUhj hj hjh}rH(jX-h]h]h]h]h]uhMdhhh]rI(j)rJ}rK(hXRenamed “ti/csl/device” folder to “ti/csl/soc” – hence any include header files as “ti/csl/device/k2?/src/xxxx.h” needs to be changed to “ti/csl/soc/k2?/src/xxxx.h”hjFhj hjh}rL(h]h]h]h]h]uhNhhh]rMh)rN}rO(hXRenamed “ti/csl/device” folder to “ti/csl/soc” – hence any include header files as “ti/csl/device/k2?/src/xxxx.h” needs to be changed to “ti/csl/soc/k2?/src/xxxx.h”rPhjJhj hhh}rQ(h]h]h]h]h]uhMdh]rRhXRenamed “ti/csl/device” folder to “ti/csl/soc” – hence any include header files as “ti/csl/device/k2?/src/xxxx.h” needs to be changed to “ti/csl/soc/k2?/src/xxxx.h”rSrT}rU(hjPhjNubaubaubj)rV}rW(hXOne top level include header files per IP replaces multiple CSL files per IP for the following : - , , , , and hjFhNhjh}rX(h]h]h]h]h]uhNhhh]rY(h)rZ}r[(hXaOne top level include header files per IP replaces multiple CSL files per IP for the following :r\hjVhj hhh}r](h]h]h]h]h]uhMgh]r^hXaOne top level include header files per IP replaces multiple CSL files per IP for the following :r_r`}ra(hj\hjZubaubj)rb}rc(hUh}rd(jX-h]h]h]h]h]uhjVh]rej)rf}rg(hX, , , , and h}rh(h]h]h]h]h]uhjbh]rih)rj}rk(hX, , , , and hjfhj hhh}rl(h]h]h]h]h]uhMjh]rmhX, , , , and rnro}rp(hX, , , , and hjjubaubahjubahjubeubj)rq}rr(hXDeprecated top level cslr\_cpsw\_5gf.h files - applications including csl 5gf header files would need to migrate to include file. hjFhj hjh}rs(h]h]h]h]h]uhNhhh]rth)ru}rv(hXDeprecated top level cslr\_cpsw\_5gf.h files - applications including csl 5gf header files would need to migrate to include file.hjqhj hhh}rw(h]h]h]h]h]uhMnh]rxhXDeprecated top level cslr_cpsw_5gf.h files - applications including csl 5gf header files would need to migrate to include file.ryrz}r{(hXDeprecated top level cslr\_cpsw\_5gf.h files - applications including csl 5gf header files would need to migrate to include file.hjuubaubaubeubh)r|}r}(hX Migration from BIOS-MCSDK (C66x)r~hj hj hhh}r(h]rheah]h]h]h]rh auhNhhh]rhX Migration from BIOS-MCSDK (C66x)rr}r(hj~hj|ubaubh)r}r(hXCSLrhj hj hhh}r(h]rhnah]h]h]h]rhauhNhhh]rhXCSLrr}r(hjhjubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhMxhhh]r(j)r}r(hXaFollowing SoC defines are added to support C6657 and C6678 in the CSL. - SOC\_C6657 SOC\_C6678 hjhNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hXFFollowing SoC defines are added to support C6657 and C6678 in the CSL.rhjhj hhh}r(h]h]h]h]h]uhMxh]rhXFFollowing SoC defines are added to support C6657 and C6678 in the CSL.rr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]rj)r}r(hXSOC\_C6657 SOC\_C6678 h}r(h]h]h]h]h]uhjh]rh)r}r(hXSOC\_C6657 SOC\_C6678hjhj hhh}r(h]h]h]h]h]uhM{h]rhXSOC_C6657 SOC_C6678rr}r(hXSOC\_C6657 SOC\_C6678hjubaubahjubahjubeubj)r}r(hXfollowing files are not supported from the top level CSL folder (ti/csl) - csl\_mpuAux.h, csl\_memprot.h, csl\_memprotAux.h, csl\_pllcAux.h, csl\_cp\_tracer.h hjhNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hXHfollowing files are not supported from the top level CSL folder (ti/csl)rhjhj hhh}r(h]h]h]h]h]uhM}h]rhXHfollowing files are not supported from the top level CSL folder (ti/csl)rr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]rj)r}r(hXTcsl\_mpuAux.h, csl\_memprot.h, csl\_memprotAux.h, csl\_pllcAux.h, csl\_cp\_tracer.h h}r(h]h]h]h]h]uhjh]rh)r}r(hXScsl\_mpuAux.h, csl\_memprot.h, csl\_memprotAux.h, csl\_pllcAux.h, csl\_cp\_tracer.hhjhj hhh}r(h]h]h]h]h]uhMh]rhXMcsl_mpuAux.h, csl_memprot.h, csl_memprotAux.h, csl_pllcAux.h, csl_cp_tracer.hrr}r(hXScsl\_mpuAux.h, csl\_memprot.h, csl\_memprotAux.h, csl\_pllcAux.h, csl\_cp\_tracer.hhjubaubahjubahjubeubj)r}r(hXinclude file changes - Instead of , should be included - Instead of , should be included - Instead of needs to be changed to include cslr\_pcie.h - Instead of , include and respectively. - Instead of include hjhNhjh}r(h]h]h]h]h]uhNhhh]r(h)r}r(hXinclude file changesrhjhj hhh}r(h]h]h]h]h]uhMh]rhXinclude file changesrr}r(hjhjubaubj)r}r(hUh}r(jX-h]h]h]h]h]uhjh]r(j)r}r(hXTInstead of , should be includedh}r(h]h]h]h]h]uhjh]rh)r}r(hXTInstead of , should be includedhjhj hhh}r(h]h]h]h]h]uhMh]rhXQInstead of , should be includedrr}r(hXTInstead of , should be includedhjubaubahjubj)r}r(hX\Instead of , should be includedh}r(h]h]h]h]h]uhjh]rh)r}r(hX\Instead of , should be includedhjhj hhh}r(h]h]h]h]h]uhMh]rhXWInstead of , should be includedrr}r(hX\Instead of , should be includedhjubaubahjubj)r}r(hXNInstead of needs to be changed to include cslr\_pcie.hh}r(h]h]h]h]h]uhjh]rh)r}r(hXNInstead of needs to be changed to include cslr\_pcie.hhjhj hhh}r(h]h]h]h]h]uhMh]rhXKInstead of needs to be changed to include cslr_pcie.hrr}r(hXNInstead of needs to be changed to include cslr\_pcie.hhjubaubahjubj)r}r(hXInstead of , include and respectively.h}r(h]h]h]h]h]uhjh]rh)r}r(hXInstead of , include and respectively.hjhj hhh}r(h]h]h]h]h]uhMh]rhXInstead of , include and respectively.rr}r(hXInstead of , include and respectively.hjubaubahjubj)r}r(hXJInstead of include h}r(h]h]h]h]h]uhjh]r h)r }r (hXIInstead of include hjhj hhh}r (h]h]h]h]h]uhMh]r hXEInstead of include rr}r(hXIInstead of include hj ubaubahjubehjubeubeubcdocutils.nodes raw r)r}r(hXh
hj hj hUrawrh}r(UformatXhtmlhhh]h]h]h]h]uhMhhh]rhXh
rr}r(hUhjubaubh)r}r(hX**NOTE** Please define appropriate SOC define in the applicatoin when using the CSL. E.g., SOC\_C6678 or SOC\_C6657 for c6678 and c6657 devices.hj hj hhh}r(h]h]h]h]h]uhMhhh]r(j)r}r(hX**NOTE**h}r (h]h]h]h]h]uhjh]r!hXNOTEr"r#}r$(hUhjubahjubhX Please define appropriate SOC define in the applicatoin when using the CSL. E.g., SOC_C6678 or SOC_C6657 for c6678 and c6657 devices.r%r&}r'(hX Please define appropriate SOC define in the applicatoin when using the CSL. E.g., SOC\_C6678 or SOC\_C6657 for c6678 and c6657 devices.hjubeubj)r(}r)(hX
hj hj hjh}r*(UformatXhtmlhhh]h]h]h]h]uhMhhh]r+hX
r,r-}r.(hUhj(ubaubh)r/}r0(hXCPPIr1hj hj hhh}r2(h]r3hah]h]h]h]r4h?auhNhhh]r5hXCPPIr6r7}r8(hj1hj/ubaubj)r9}r:(hUhj hj hjh}r;(jX-h]h]h]h]h]uhMhhh]r<(j)r=}r>(hX8Interface with Resource Management (RM) LLD ( Optional )r?hj9hj hjh}r@(h]h]h]h]h]uhNhhh]rAh)rB}rC(hj?hj=hj hhh}rD(h]h]h]h]h]uhMh]rEhX8Interface with Resource Management (RM) LLD ( Optional )rFrG}rH(hj?hjBubaubaubj)rI}rJ(hX#Cppi\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /cppi\_device.c> file. Applications does not include this directly, need to align the configuration as demonstrated in the cppi\_device.c file: hj9hj hjh}rK(h]h]h]h]h]uhNhhh]rLh)rM}rN(hX"Cppi\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /cppi\_device.c> file. Applications does not include this directly, need to align the configuration as demonstrated in the cppi\_device.c file:hjIhj hhh}rO(h]h]h]h]h]uhMh]rPhXCppi_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /cppi_device.c> file. Applications does not include this directly, need to align the configuration as demonstrated in the cppi_device.c file:rQrR}rS(hX"Cppi\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /cppi\_device.c> file. Applications does not include this directly, need to align the configuration as demonstrated in the cppi\_device.c file:hjMubaubaubeubh)rT}rU(hXQMSSrVhj hj hhh}rW(h]rXh|ah]h]h]h]rYh"auhNhhh]rZhXQMSSr[r\}r](hjVhjTubaubj)r^}r_(hUhj hj hjh}r`(jX-h]h]h]h]h]uhMhhh]ra(j)rb}rc(hXWOptional RM LLD interface is supported to enable customers to use Resource manangement.hj^hj hjh}rd(h]h]h]h]h]uhNhhh]reh)rf}rg(hXWOptional RM LLD interface is supported to enable customers to use Resource manangement.rhhjbhj hhh}ri(h]h]h]h]h]uhMh]rjhXWOptional RM LLD interface is supported to enable customers to use Resource manangement.rkrl}rm(hjhhjfubaubaubj)rn}ro(hX0Qmss\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /qmss\_device.c> file. For applications that does not include this directly, it needs to align the configuration as demonstrated in the qmss\_device.c file: hj^hj hjh}rp(h]h]h]h]h]uhNhhh]rqh)rr}rs(hX/Qmss\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /qmss\_device.c> file. For applications that does not include this directly, it needs to align the configuration as demonstrated in the qmss\_device.c file:hjnhj hhh}rt(h]h]h]h]h]uhMh]ruhX,Qmss_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /qmss_device.c> file. For applications that does not include this directly, it needs to align the configuration as demonstrated in the qmss_device.c file:rvrw}rx(hX/Qmss\_GlobalConfigParams configuration structure is changed, however there is no change for the applications that include /qmss\_device.c> file. For applications that does not include this directly, it needs to align the configuration as demonstrated in the qmss\_device.c file:hjrubaubaubeubh)ry}rz(hXPA/SAr{hj hj hhh}r|(h]r}hcah]h]h]h]r~h auhNhhh]rhXPA/SArr}r(hj{hjyubaubj)r}r(hUhj hj hjh}r(jX-h]h]h]h]h]uhMhhh]rj)r}r(hXSupport for Resource management (RM LLD) is supported for PA LLD - Note that this is an optional feature, applications that do not enable RM would not need to bring in RM LLD. hjhj hjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXSupport for Resource management (RM LLD) is supported for PA LLD - Note that this is an optional feature, applications that do not enable RM would not need to bring in RM LLD.rhjhj hhh}r(h]h]h]h]h]uhMh]rhXSupport for Resource management (RM LLD) is supported for PA LLD - Note that this is an optional feature, applications that do not enable RM would not need to bring in RM LLD.rr}r(hjhjubaubaubaubh)r}r(hXHUA Demonstrationrhj hj hhh}r(h]rhah]h]h]h]rhIauhNhhh]rhXHUA Demonstrationrr}r(hjhjubaubh)r}r(hXThe HUA Demo for C66x in BIOS-MCSDK is no longer supported in Processor-SDK. Rather, the Image Processing Demo is the common RTOS demonstration that is supported across all supported devices in the Processor-SDK for RTOS. This demo will continue to be enhanced with more capabilities.rhj hj hhh}r(h]h]h]h]h]uhMhhh]rhXThe HUA Demo for C66x in BIOS-MCSDK is no longer supported in Processor-SDK. Rather, the Image Processing Demo is the common RTOS demonstration that is supported across all supported devices in the Processor-SDK for RTOS. This demo will continue to be enhanced with more capabilities.rr}r(hjhjubaubh)r}r(hX.Common Migration for Both MCSDK and BIOS-MCSDKrhj hj hhh}r(h]rhah]h]h]h]rh(auhNhhh]rhX.Common Migration for Both MCSDK and BIOS-MCSDKrr}r(hjhjubaubh)r}r(hXPlatform Libraryrhj hj hhh}r(h]rhoah]h]h]h]rhauhNhhh]rhXPlatform Libraryrr}r(hjhjubaubh)r}r(hX)The Platform Library is deprecated and functionality is provided by the Board Library. For backwards compatibility, Platform Library is provided in this initial release. But it is planned to be dropped in a future release. The Board Library is a common API across all devices in the Processor-SDK.rhj hj hhh}r(h]h]h]h]h]uhMhhh]rhX)The Platform Library is deprecated and functionality is provided by the Board Library. For backwards compatibility, Platform Library is provided in this initial release. But it is planned to be dropped in a future release. The Board Library is a common API across all devices in the Processor-SDK.rr}r(hjhjubaubj)r}r(hUhj hj hjh}r(h]h]h]h]h]uhMhhh]rj)r}r(hUjKhjhj hhh}r(h]h]h]h]h]uhKhhh]ubaubh)r}r(hX8MCSDK1.1 to Processor SDK Migration for OMAPL13x devicesrhj hj hhh}r(h]rhah]h]h]h]rh)auhNhhh]rhX8MCSDK1.1 to Processor SDK Migration for OMAPL13x devicesrr}r(hjhjubaubh)r}r(hXFor OMAPL13x devices, you can refer to the `MCSDK1.1 to Processor SDK Migration `__ linkhj hj hhh}r(h]h]h]h]h]uhMhhh]r(hX+For OMAPL13x devices, you can refer to the rr}r(hX+For OMAPL13x devices, you can refer to the hjubjg)r}r(hX`MCSDK1.1 to Processor SDK Migration `__h}r(UnameX#MCSDK1.1 to Processor SDK MigrationjkXjRelease_Specific_Migration_Guide.html#mcsdk1-1-to-processor-sdk-linux-migration-guide-for-omapl13x-devicesh]h]h]h]h]uhjh]rhX#MCSDK1.1 to Processor SDK Migrationrr}r(hUhjubahjpubhX linkrr}r(hX linkhjubeubh)r}r(hX>MCSDK1.1 to Processor SDK Migration Guide for OMAPL13x deviceshj hX`/home/gtbldadm/nightlybuilds/processor-sdk-doc/source/linux/Release_Specific_Migration_Guide.rstrhhh}r(hhh]h]h]h]h]uhKhhh]rhX>MCSDK1.1 to Processor SDK Migration Guide for OMAPL13x devicesrr}r(hUhjubaubh)r}r(hXlhttp://processors.wiki.ti.com/index.php/MCSDK1.1_to_Processor_SDK_Migration_Guide_for_OMAPL13x/C674x_deviceshj hhXjsource/linux/Release_Specific/MCSDK1.1_to_Processor_SDK_Migration_Guide_for_OMAPL13x_C674x_devices.rst.incrr}rbhhh}r(hhh]h]h]h]h]uhKhhh]rhXlhttp://processors.wiki.ti.com/index.php/MCSDK1.1_to_Processor_SDK_Migration_Guide_for_OMAPL13x/C674x_devicesrr}r(hUhjubaubeubh)r}r(hUhhhjhhh}r(h]h]h]h]rhah]rhj)r?}r@(hXpThe Processor SDK Linux installer is available only for 64-bit host machines running Linux. Support for 32-bit machines is dropped primarily due to the Linzro toolchain not supporting 32-bit anymore. .. ifconfig:: CONFIG_sdk in ('PLSDK') Host support for the SDK is described in the `Release Notes `__ hj;hNhjh}rA(h]h]h]h]h]uhNhhh]rB(h)rC}rD(hXThe Processor SDK Linux installer is available only for 64-bit host machines running Linux. Support for 32-bit machines is dropped primarily due to the Linzro toolchain not supporting 32-bit anymore.rEhj?hjhhh}rF(h]h]h]h]h]uhKh]rGhXThe Processor SDK Linux installer is available only for 64-bit host machines running Linux. Support for 32-bit machines is dropped primarily due to the Linzro toolchain not supporting 32-bit anymore.rHrI}rJ(hjEhjCubaubcsphinx.ext.ifconfig ifconfig rK)rL}rM(hUhj?hjhUifconfigrNh}rO(UexprrPXCONFIG_sdk in ('PLSDK')h]h]h]h]h]uhKhhh]rQh)rR}rS(hXwHost support for the SDK is described in the `Release Notes `__hjLhjhhh}rT(h]h]h]h]h]uhKhhh]rU(hX-Host support for the SDK is described in the rVrW}rX(hX-Host support for the SDK is described in the hjRubjg)rY}rZ(hXJ`Release Notes `__h}r[(UnameX Release NotesjkX6Release_Specific_PLSDK_Release_Notes.html#host_supporth]h]h]h]h]uhjRh]r\hX Release Notesr]r^}r_(hUhjYubahjpubeubaubeubaubh)r`}ra(hX Tool Chainrbhjhjhhh}rc(h]rdhjah]h]h]h]rehauhNhhh]rfhX Tool Chainrgrh}ri(hjbhj`ubaubj)rj}rk(hUhjhjhjh}rl(jX-h]h]h]h]h]uhK#hhh]rmj)rn}ro(hXDProcessor Linux SDK is using Linaro GCC 6.2-2016.11 cross compiler. hjjhjhjh}rp(h]h]h]h]h]uhNhhh]rqh)rr}rs(hXCProcessor Linux SDK is using Linaro GCC 6.2-2016.11 cross compiler.rthjnhjhhh}ru(h]h]h]h]h]uhK#h]rvhXCProcessor Linux SDK is using Linaro GCC 6.2-2016.11 cross compiler.rwrx}ry(hjthjrubaubaubaubh)rz}r{(hXDirectory Structurer|hjhjhhh}r}(h]r~hah]h]h]h]rh*auhNhhh]rhXDirectory Structurerr}r(hj|hjzubaubj)r}r(hUhjhjhjh}r(jX-h]h]h]h]h]uhK(hhh]r(j)r}r(hXfThe images directory in MCSDK is renamed to prebuilt\_images and moved under board\_support directory.hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXfThe images directory in MCSDK is renamed to prebuilt\_images and moved under board\_support directory.hjhjhhh}r(h]h]h]h]h]uhK(h]rhXdThe images directory in MCSDK is renamed to prebuilt_images and moved under board_support directory.rr}r(hXfThe images directory in MCSDK is renamed to prebuilt\_images and moved under board\_support directory.hjubaubaubj)r}r(hXIn addition to the prebuilt\_images and filesystem, the Linux installer now contains a copy of the Linux Kernel and U-Boot GIT repositories.hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXIn addition to the prebuilt\_images and filesystem, the Linux installer now contains a copy of the Linux Kernel and U-Boot GIT repositories.hjhjhhh}r(h]h]h]h]h]uhK*h]rhXIn addition to the prebuilt_images and filesystem, the Linux installer now contains a copy of the Linux Kernel and U-Boot GIT repositories.rr}r(hXIn addition to the prebuilt\_images and filesystem, the Linux installer now contains a copy of the Linux Kernel and U-Boot GIT repositories.hjubaubaubj)r}r(hXtA script create-sdcard.sh is provided in bin directory to create the SD card using prebuilt images in Processor SDK.hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXtA script create-sdcard.sh is provided in bin directory to create the SD card using prebuilt images in Processor SDK.rhjhjhhh}r(h]h]h]h]h]uhK-h]rhXtA script create-sdcard.sh is provided in bin directory to create the SD card using prebuilt images in Processor SDK.rr}r(hjhjubaubaubj)r}r(hXhost-tools folder in MCSDK is not included in Processor SDK. Pinmux utility can be downloaded from ti.com. Aisgen utility is replaced by dd command to generate the u-boot ais image.hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXhost-tools folder in MCSDK is not included in Processor SDK. Pinmux utility can be downloaded from ti.com. Aisgen utility is replaced by dd command to generate the u-boot ais image.rhjhjhhh}r(h]h]h]h]h]uhK/h]rhXhost-tools folder in MCSDK is not included in Processor SDK. Pinmux utility can be downloaded from ti.com. Aisgen utility is replaced by dd command to generate the u-boot ais image.rr}r(hjhjubaubaubj)r}r(hXFor an overview of the directory structure and a brief description of the contents of the folders, please refer to `Processor SDK Linux Directory Structure `__ hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXFor an overview of the directory structure and a brief description of the contents of the folders, please refer to `Processor SDK Linux Directory Structure `__hjhjhhh}r(h]h]h]h]h]uhK2h]r(hXsFor an overview of the directory structure and a brief description of the contents of the folders, please refer to rr}r(hXsFor an overview of the directory structure and a brief description of the contents of the folders, please refer to hjubjg)r}r(hXX`Processor SDK Linux Directory Structure `__h}r(UnameX'Processor SDK Linux Directory StructurejkX*Overview_Directory_Structure_Overview.htmlh]h]h]h]h]uhjh]rhX'Processor SDK Linux Directory Structurerr}r(hUhjubahjpubeubaubeubh)r}r(hXU-Bootrhjhjhhh}r(h]rhsah]h]h]h]rhauhNhhh]rhXU-Bootrr}r(hjhjubaubj)r}r(hUhjhjhjh}r(jX-h]h]h]h]h]uhK:hhh]r(j)r}r(hX;Bootz is enabled in u-boot. So use zImage instead of uImagerhjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hjhjhjhhh}r(h]h]h]h]h]uhK:h]rhX;Bootz is enabled in u-boot. So use zImage instead of uImagerr}r(hjhjubaubaubj)r}r(hXcA copy of u-boot GIT repo is included in the board-support folder of the Processor SDK installationhjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXcA copy of u-boot GIT repo is included in the board-support folder of the Processor SDK installationrhjhjhhh}r(h]h]h]h]h]uhK;h]rhXcA copy of u-boot GIT repo is included in the board-support folder of the Processor SDK installationrr}r(hjhjubaubaubj)r}r(hXdAisgen utility is not used in Processor SDK to generate the U-Boot ais image, but using dd command: hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXcAisgen utility is not used in Processor SDK to generate the U-Boot ais image, but using dd command:rhjhjhhh}r(h]h]h]h]h]uhK=h]rhXcAisgen utility is not used in Processor SDK to generate the U-Boot ais image, but using dd command:rr}r(hjhjubaubaubeubj_)r}r(hX@$ sudo dd if=u-boot.ais of=/dev/sd seek=117 bs=512 conv=fsynchjhjhjbh}r(hhh]h]h]h]h]uhM,hhh]rhX@$ sudo dd if=u-boot.ais of=/dev/sd seek=117 bs=512 conv=fsyncrr}r(hUhjubaubj)r}r(hUhjhjhjh}r(jX-h]h]h]h]h]uhKDhhh]rj)r}r(hXFor more details, refer to `Processor SDK U-Boot Release Notes `__ and `Processor SDK U-Boot User’s Guide `__ hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r }r (hXFor more details, refer to `Processor SDK U-Boot Release Notes `__ and `Processor SDK U-Boot User’s Guide `__hjhjhhh}r (h]h]h]h]h]uhKDh]r (hXFor more details, refer to r r}r(hXFor more details, refer to hj ubjg)r}r(hXa`Processor SDK U-Boot Release Notes `__h}r(UnameX"Processor SDK U-Boot Release NotesjkX8Foundational_Components_U-Boot.html#u-boot-release-notesh]h]h]h]h]uhj h]rhX"Processor SDK U-Boot Release Notesrr}r(hUhjubahjpubhX and rr}r(hX and hj ubjg)r}r(hXa`Processor SDK U-Boot User’s Guide `__h}r(UnameX#Processor SDK U-Boot User’s GuidejkX7Foundational_Components_U-Boot.html#u-boot-user-s-guideh]h]h]h]h]uhj h]rhX#Processor SDK U-Boot User’s Guiderr}r (hUhjubahjpubeubaubaubh)r!}r"(hX Linux Kernelr#hjhjhhh}r$(h]r%hah]h]h]h]r&h2auhNhhh]r'hX Linux Kernelr(r)}r*(hj#hj!ubaubj)r+}r,(hUhjhjhjh}r-(jX-h]h]h]h]h]uhKLhhh]r.(j)r/}r0(hX$The Linux kernel is upgraded to 4.9.r1hj+hjhjh}r2(h]h]h]h]h]uhNhhh]r3h)r4}r5(hj1hj/hjhhh}r6(h]h]h]h]h]uhKLh]r7hX$The Linux kernel is upgraded to 4.9.r8r9}r:(hj1hj4ubaubaubj)r;}r<(hXcA copy of Kernel GIT repo is included in the board-support folder of the Processor SDK installationhj+hjhjh}r=(h]h]h]h]h]uhNhhh]r>h)r?}r@(hXcA copy of Kernel GIT repo is included in the board-support folder of the Processor SDK installationrAhj;hjhhh}rB(h]h]h]h]h]uhKMh]rChXcA copy of Kernel GIT repo is included in the board-support folder of the Processor SDK installationrDrE}rF(hjAhj?ubaubaubj)rG}rH(hXPKernel is device tree (.dts) based, and not board platform based implementation.hj+hjhjh}rI(h]h]h]h]h]uhNhhh]rJh)rK}rL(hXPKernel is device tree (.dts) based, and not board platform based implementation.rMhjGhjhhh}rN(h]h]h]h]h]uhKOh]rOhXPKernel is device tree (.dts) based, and not board platform based implementation.rPrQ}rR(hjMhjKubaubaubj)rS}rT(hXFor more details, refer to `Processor SDK Kernel Release Notes `__ and `Processor SDK Kernel User’s Guide `__ hj+hjhjh}rU(h]h]h]h]h]uhNhhh]rVh)rW}rX(hXFor more details, refer to `Processor SDK Kernel Release Notes `__ and `Processor SDK Kernel User’s Guide `__hjShjhhh}rY(h]h]h]h]h]uhKQh]rZ(hXFor more details, refer to r[r\}r](hXFor more details, refer to hjWubjg)r^}r_(hXZ`Processor SDK Kernel Release Notes `__h}r`(UnameX"Processor SDK Kernel Release NotesjkX1Foundational_Components_Kernel_Release_Notes.htmlh]h]h]h]h]uhjWh]rahX"Processor SDK Kernel Release Notesrbrc}rd(hUhj^ubahjpubhX and rerf}rg(hX and hjWubjg)rh}ri(hXY`Processor SDK Kernel User’s Guide `__h}rj(UnameX#Processor SDK Kernel User’s GuidejkX/Foundational_Components_Kernel_Users_Guide.htmlh]h]h]h]h]uhjWh]rkhX#Processor SDK Kernel User’s Guiderlrm}rn(hUhjhubahjpubeubaubeubh)ro}rp(hXBuilding the Linux SDKrqhjhjhhh}rr(h]rshkah]h]h]h]rthauhNhhh]ruhXBuilding the Linux SDKrvrw}rx(hjqhjoubaubj)ry}rz(hUhjhjhjh}r{(jX-h]h]h]h]h]uhKYhhh]r|(j)r}}r~(hXGThe Processor SDK Linux can be fully assembled from sources, via Yocto.hjyhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXGThe Processor SDK Linux can be fully assembled from sources, via Yocto.rhj}hjhhh}r(h]h]h]h]h]uhKYh]rhXGThe Processor SDK Linux can be fully assembled from sources, via Yocto.rr}r(hjhjubaubaubj)r}r(hXThe instructions on how to build the Processor SDK Linux are available in `Building the Linux SDK `__ hjyhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXThe instructions on how to build the Processor SDK Linux are available in `Building the Linux SDK `__hjhjhhh}r(h]h]h]h]h]uhK[h]r(hXJThe instructions on how to build the Processor SDK Linux are available in rr}r(hXJThe instructions on how to build the Processor SDK Linux are available in hjubjg)r}r(hX;`Building the Linux SDK `__h}r(UnameXBuilding the Linux SDKjkXOverview_Building_the_SDK.htmlh]h]h]h]h]uhjh]rhXBuilding the Linux SDKrr}r(hUhjubahjpubeubaubeubh)r}r(hX#Inter-Processor Communication (IPC)rhjhjhhh}r(h]rh~ah]h]h]h]rh$auhNhhh]rhX#Inter-Processor Communication (IPC)rr}r(hjhjubaubj)r}r(hUhjhjhjh}r(jX-h]h]h]h]h]uhKbhhh]r(j)r}r(hXGProcessor SDK supports IPC 3.x. It is not Syslink based implementation.hjhjhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXGProcessor SDK supports IPC 3.x. It is not Syslink based implementation.rhjhjhhh}r(h]h]h]h]h]uhKbh]rhXGProcessor SDK supports IPC 3.x. It is not Syslink based implementation.rr}r(hjhjubaubaubj)r}r(hXTo migrate to IPC 3.x, please refer to `IPC 3.x Migration Guide `__ hjhXinternal padding after source/linux/Release_Specific/MCSDK1.1_to_Processor_SDK_Migration_Guide_for_OMAPL13x_C674x_devices.rst.incrhjh}r(h]h]h]h]h]uhNhhh]rh)r}r(hXTo migrate to IPC 3.x, please refer to `IPC 3.x Migration Guide `__hjhjhhh}r(h]h]h]h]h]uhKdh]r(hX'To migrate to IPC 3.x, please refer to rr}r(hX'To migrate to IPC 3.x, please refer to hjubjg)r}r(hX]`IPC 3.x Migration Guide `__h}r(UnameXIPC 3.x Migration GuidejkX?http://processors.wiki.ti.com/index.php/IPC_3.x_Migration_Guideh]h]h]h]h]uhjh]rhXIPC 3.x Migration Guiderr}r(hUhjubahjpubeubaubeubh)r}r(hX&AMSDK to Processor SDK Migration Guidehjhjhhh}r(hhh]h]h]h]h]uhKhhh]rhX&AMSDK to Processor SDK Migration Guiderr}r(hUhjubaubh)r}r(hXNhttp://processors.wiki.ti.com/index.php/AMSDK_to_Processor_SDK_Migration_GuidehjhhXLsource/linux/Release_Specific/AMSDK_to_Processor_SDK_Migration_Guide.rst.incrr}rbhhh}r(hhh]h]h]h]h]uhKhhh]rhXNhttp://processors.wiki.ti.com/index.php/AMSDK_to_Processor_SDK_Migration_Guiderr}r(hUhjubaubeubh)r}r(hUhhhjhhh}r(h]h]h]h]rhaah]rhauhKhhh]r(h)r}r(hX&AMSDK to Processor SDK Migration Guiderhjhjhhh}r(h]h]h]h]h]uhKhhh]rhX&AMSDK to Processor SDK Migration Guiderr}r(hjhjubaubh)r}r(hXFor many years, the AMSDK has been a great way to get started with Embedded Linux development on TI's broad market line of ARM Cortex-A microprocessors, also referred to as Sitara. If you go by "what's in a name?", you can easily see the connection. The "AM" of AMSDK is the first two letters of part numbers in the Sitara line-up. For example, take the AM335x which is an ARM Cortex-A8 based processor which drives the popular Beaglebone Black board. The "SDK" refers to Software Development Kit. The AMSDK was designed from the ground up to provide a great starting point for developing an embedded Linux system on a Sitara Processor. One of the goals of the AMSDK was to enable a developer to quickly (under 10 minutes) explore and evaluate the possibilities as well as start development on a customized Linux software platform in under an hour. It's up to each developer to decide if the AMSDK achieved these goals, but the feedback overall has been positive.rhjhjhhh}r(h]h]h]h]h]uhKhhh]rhXFor many years, the AMSDK has been a great way to get started with Embedded Linux development on TI's broad market line of ARM Cortex-A microprocessors, also referred to as Sitara. If you go by "what's in a name?", you can easily see the connection. The "AM" of AMSDK is the first two letters of part numbers in the Sitara line-up. For example, take the AM335x which is an ARM Cortex-A8 based processor which drives the popular Beaglebone Black board. The "SDK" refers to Software Development Kit. The AMSDK was designed from the ground up to provide a great starting point for developing an embedded Linux system on a Sitara Processor. One of the goals of the AMSDK was to enable a developer to quickly (under 10 minutes) explore and evaluate the possibilities as well as start development on a customized Linux software platform in under an hour. It's up to each developer to decide if the AMSDK achieved these goals, but the feedback overall has been positive.rr}r(hjhjubaubh)r}r(hXLike the Linux kernel itself, which evolves every 77 days or so with a new release, it's time for the AMSDK to evolve, without departing from it's heritage. TI has a rich offering of microprocessors from multicore ARMs to tiny, power-efficient DSPs, and different combinations of ARM, DSP, and specialized cores to provide the broad market a variety of solutions. Since many developers will touch several of these devices from project to project, it is beneficial to standardize the experience to maximize the benefit of learning. The limited time developers have in today's time-to-market driven environment is very important and shouldn't be wasted.rhjhjhhh}r(h]h]h]h]h]uhKhhh]rhXLike the Linux kernel itself, which evolves every 77 days or so with a new release, it's time for the AMSDK to evolve, without departing from it's heritage. TI has a rich offering of microprocessors from multicore ARMs to tiny, power-efficient DSPs, and different combinations of ARM, DSP, and specialized cores to provide the broad market a variety of solutions. Since many developers will touch several of these devices from project to project, it is beneficial to standardize the experience to maximize the benefit of learning. The limited time developers have in today's time-to-market driven environment is very important and shouldn't be wasted.rr}r(hjhjubaubh)r}r(hXjTo this end, the AMSDK is being renamed to the Processor SDK for Linux. This new title will allow future devices, which may not carry the "AM" naming convention, to benefit from the same software development experience. Each developer that uses the Processor SDK from project to project can leverage that experience and know with confidence what they can expect.rhjhjhhh}r(h]h]h]h]h]uhK!hhh]rhXjTo this end, the AMSDK is being renamed to the Processor SDK for Linux. This new title will allow future devices, which may not carry the "AM" naming convention, to benefit from the same software development experience. Each developer that uses the Processor SDK from project to project can leverage that experience and know with confidence what they can expect.rr}r(hjhjubaubh)r}r(hX=With this background in place, let's dig into more specifics.rhjhjhhh}r(h]h]h]h]h]uhK(hhh]rhX=With this background in place, let's dig into more specifics.rr}r(hjhjubaubh)r}r(hUhjhjhhh}r (h]h]h]h]r hah]r h'auhK+hhh]r (h)r }r(hX-Migrating from AMSDK 8.0 to Processor SDK 1.0rhjhjhhh}r(h]h]h]h]h]uhK+hhh]rhX-Migrating from AMSDK 8.0 to Processor SDK 1.0rr}r(hjhj ubaubh)r}r(hXAs suggested above, this transition at this point in time, is largely a name change. The good news is, migration should be very simple. From a component point of view, Processor SDK for Linux 1.0 is very similar to AMSDK 8.0:rhjhjhhh}r(h]h]h]h]h]uhK-hhh]rhXAs suggested above, this transition at this point in time, is largely a name change. The good news is, migration should be very simple. From a component point of view, Processor SDK for Linux 1.0 is very similar to AMSDK 8.0:rr}r(hjhjubaubcdocutils.nodes table r)r}r(hUhjhjhUtabler h}r!(h]h]h]h]h]uhNhhh]r"cdocutils.nodes tgroup r#)r$}r%(hUh}r&(h]h]h]h]h]UcolsKuhjh]r'(cdocutils.nodes colspec r()r)}r*(hUh}r+(h]h]h]h]h]UcolwidthKuhj$h]hUcolspecr,ubj()r-}r.(hUh}r/(h]h]h]h]h]UcolwidthK%uhj$h]hj,ubj()r0}r1(hUh}r2(h]h]h]h]h]UcolwidthK%uhj$h]hj,ubcdocutils.nodes thead r3)r4}r5(hUh}r6(h]h]h]h]h]uhj$h]r7cdocutils.nodes row r8)r9}r:(hUh}r;(h]h]h]h]h]uhj4h]r<(cdocutils.nodes entry r=)r>}r?(hUh}r@(h]h]h]h]h]uhj9h]rAh)rB}rC(hX ComponentrDhj>hjhhh}rE(h]h]h]h]h]uhK3h]rFhX ComponentrGrH}rI(hjDhjBubaubahUentryrJubj=)rK}rL(hUh}rM(h]h]h]h]h]uhj9h]rNh)rO}rP(hX AMSDK 8.0rQhjKhjhhh}rR(h]h]h]h]h]uhK3h]rShX AMSDK 8.0rTrU}rV(hjQhjOubaubahjJubj=)rW}rX(hUh}rY(h]h]h]h]h]uhj9h]rZh)r[}r\(hXProcessor SDK 1.0r]hjWhjhhh}r^(h]h]h]h]h]uhK3h]r_hXProcessor SDK 1.0r`ra}rb(hj]hj[ubaubahjJubehUrowrcubahUtheadrdubcdocutils.nodes tbody re)rf}rg(hUh}rh(h]h]h]h]h]uhj$h]ri(j8)rj}rk(hUh}rl(h]h]h]h]h]uhjfh]rm(j=)rn}ro(hUh}rp(h]h]h]h]h]uhjjh]rqh)rr}rs(hXU-Boot Bootloaderrthjnhjhhh}ru(h]h]h]h]h]uhK5h]rvhXU-Boot Bootloaderrwrx}ry(hjthjrubaubahjJubj=)rz}r{(hUh}r|(h]h]h]h]h]uhjjh]r}h)r~}r(hXv2014.07rhjzhjhhh}r(h]h]h]h]h]uhK5h]rhXv2014.07rr}r(hjhj~ubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjjh]rh)r}r(hXv2014.07rhjhjhhh}r(h]h]h]h]h]uhK5h]rhXv2014.07rr}r(hjhjubaubahjJubehjcubj8)r}r(hUh}r(h]h]h]h]h]uhjfh]r(j=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX Linux Kernelrhjhjhhh}r(h]h]h]h]h]uhK7h]rhX Linux Kernelrr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX3.14.26rhjhjhhh}r(h]h]h]h]h]uhK7h]rhX3.14.26rr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX3.14.26rhjhjhhh}r(h]h]h]h]h]uhK7h]rhX3.14.26rr}r(hjhjubaubahjJubehjcubj8)r}r(hUh}r(h]h]h]h]h]uhjfh]r(j=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX Toolchainrhjhjhhh}r(h]h]h]h]h]uhK9h]rhX Toolchainrr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX!Linaro GCC 4.7 2013.03 hard-floatrhjhjhhh}r(h]h]h]h]h]uhK9h]rhX!Linaro GCC 4.7 2013.03 hard-floatrr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hX!Linaro GCC 4.7 2013.03 hard-floatrhjhjhhh}r(h]h]h]h]h]uhK9h]rhX!Linaro GCC 4.7 2013.03 hard-floatrr}r(hjhjubaubahjJubehjcubj8)r}r(hUh}r(h]h]h]h]h]uhjfh]r(j=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hXGUI Development Platformrhjhjhhh}r(h]h]h]h]h]uhK;h]rhXGUI Development Platformrr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hXQt 4.8rhjhjhhh}r(h]h]h]h]h]uhK;h]rhXQt 4.8rr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhjh]rh)r}r(hXQt 5.4rhjhjhhh}r(h]h]h]h]h]uhK;h]rhXQt 5.4rr}r (hjhjubaubahjJubehjcubj8)r }r (hUh}r (h]h]h]h]h]uhjfh]r (j=)r}r(hUh}r(h]h]h]h]h]uhj h]rh)r}r(hX Graphics SDKrhjhjhhh}r(h]h]h]h]h]uhK=h]rhX Graphics SDKrr}r(hjhjubaubahjJubj=)r}r(hUh}r(h]h]h]h]h]uhj h]rh)r}r(hX 05.01.01.02r hjhjhhh}r!(h]h]h]h]h]uhK=h]r"hX 05.01.01.02r#r$}r%(hj hjubaubahjJubj=)r&}r'(hUh}r((h]h]h]h]h]uhj h]r)h)r*}r+(hX 05.01.01.02r,hj&hjhhh}r-(h]h]h]h]h]uhK=h]r.hX 05.01.01.02r/r0}r1(hj,hj*ubaubahjJubehjcubj8)r2}r3(hUh}r4(h]h]h]h]h]uhjfh]r5(j=)r6}r7(hUh}r8(h]h]h]h]h]uhj2h]r9h)r:}r;(hXSupported Platformsr<hj6hjhhh}r=(h]h]h]h]h]uhK?h]r>hXSupported Platformsr?r@}rA(hj<hj:ubaubahjJubj=)rB}rC(hUh}rD(h]h]h]h]h]uhj2h]rEh)rF}rG(hXAM335x and AM437xrHhjBhjhhh}rI(h]h]h]h]h]uhK?h]rJhXAM335x and AM437xrKrL}rM(hjHhjFubaubahjJubj=)rN}rO(hUh}rP(h]h]h]h]h]uhj2h]rQh)rR}rS(hXAM335x and AM437xrThjNhjhhh}rU(h]h]h]h]h]uhK?h]rVhXAM335x and AM437xrWrX}rY(hjThjRubaubahjJubehjcubj8)rZ}r[(hUh}r\(h]h]h]h]h]uhjfh]r](j=)r^}r_(hUh}r`(h]h]h]h]h]uhjZh]rah)rb}rc(hXSupported Hostsrdhj^hjhhh}re(h]h]h]h]h]uhKAh]rfhXSupported Hostsrgrh}ri(hjdhjbubaubahjJubj=)rj}rk(hUh}rl(h]h]h]h]h]uhjZh]rmh)rn}ro(hXUbuntu 12.04 and 14.04rphjjhjhhh}rq(h]h]h]h]h]uhKAh]rrhXUbuntu 12.04 and 14.04rsrt}ru(hjphjnubaubahjJubj=)rv}rw(hUh}rx(h]h]h]h]h]uhjZh]ryh)rz}r{(hXUbuntu 12.04 and 14.04r|hjvhjhhh}r}(h]h]h]h]h]uhKAh]r~hXUbuntu 12.04 and 14.04rr}r(hj|hjzubaubahjJubehjcubehUtbodyrubehUtgrouprubaubh)r}r(hX;Table: AMSDK 8.0 to Processor SDK 1.0 Component Comparisonrhjhjhhh}r(h]h]h]h]h]uhKDhhh]rhX;Table: AMSDK 8.0 to Processor SDK 1.0 Component Comparisonrr}r(hjhjubaubh)r}r(hXtIt is clear from the above that these SDKs are very similar. The biggest difference by far is the transition from Qt 4.8 to Qt 5.4. If you'd like to learn more about this specifically, please see the `Qt 4 to 5 Migration `__. If you have a "headless" system, or don't use Qt, then this is really a "don't care".hjhjhhh}r(h]h]h]h]h]uhKFhhh]r(hXIt is clear from the above that these SDKs are very similar. The biggest difference by far is the transition from Qt 4.8 to Qt 5.4. If you'd like to learn more about this specifically, please see the rr}r(hXIt is clear from the above that these SDKs are very similar. The biggest difference by far is the transition from Qt 4.8 to Qt 5.4. If you'd like to learn more about this specifically, please see the hjubjg)r}r(hXU`Qt 4 to 5 Migration `__h}r(UnameXQt 4 to 5 MigrationjkX;http://processors.wiki.ti.com/index.php/Qt_4_to_5_Migrationh]h]h]h]h]uhjh]rhXQt 4 to 5 Migrationrr}r(hUhjubahjpubhXW. If you have a "headless" system, or don't use Qt, then this is really a "don't care".rr}r(hXW. If you have a "headless" system, or don't use Qt, then this is really a "don't care".hjubeubh)r}r(hXThe rest of the Arago filesystem provided with the SDK was updated as well. Please consult the Software Manifest for specific changes.rhjhjhhh}r(h]h]h]h]h]uhKLhhh]rhXThe rest of the Arago filesystem provided with the SDK was updated as well. Please consult the Software Manifest for specific changes.rr}r(hjhjubaubh)r}r(hUhjhjhhh}r(h]h]h]h]rhvah]rhauhKPhhh]r(h)r}r(hX Documentationrhjhjhhh}r(h]h]h]h]h]uhKPhhh]rhX Documentationrr}r(hjhjubaubh)r}r(hXSince the components are mostly common, the documentation is also very similar. The headings and such have been updated to include the new Processor SDK naming, but the content, except when improved or necessary, is largely the same.rhjhjhhh}r(h]h]h]h]h]uhKRhhh]rhXSince the components are mostly common, the documentation is also very similar. The headings and such have been updated to include the new Processor SDK naming, but the content, except when improved or necessary, is largely the same.rr}r(hjhjubaubeubh)r}r(hUhjhjhhh}r(h]h]h]h]rhah]rh+auhKXhhh]r(h)r}r(hXHardware Platformsrhjhjhhh}r(h]h]h]h]h]uhKXhhh]rhXHardware Platformsrr}r(hjhjubaubh)r}r(hXBoth SDKs support the same hardware platforms from TI. Here's the `list `__ from the Processor SDK, for completeness.hjhjhhh}r(h]h]h]h]h]uhKZhhh]r(hXBBoth SDKs support the same hardware platforms from TI. Here's the rr}r(hXBBoth SDKs support the same hardware platforms from TI. Here's the hjubjg)r}r(hXA`list `__h}r(UnameXlistjkX6Release_Specific_Supported_Platforms_and_Versions.htmlh]h]h]h]h]uhjh]rhXlistrr}r(hUhjubahjpubhX* from the Processor SDK, for completeness.rr}r(hX* from the Processor SDK, for completeness.hjubeubeubh)r}r(hUhjhjhhh}r(h]h]h]h]rhah]rh5auhK_hhh]r(h)r}r(hX Board Portingrhjhjhhh}r(h]h]h]h]h]uhK_hhh]rhX Board Portingrr}r(hjhjubaubh)r}r(hX{One of the major efforts to developing a customer Linux Embedded System is porting the bootloader, U-Boot in this case, and the Linux kernel to a new hardware platform. Since the U-Boot and Kernel sources provided with the Processor SDK 1.0 are identical, this effort is minimal to non-existent. Custom drivers and any other bootloader or kernel code should move over seamlessly.rhjhjhhh}r(h]h]h]h]h]uhKahhh]rhX{One of the major efforts to developing a customer Linux Embedded System is porting the bootloader, U-Boot in this case, and the Linux kernel to a new hardware platform. Since the U-Boot and Kernel sources provided with the Processor SDK 1.0 are identical, this effort is minimal to non-existent. Custom drivers and any other bootloader or kernel code should move over seamlessly.rr}r(hjhjubaubeubh)r}r(hUhjhjhhh}r(h]h]h]h]rhah]rh&auhKihhh]r(h)r}r(hXApplication Developmentrhjhjhhh}r(h]h]h]h]h]uhKihhh]rhXApplication Developmentrr}r(hjhjubaubh)r}r(hX If using the Arago Filesystem provided with the SDK (i.e. you haven't yet used Yocto/Open Embedded to create your own), the specific versions of the packages provided might change slightly. Please consult the Software Manifest for any packages your are concerned with.rhjhjhhh}r(h]h]h]h]h]uhKkhhh]rhX If using the Arago Filesystem provided with the SDK (i.e. you haven't yet used Yocto/Open Embedded to create your own), the specific versions of the packages provided might change slightly. Please consult the Software Manifest for any packages your are concerned with.rr}r(hjhjubaubh)r}r(hXGUI Developmentrhjhjhhh}r (h]r hah]h]h]h]r hSauhNhhh]r hXGUI Developmentr r}r(hjhjubaubh)r}r(hX{As highlighted above, this is the largest change between the two SDKs. If Qt 4.x is used currently, it is possible that adaptation to Qt 5.4 will be necessary. It depends largely on the Qt components used and how they transition to Qt 5.4. Again, please consult the `Qt 4 to 5 Migration Guide `__ for more information.hjhjhhh}r(h]h]h]h]h]uhKshhh]r(hX As highlighted above, this is the largest change between the two SDKs. If Qt 4.x is used currently, it is possible that adaptation to Qt 5.4 will be necessary. It depends largely on the Qt components used and how they transition to Qt 5.4. Again, please consult the rr}r(hX As highlighted above, this is the largest change between the two SDKs. If Qt 4.x is used currently, it is possible that adaptation to Qt 5.4 will be necessary. It depends largely on the Qt components used and how they transition to Qt 5.4. Again, please consult the hjubjg)r}r(hX[`Qt 4 to 5 Migration Guide `__h}r(UnameXQt 4 to 5 Migration GuidejkX;http://processors.wiki.ti.com/index.php/Qt_4_to_5_Migrationh]h]h]h]h]uhjh]rhXQt 4 to 5 Migration Guiderr}r(hUhjubahjpubhX for more information.rr}r (hX for more information.hjubeubeubeubh)r!}r"(hUhjhjhhh}r#(h]h]h]h]r$hah]r%hJauhK{hhh]r&(h)r'}r((hXSummaryr)hj!hjhhh}r*(h]h]h]h]h]uhK{hhh]r+hXSummaryr,r-}r.(hj)hj'ubaubh)r/}r0(hXThe AMSDK that you may be familiar with is getting a new name, the Processor SDK for Linux. This name change paves the way for adding more devices from TI's processor line-up and allow developer's to enjoy the same experience with more options. What seems like a simple name change at this point, will continue to grow to become an extensive software offering covering a broad range of devices, as well as operating systems, examples, tools, and other important components developers need in this fast-paced, time-to-market driven environment. The experience gained will translate nicely to the next project or the next set of challenges, enabling developers to be more efficient and successful.r1hj!hjhhh}r2(h]h]h]h]h]uhK}hhh]r3hXThe AMSDK that you may be familiar with is getting a new name, the Processor SDK for Linux. This name change paves the way for adding more devices from TI's processor line-up and allow developer's to enjoy the same experience with more options. What seems like a simple name change at this point, will continue to grow to become an extensive software offering covering a broad range of devices, as well as operating systems, examples, tools, and other important components developers need in this fast-paced, time-to-market driven environment. The experience gained will translate nicely to the next project or the next set of challenges, enabling developers to be more efficient and successful.r4r5}r6(hj1hj/ubaubh)r7}r8(hXThe migration from the AMSDK to the Processor SDK is expected to be minimal, with a few noted exceptions. It's a great time to explore the "new" AMSDK, and see how it will help solve the challenges faced today, and preparing for those in the future.r9hj!hjhhh}r:(h]h]h]h]h]uhKhhh]r;hXThe migration from the AMSDK to the Processor SDK is expected to be minimal, with a few noted exceptions. It's a great time to explore the "new" AMSDK, and see how it will help solve the challenges faced today, and preparing for those in the future.r<r=}r>(hj9hj7ubaubeubeubeubehUU transformerr?NU footnote_refsr@}rAUrefnamesrB}rCUsymbol_footnotesrD]rEUautofootnote_refsrF]rGUsymbol_footnote_refsrH]rIU citationsrJ]rKhhU current_linerLNUtransform_messagesrM]rNUreporterrONUid_startrPKU autofootnotesrQ]rRU citation_refsrS}rTUindirect_targetsrU]rVUsettingsrW(cdocutils.frontend Values rXorY}rZ(Ufootnote_backlinksr[KUrecord_dependenciesr\NU rfc_base_urlr]Uhttps://tools.ietf.org/html/r^U tracebackr_Upep_referencesr`NUstrip_commentsraNU toc_backlinksrbjJU language_codercUenrdU datestampreNU report_levelrfKU _destinationrgNU halt_levelrhKU strip_classesriNhNUerror_encoding_error_handlerrjUbackslashreplacerkUdebugrlNUembed_stylesheetrmUoutput_encoding_error_handlerrnUstrictroU sectnum_xformrpKUdump_transformsrqNU docinfo_xformrrKUwarning_streamrsNUpep_file_url_templatertUpep-%04druUexit_status_levelrvKUconfigrwNUstrict_visitorrxNUcloak_email_addressesryUtrim_footnote_reference_spacerzUenvr{NUdump_pseudo_xmlr|NUexpose_internalsr}NUsectsubtitle_xformr~U source_linkrNUrfc_referencesrNUoutput_encodingrUutf-8rU source_urlrNUinput_encodingrU utf-8-sigrU_disable_configrNU id_prefixrUU tab_widthrKUerror_encodingrUUTF-8rU_sourcerjUgettext_compactrU generatorrNUdump_internalsrNU smart_quotesrU pep_base_urlrU https://www.python.org/dev/peps/rUsyntax_highlightrUlongrUinput_encoding_error_handlerrjoUauto_id_prefixrUidrUdoctitle_xformrUstrip_elements_with_classesrNU _config_filesr]Ufile_insertion_enabledrU raw_enabledrKU dump_settingsrNubUsymbol_footnote_startrKUidsr}r(h`jhvjhcjyhdj hej|hjhhjhij# hjhkjohljhfhhnjhojhjj`htj hsjhjhjthj2hjhj<h}j1hjhj h|jThhhjhjh~jhj hujhjhzjhyj|hxj6hwjThpjS hj(hjhjS hj hmjhhjh{j hrjc hjhqj hj hjhjhjShj2hj hj/hjhjhjghj!hjhj hjzhajhbjhj hj' hju hj hjhjvhjIhjhj!hjghjU hjhgjhjhjhjo hj=uUsubstitution_namesr}rhhh}r(h]h]h]Usourcejh]h]uU footnotesr]rUrefidsr}rub.