Skip to content

docs(linux): J722S 11.2 release documentation updates #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Puyush45 wants to merge 2 commits into from
Closed

docs(linux): J722S 11.2 release documentation updates #712

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cde4c81
docs(linux): Add J722S NFS boot limitation and remove outdated NFS co…
Puyush45 May 21, 2026
63cfd2b
docs(linux): J722s: Update meta-tisdk and meta-edgeai tag for 11.2 re…
Puyush45 May 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions source/devices/J7_Family/linux/Release_Specific_Release_Notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -498,6 +498,7 @@ Linux Known Issues
"LCPD-15708","j721e-vlab","J721E: vlab: MMC1 not functional",""
"LCPD-14249","j721e-vlab","PCI kernel oops seen between rc7 and rc8 of 4.19",""
"LCPD-9981","j721e-vlab,omapl138-lcdk","Some LTP's memory management tests fail due to low amount of free memory",""
"LCPD-47749","j722s_evm-fs,j722s_evm-se","NFS boot fails when EthFW is enabled on MCU2_0 R5F core due to CPSW Proxy Client driver circular dependency",""

@uditkumarti uditkumarti May 22, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this capture in PR of @gehariprasath ? #706

@gehariprasath gehariprasath May 22, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be created yesterday by @Puyush45 . So it doesn't appear in my list.

@Puyush45 Puyush45 May 22, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the bug is created recently. do anything else needs to be taken care?


|
Expand Down
48 changes: 0 additions & 48 deletions source/linux/How_to_Guides/Host/Moving_Files_to_the_Target_System.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,51 +21,3 @@ Switching the SD card back and forth from the EVM to the SD card reader
is time consuming during development. Using a NFS during development is
the preferred method and makes moving files between the host and target
trivial.

.. rubric:: File System on Network File System (NFS)
:name: file-system-on-network-file-system-nfs

When the target file system is served from the Linux development host
machine it is trivial to move files between the host and target. The
NFS directory is set up on the host machine by the SDK installer. The
default location in the SDK environment is :file:`${PSDK_PATH}/targetNFS`
This could vary depending on the version of the SDK and how it was installed.
An :command:`ls -l` of this directory in the host system will show what will be the root
directory of the target when it boots up.

.. code-block:: console

user@U1004GT:~/ti-sdk-AM3715-evm-4.0.0.0/filesystem$ pwd
/home/user/ti-sdk-AM3715-evm-4.0.0.0/filesystem
user@U1004GT:~/ti-sdk-AM3715-evm-4.0.0.0/filesystem$ ls -l
total 68
drwxr-xr-x 2 root root 4096 Mar 9 2018 bin
drwxr-xr-x 4 root root 4096 Mar 9 2018 boot
drwxr-xr-x 2 root root 4096 Mar 9 2018 dev
drwxr-xr-x 55 root root 4096 Mar 9 2018 etc
drwxr-xr-x 4 root root 4096 Mar 9 2018 home
drwxr-xr-x 10 root root 4096 Mar 9 2018 lib
lrwxrwxrwx 1 root root 19 Mar 9 2018 linuxrc -> /bin/busybox.nosuid
drwxr-xr-x 2 root root 4096 Mar 9 2018 media
drwxr-xr-x 2 root root 4096 Mar 9 2018 mnt
drwxr-xr-x 14 root root 4096 Mar 9 2018 opt
dr-xr-xr-x 2 root root 4096 Mar 9 2018 proc
drwxr-xr-x 2 root root 4096 Mar 9 2018 run
drwxr-xr-x 2 root root 4096 Mar 9 2018 sbin
drwxr-xr-x 2 root root 4096 Mar 9 2018 srv
dr-xr-xr-x 2 root root 4096 Mar 9 2018 sys
drwxrwxrwt 2 root root 4096 Mar 9 2018 tmp
drwxr-xr-x 12 root root 4096 Mar 9 2018 usr
drwxr-xr-x 9 root root 4096 Mar 9 2018 var

So from the perspective of the host, the target filesystem is just a
sub-directory of the host. If the file is in :file:`./targetNFS` on the host,
then the same file will show up in the root directory of the target
after the target boots into the NFS. And if the file is in a
subdirectory of :file:`./targetNFS` (example :file:`./targetNFS/{sub-dir}/`) then it will
show up in the /sub-dir directory of the target after the target boots
into the NFS.

The top level makefile of the TI SDK supports an install target that
will copy applications into the NFS of the SDK. See the README file at
the top level of the SDK for information about the install target.