• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 334 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.

Linux/AM5728: SDK build issues

Dermot Murphy
Intellectual 895 points
Part Number: AM5728

Tool/software: Linux

Hi,

Attempting to compile & install modules using Processor SDK Linux 4.3 - install doesn't appear to work

I'm trying to rebuild the kernel, modules and device tree binaries by following these steps:

  • make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- distclean
  • make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- tisdk_am57xx-evm_defconfig
  • make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage
  • make ARCH=arm CROSS_COMPILE=../../linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf- am57xx-beagle-x15-revb1.dtb
  • make ARCH=arm CROSS_COMPILE=../../linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf- modules

This appears to complete with no issues.  However, when I go to install the modules:
  • export CROSS_COMPILE=arm-linux-gnueabihf-
  • sudo make ARCH=arm  INSTALL_MOD_PATH=/home/dmurphy/my_build modules_install

Unfortunately, the "sudo make ARCH=arm INSTALL_MOD_PATH=/media/rootfs modules_install" command from the link below doesn't actually install the modules in the INSTALL_MOD_PATH.

http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components.html#kernel 

In fact, to run the command with sudo, I have to change the command to avoid gcc being picked up instead of the arm cross compiler:

sudo bash -c ' export CROSS_COMPILE=../../linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf- ; make ARCH=arm INSTALL_MOD_PATH=/home/dmurphy/my_build/modules/ modules_install'

Regardless of whether I use sudo or not to make modules_install, nothing ends up in the INSTALL_MOD_PATH directory.  After some time, the Make just ends abruptly with the following output:

...

CC sound/soc/generic/snd-soc-simple-card-utils.mod.o
LD [M] sound/soc/generic/snd-soc-simple-card-utils.ko
CC sound/soc/generic/snd-soc-simple-card.mod.o
LD [M] sound/soc/generic/snd-soc-simple-card.ko
CC sound/soc/omap/snd-soc-omap-hdmi-audio.mod.o
LD [M] sound/soc/omap/snd-soc-omap-hdmi-audio.ko
CC sound/usb/snd-usb-audio.mod.o
LD [M] sound/usb/snd-usb-audio.ko
CC sound/usb/snd-usbmidi-lib.mod.o
LD [M] sound/usb/snd-usbmidi-lib.ko
dmurphy@tibuilder:~/ti-processor-sdk-linux-am57xx-evm-04.03.00.05/board-support/linux-4.9.69+gitAUTOINC+9ce43c71ae-g9ce43c71ae$

Any assistance would be greatly appreciated.

Thanks,

Dermot

  • 0
    TI__Guru**** 170625 points
    Dermot,

    These modules should be install in root filesystem that has the expected structure. You can not install these on a empty folder, like my_build_modules.

    Please try to install in SD card rootfs or Ethernet rootfs (targetNFS).

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Intellectual 895 points
    Hey Pavel,

    Thanks - that makes some sense for sure. I'll put the SD card from the BB X15 in to my build host first (presumably that's why sudo is required?) rather than build to a new directory. The reason I did that is because I thought I'd have to run the create-sdcard.sh script again and point to custom locations as opposed to pre-built binaries.

    I'll post back just to confirm everything is OK once I've completed.

    Regards,
    Dermot
  • 0 in reply to Dermot Murphy
    TI__Guru**** 170625 points
    Dermot,

    Yes, we need sudo as we will install on SD card rootfs.

    You can also try with targetNFS, which will be created by the {PSDK}/setup.sh script.

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Intellectual 895 points

    Thanks Pavel,

    I ran the setup.sh script already although I didn't use the targetNFS directory directly. I thought maybe that's where the sdcard-setup.sh script pulls in the rootfs from if I choose not to use pre-built.

    Cheers,
    Dermot