• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 596 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

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

Original question:

AM6442: On AM64X Linux SDK - on TI cgit, where are the serial drivers that can interact with the SoC UART4 peripheral?

AM6442: AM64x Linux-RT SDK 10.1 -- Kernel make failure (after menuconfig) to make Image

Jim Mrowca
Genius 4132 points
Part Number: AM6442


Tool/software:

URGENT make compile issue

I followed Bin's guidance per  (17) AM6442: On AM64X Linux SDK - on TI cgit, where are the serial drivers that can interact with the SoC UART4 peripheral? - Processors forum - Processors - TI E2E support forums

Followed use manual section 3.2.1.3 up to 3.2.1.5.1 i.e. to 3.2.1. Users Guide — Processor SDK AM64X Documentation


build_UART4_rt_mconf_dts_031325.txt

attached is the log with the "little endian" Error that does not make sense 

I need to get an image so I can map the USART4 into an updated device tree .dts file

  • 0
    Genius 4132 points

    Path to /usr/bin/make

    GNU Make 4.3

    attached (.config)   in DOTconfig.zip  file (generated after interactive "make ... menuconfig") - 214k uncompressed

    DOTconfig.zip

  • 0 in reply to Jim Mrowca
    Genius 4132 points

    Attached my k3-am642-evm.dts (not yet compiled, for reference) in attached zip - 23k uncompressed

     5102.k3-am642-evm.zip

  • 0 in reply to Jim Mrowca
    TI__Guru 70040 points

    The subject owner is OoO this week. Please expect delayed response till next week.

  • 0
    TI__Guru**** 170051 points

    Hi Jim,

    Jim Mrowca said:
    Followed use manual section 3.2.1.3 up to 3.2.1.5.1 i.e. to 3.2.1. Users Guide — Processor SDK AM64X Documentation

    Instead of following the manual process in this documentation, you can just run command 'make linux' in the SDK top level directory to build the kernel, then you shouldn't have this 'little endian' problem.

  • 0 in reply to Bin Liu
    Genius 4132 points

    Bin: 

    I was prompted SEVERAL times (see lines 1433  to   3624  )  before I got an Error 2

    . build_UART4_rt_mconf_dts_031925.txt

  • 0 in reply to Jim Mrowca
    TI__Guru**** 170051 points

    jmrowca@jmrowca-Kabylake-Client-platform:~/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel-6.6.58+git-ti-rt$ make linux

    Bin Liu said:
    Instead of following the manual process in this documentation, you can just run command 'make linux' in the SDK top level directory to build the kernel, then you shouldn't have this 'little endian' problem.

    I said to just run "make linux" in the SDK top level directory. Not in the kernel source directory.

  • 0 in reply to Bin Liu
    Genius 4132 points

    Hi Bin:

    I did get further, but now 7 errors (see bottom photo from a Notepad++ search) towards the end of the log attached. Cannot tell if an Image is generated - where?  

    makelinuxattempt032025.txt

    Do I need to reinstall AM64X SDK v10.1 before retrying?

    regards, Jim

  • 0 in reply to Jim Mrowca
    TI__Guru**** 170051 points

    Jim,

    You still use your own way to build kernel, but I don't know what your runsetup4kern.bash script does. But anyway the build log shows kernel build is complete, but u-boot build failed.

    The generated kernel image should be ~/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel-6.6.58+git-ti-rt/arch/arm64/boot/Image.

    The u-boot build failure should be due to:

    error: command 'swig' failed: No such file or directory

    which can be fixed by:

    $ sudo apt install swig

  • 0 in reply to Bin Liu
    Genius 4132 points

    Bin:

    first my runsetup4kern.bash script is this: 

    ---------------------

    export SDK_INSTALL_DIR=/home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04
    export CROSS_COMPILE_64="${SDK_INSTALL_DIR}/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-"
    export SYSROOT_64="${SDK_INSTALL_DIR}/linux-devkit/sysroots/aarch64-oe-linux"
    export CC_64="${CROSS_COMPILE_64}gcc --sysroot=${SYSROOT_64}"
    export CROSS_COMPILE_32="${SDK_INSTALL_DIR}/k3r5-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-oe-eabi/arm-oe-eabi-"

    -----------------------

    After installing swig,

    Now I have a DIFFERENT set of 4 errors as seen in the attached log

    build_UART4_rt_mconf_dts_032025.txt

    later

    Jim

  • 0 in reply to Jim Mrowca
    TI__Guru**** 170051 points

    binman: Unknown entry type 'ti-board-config' in node '/binman/board-cfg/ti-board-config' (expected etype/ti_board_config.py, error 'No module named 'yamllint''

    Use the following command to install the component on your PC.

    $ pip install yamllint

  • 0 in reply to Bin Liu
    Genius 4132 points

    Bin:

    A different end problem error showed up this time. (Portions of logfile attached)

    ------------------------

    LD [M] net/qrtr/qrtr-tun.ko
    LD [M] net/qrtr/qrtr-mhi.ko
    make[1]: Leaving directory '/home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel-6.6.58+git-ti-rt'
    # Build FitImage
    cd /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel* ; cp arch/arm64/boot/Image.gz ./linux.bin ; cd ..
    cp /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/prebuilt-images/am64xx-evm/fitImage-its-am64xx-evm /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel*
    mkimage -r -f /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-linux-kernel*/fitImage-its-am64xx-evm -k /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/ti-u-boot*/arch/arm/mach-k3/keys -K /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/u-boot-build/a53/arch/arm/dts/k3-am642-evm.dtb /home/jmrowca/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04/board-support/built-images/fitImage
    /bin/sh: 1: mkimage: not found
    make: *** [makerules/Makefile_linux:13: linux] Error 127

    real 13m22.446s
    user 77m25.344s
    sys 8m21.772s
    jmrowca@jmrowca-Kabylake-Client-platform:~/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04$

    ---------------------------

    build_UART4_rt_mconf_dts_032125.txt

  • 0 in reply to Jim Mrowca
    TI__Guru**** 170051 points
    Jim Mrowca said:
    /bin/sh: 1: mkimage: not found

    package is missing. You could just google the error message to find out what package should be installed.

  • 0 in reply to Bin Liu
    Genius 4132 points

    Well Bin, the image finally did compile! Relaxed

    For the record, that mkimage is located via this find & install process (indicating some dependencies) :

    ==========================

    jmrowca@jmrowca-Kabylake-Client-platform:~/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04$ mkimage
    Command 'mkimage' not found, but can be installed with:
    sudo apt install u-boot-tools
    jmrowca@jmrowca-Kabylake-Client-platform:~/ti/ti-processor-sdk-linux-rt-am64xx-evm-10.01.10.04$ sudo apt install u-boot-tools
    [sudo] password for jmrowca:
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    The following additional packages will be installed:
    device-tree-compiler libfdt1 libubootenv-tool libubootenv0.1
    The following NEW packages will be installed:
    device-tree-compiler libfdt1 libubootenv-tool libubootenv0.1 u-boot-tools

    ===========================

    I'll go through my notes to summarize what needed for the AM64x Linux SDK v11 documentation (on a separate e2e)

    thanks

    Jim