€cdocutils.nodes document q)q}q(U nametypesq}qXfaqsqNsUsubstitution_defsq}qUparse_messagesq ]q Ucurrent_sourceq NU decorationq NUautofootnote_startq KUnameidsq}qhUfaqsqsUchildrenq]qcdocutils.nodes section q)q}q(U rawsourceqUUparentqhUsourceqXc/home/gtbldadm/nightlybuilds/processor-sdk-doc/source/linux/Foundational_Components_Kernel_FAQs.rstqUtagnameqUsectionqU attributesq}q(Udupnamesq]Uclassesq]Ubackrefsq ]Uidsq!]q"haUnamesq#]q$hauUlineq%KUdocumentq&hh]q'(cdocutils.nodes title q()q)}q*(hXFAQsq+hhhhhUtitleq,h}q-(h]h]h ]h!]h#]uh%Kh&hh]q.cdocutils.nodes Text q/XFAQsq0…q1}q2(hh+hh)ubaubcdocutils.nodes comment q3)q4}q5(hXGhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_kernel_FAQshhhcdocutils.nodes reprunicode q6X8source/linux/Foundational_Components/Kernel/FAQs.rst.incq7…q8}q9bhUcommentq:h}q;(U xml:spaceqh/XGhttp://processors.wiki.ti.com/index.php/Processor_Linux_SDK_kernel_FAQsq?…q@}qA(hUhh4ubaubcdocutils.nodes paragraph qB)qC}qD(hXV**Q: How to let Linux not load kernel modules automatically during system boot time?**qEhhhh8hU paragraphqFh}qG(h]h]h ]h!]h#]uh%Kh&hh]qHcdocutils.nodes strong qI)qJ}qK(hhEh}qL(h]h]h ]h!]h#]uhhCh]qMh/XRQ: How to let Linux not load kernel modules automatically during system boot time?qN…qO}qP(hUhhJubahUstrongqQubaubhB)qR}qS(hXm**A:** Add the module name into the modprobe blacklist in file */etc/modprobe.d/modprobe.conf*. For example,qThhhh8hhFh}qU(h]h]h ]h!]h#]uh%Kh&hh]qV(hI)qW}qX(hX**A:**h}qY(h]h]h ]h!]h#]uhhRh]qZh/XA:q[…q\}q](hUhhWubahhQubh/X: Add the module name into the modprobe blacklist in file q^…q_}q`(hX: Add the module name into the modprobe blacklist in file hhRubcdocutils.nodes emphasis qa)qb}qc(hX*/etc/modprobe.d/modprobe.conf*h}qd(h]h]h ]h!]h#]uhhRh]qeh/X/etc/modprobe.d/modprobe.confqf…qg}qh(hUhhbubahUemphasisqiubh/X. For example,qj…qk}ql(hX. For example,hhRubeubcdocutils.nodes literal_block qm)qn}qo(hX9# cat /etc/modprobe.d/modprobe.conf blacklist musb_am335xhhhh8hU literal_blockqph}qq(h unbind root@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc#hhhh8hhph}qž(h unbind root@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc#q …q¡}q¢(hUhhœubaubhB)q£}q¤(hXto enable it again,q¥hhhh8hhFh}q¦(h]h]h ]h!]h#]uh%Kh&hh]q§h/Xto enable it again,q¨…q©}qª(hh¥hh£ubaubhm)q«}q¬(hXroot@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc# echo 48838000.rtc > bind [ 7792.863975] omap_rtc 48838000.rtc: already running [ 7792.869822] omap_rtc 48838000.rtc: rtc core: registered 48838000.rtc as rtc1 root@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc#hhhh8hhph}q­(h bind [ 7792.863975] omap_rtc 48838000.rtc: already running [ 7792.869822] omap_rtc 48838000.rtc: rtc core: registered 48838000.rtc as rtc1 root@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc#q¯…q°}q±(hUhh«ubaubhv)q²}q³(hUhhhh8hhyh}q´(h]h]h ]h!]h#]uh%K&h&hh]qµh|)q¶}q·(hUhKhh²hh8hh%h}q¸(h]h]h ]h!]h#]uh%Kh&hh]ubaubcsphinx.ext.ifconfig ifconfig q¹)qº}q»(hUhhhh8hUifconfigq¼h}q½(Uexprq¾X(CONFIG_part_family in ('General_family')h!]h ]h]h]h#]uh%K(h&hh]q¿(hB)qÀ}qÁ(hXc**Q: Without SD card in K2H/E, what options are availabe for Keystone-2 platforms to boot kernel?**qÂhhºhh8hhFh}qÃ(h]h]h ]h!]h#]uh%K*h&hh]qÄhI)qÅ}qÆ(hhÂh}qÇ(h]h]h ]h!]h#]uhhÀh]qÈh/X_Q: Without SD card in K2H/E, what options are availabe for Keystone-2 platforms to boot kernel?qÉ…qÊ}qË(hUhhÅubahhQubaubhB)qÌ}qÍ(hXM**A:** Keystone-2 platforms support the following ways of booting the kernel:qÎhhºhh8hhFh}qÏ(h]h]h ]h!]h#]uh%K,h&hh]qÐ(hI)qÑ}qÒ(hX**A:**h}qÓ(h]h]h ]h!]h#]uhhÌh]qÔh/XA:qÕ…qÖ}q×(hUhhÑubahhQubh/XG Keystone-2 platforms support the following ways of booting the kernel:qØ…qÙ}qÚ(hXG Keystone-2 platforms support the following ways of booting the kernel:hhÌubeubcdocutils.nodes bullet_list qÛ)qÜ}qÝ(hUhhºhh8hU bullet_listqÞh}qß(UbulletqàX*h!]h ]h]h]h#]uh%K.h&hh]qácdocutils.nodes list_item qâ)qã}qä(hX Network Boot hhÜhh8hU list_itemqåh}qæ(h]h]h ]h!]h#]uh%Nh&hh]qçhB)qè}qé(hX Network Bootqêhhãhh8hhFh}që(h]h]h ]h!]h#]uh%K.h]qìh/X Network Bootqí…qî}qï(hhêhhèubaubaubaubhB)qð}qñ(hXšNetowrk Boot is to boot the kernel from network which downloads the kernel, boot monitor, and dtb images from TFTP server and uses NFS mounted filesystem.qòhhºhh8hhFh}qó(h]h]h ]h!]h#]uh%K0h&hh]qôh/XšNetowrk Boot is to boot the kernel from network which downloads the kernel, boot monitor, and dtb images from TFTP server and uses NFS mounted filesystem.qõ…qö}q÷(hhòhhðubaubhB)qø}qù(hX¤This requires the TFTP and NFS servers set up first. The u-boot scripts assume TFTP and NFS servers are on the same system and the IP address is set in "server_ip".qúhhºhh8hhFh}qû(h]h]h ]h!]h#]uh%K3h&hh]qüh/X¤This requires the TFTP and NFS servers set up first. The u-boot scripts assume TFTP and NFS servers are on the same system and the IP address is set in "server_ip".qý…qþ}qÿ(hhúhhøubaubhB)r}r(hXœThe prebuilt kernel, boot monitor, and dtb files are located in /board-support/prebuilt_images folder. The filesystem tarballs are the .tar.xz files and in /filesystem folder. The filesystem needs to be extracted from the tarball to the NFS mount point, e.g. /nfs/k2e_fs. The corresponding NFS mount point needs to be exported on server through /etc/exports.rhhºhh8hhFh}r(h]h]h ]h!]h#]uh%K6h&hh]rh/XœThe prebuilt kernel, boot monitor, and dtb files are located in /board-support/prebuilt_images folder. The filesystem tarballs are the .tar.xz files and in /filesystem folder. The filesystem needs to be extracted from the tarball to the NFS mount point, e.g. /nfs/k2e_fs. The corresponding NFS mount point needs to be exported on server through /etc/exports.r…r}r(hjhjubaubhB)r}r (hXPTo boot from network, the following u-boot environment variables need to be set:r hhºhh8hhFh}r (h]h]h ]h!]h#]uh%K;h&hh]r h/XPTo boot from network, the following u-boot environment variables need to be set:r …r}r(hj hjubaubhm)r}r(hXÍ=> setenv boot net => setenv server_ip => setenv tftp_root => setenv nfs_root => saveenv => boothhºhh8hhph}r(h setenv boot net => setenv server_ip => setenv tftp_root => setenv nfs_root => saveenv => bootr…r}r(hUhjubaubhÛ)r}r(hUhhºhh8hhÞh}r(hàX*h!]h ]h]h]h#]uh%KFh&hh]rhâ)r}r(hX UBI Boot hjhh8hhåh}r(h]h]h ]h!]h#]uh%Nh&hh]rhB)r}r (hXUBI Bootr!hjhh8hhFh}r"(h]h]h ]h!]h#]uh%KFh]r#h/XUBI Bootr$…r%}r&(hj!hjubaubaubaubhB)r'}r((hX$UBI boot is the default setting which boots kernel using the UBIFS filesystem on the NAND. K2H/E platforms have NAND programmed for out-of-box demo. If the NAND image is corrupted, it can be re-programmed using prebuilt UBI image (.ubi files) in /filesystem folder.r)hhºhh8hhFh}r*(h]h]h ]h!]h#]uh%KHh&hh]r+h/X$UBI boot is the default setting which boots kernel using the UBIFS filesystem on the NAND. K2H/E platforms have NAND programmed for out-of-box demo. If the NAND image is corrupted, it can be re-programmed using prebuilt UBI image (.ubi files) in /filesystem folder.r,…r-}r.(hj)hj'ubaubhB)r/}r0(hXKExecute the following u-boot scripts to re-program the NAND with UBI image:r1hhºhh8hhFh}r2(h]h]h ]h!]h#]uh%KLh&hh]r3h/XKExecute the following u-boot scripts to re-program the NAND with UBI image:r4…r5}r6(hj1hj/ubaubhm)r7}r8(hX`/* Download the UBI image from TFTP server */ /* Beware of the UBI image size not to exceed the NAND capacity */ => setenv server_ip => setenv name_ubi => setenv tftp_root => run get_ubi_net /* Program NAND with the downloaded image */ => run burn_ubihhºhh8hhph}r9(h setenv server_ip => setenv name_ubi => setenv tftp_root => run get_ubi_net /* Program NAND with the downloaded image */ => run burn_ubir;…r<}r=(hUhj7ubaubhB)r>}r?(hXqTo boot kernel using UBIFS filesystem on the NAND, the u-boot environment variable "boot" needs to be set to ubi:r@hhºhh8hhFh}rA(h]h]h ]h!]h#]uh%KYh&hh]rBh/XqTo boot kernel using UBIFS filesystem on the NAND, the u-boot environment variable "boot" needs to be set to ubi:rC…rD}rE(hj@hj>ubaubhm)rF}rG(hX%=> setenv boot ubi => saveenv => boothhºhh8hhph}rH(h setenv boot ubi => saveenv => bootrJ…rK}rL(hUhjFubaubhÛ)rM}rN(hUhhºhh8hhÞh}rO(hàX*h!]h ]h]h]h#]uh%Kah&hh]rPhâ)rQ}rR(hX RAMFS boot hjMhh8hhåh}rS(h]h]h ]h!]h#]uh%Nh&hh]rThB)rU}rV(hX RAMFS bootrWhjQhh8hhFh}rX(h]h]h ]h!]h#]uh%Kah]rYh/X RAMFS bootrZ…r[}r\(hjWhjUubaubaubaubhB)r]}r^(hX-RAMFS boot is similar to Network boot which downloads kernel, boot monitor, and dtb images from TFTP server. The difference from Network boot is that it uses a compressed cpio archive file, not the NFS mounted filesystem through netowrk. The cpio archive is downloaded to the Kernel RAM space instead.r_hhºhh8hhFh}r`(h]h]h ]h!]h#]uh%Kch&hh]rah/X-RAMFS boot is similar to Network boot which downloads kernel, boot monitor, and dtb images from TFTP server. The difference from Network boot is that it uses a compressed cpio archive file, not the NFS mounted filesystem through netowrk. The cpio archive is downloaded to the Kernel RAM space instead.rb…rc}rd(hj_hj]ubaubhB)re}rf(hXNThe compressed cpio archive is not included in the Processor SDK, but can be created from the released filesystem. The size of the released filesystem has increased beyond 80MB. As a result, special attention needs to be on the filesystem size used to create the cpio archive. The filesystem needs to be under 80MB for use with RAMFS.rghhºhh8hhFh}rh(h]h]h ]h!]h#]uh%Kgh&hh]rih/XNThe compressed cpio archive is not included in the Processor SDK, but can be created from the released filesystem. The size of the released filesystem has increased beyond 80MB. As a result, special attention needs to be on the filesystem size used to create the cpio archive. The filesystem needs to be under 80MB for use with RAMFS.rj…rk}rl(hjghjeubaubhB)rm}rn(hXwOn the host machine where the Processor SDK is installed, issue the following commands to create the cpio archive file:rohhºhh8hhFh}rp(h]h]h ]h!]h#]uh%Kkh&hh]rqh/XwOn the host machine where the Processor SDK is installed, issue the following commands to create the cpio archive file:rr…rs}rt(hjohjmubaubhm)ru}rv(hXÛhost$ mkdir target_fs host$ cd target_fs host$ tar xf /filesystem/arago-base-tisdk-image-k2e-evm.tar.xz host$ find . | cpio -H newc -o > ../target_fs.cpio host$ cd .. host$ gzip target_fs.cpiohhºhh8hhph}rw(h/filesystem/arago-base-tisdk-image-k2e-evm.tar.xz host$ find . | cpio -H newc -o > ../target_fs.cpio host$ cd .. host$ gzip target_fs.cpiory…rz}r{(hUhjuubaubhB)r|}r}(hX“The target_fs.cpio.gz file needs to be copied to the TFTP directory and be used for RAMFS boot. The u-boot environment variables need to be set as:r~hhºhh8hhFh}r(h]h]h ]h!]h#]uh%Kvh&hh]r€h/X“The target_fs.cpio.gz file needs to be copied to the TFTP directory and be used for RAMFS boot. The u-boot environment variables need to be set as:r…r‚}rƒ(hj~hj|ubaubhm)r„}r…(hXÃ=> setenv boot ramfs => setenv server_ip => setenv tftp_root => setenv name_fs target_fs.cpio.gz => saveenv => boothhºhh8hhph}r†(h setenv boot ramfs => setenv server_ip => setenv tftp_root => setenv name_fs target_fs.cpio.gz => saveenv => bootrˆ…r‰}rŠ(hUhj„ubaubeubeubahUU transformerr‹NU footnote_refsrŒ}rUrefnamesrŽ}rUsymbol_footnotesr]r‘Uautofootnote_refsr’]r“Usymbol_footnote_refsr”]r•U citationsr–]r—h&hU current_liner˜NUtransform_messagesr™]ršUreporterr›NUid_startrœKU autofootnotesr]ržU citation_refsrŸ}r Uindirect_targetsr¡]r¢Usettingsr£(cdocutils.frontend Values r¤or¥}r¦(Ufootnote_backlinksr§KUrecord_dependenciesr¨NU rfc_base_urlr©Uhttps://tools.ietf.org/html/rªU tracebackr«ˆUpep_referencesr¬NUstrip_commentsr­NU toc_backlinksr®Uentryr¯U language_coder°Uenr±U datestampr²NU report_levelr³KU _destinationr´NU halt_levelrµKU strip_classesr¶Nh,NUerror_encoding_error_handlerr·Ubackslashreplacer¸Udebugr¹NUembed_stylesheetrº‰Uoutput_encoding_error_handlerr»Ustrictr¼U sectnum_xformr½KUdump_transformsr¾NU docinfo_xformr¿KUwarning_streamrÀNUpep_file_url_templaterÁUpep-%04drÂUexit_status_levelrÃKUconfigrÄNUstrict_visitorrÅNUcloak_email_addressesrƈUtrim_footnote_reference_spacerljUenvrÈNUdump_pseudo_xmlrÉNUexpose_internalsrÊNUsectsubtitle_xformrˉU source_linkrÌNUrfc_referencesrÍNUoutput_encodingrÎUutf-8rÏU source_urlrÐNUinput_encodingrÑU utf-8-sigrÒU_disable_configrÓNU id_prefixrÔUU tab_widthrÕKUerror_encodingrÖUUTF-8r×U_sourcerØhUgettext_compactrÙˆU generatorrÚNUdump_internalsrÛNU smart_quotesr܉U pep_base_urlrÝU https://www.python.org/dev/peps/rÞUsyntax_highlightrßUlongràUinput_encoding_error_handlerráj¼Uauto_id_prefixrâUidrãUdoctitle_xformrä‰Ustrip_elements_with_classesråNU _config_filesræ]Ufile_insertion_enabledrçˆU raw_enabledrèKU dump_settingsréNubUsymbol_footnote_startrêKUidsrë}rìhhsUsubstitution_namesrí}rîhh&h}rï(h]h!]h ]Usourcehh]h#]uU footnotesrð]rñUrefidsrò}róub.