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.

error when build android for omap 5432 evm ES2.0


when i  Building TI WLAN Drivers  

root@ubuntu:~/myspace/5AJ.1.5/mydroid/hardware/ti/wlan/mac80211/compat_wl18xx# make ARCH=arm
make -C /kernel/android-3.4 M=/root/myspace/5AJ.1.5/mydroid/hardware/ti/wlan/mac80211/compat_wl18xx modules
make: *** /kernel/android-3.4: No such file or directory. Stop.
make: *** [modules] Error 2

anyone can help me? thank you for advance

  • Hi Luyen,

    You can make sure that your environment is set up correctly:

    (Below information is from http://omapedia.org/wiki/Panda5AJ.1.5_Release_Notes#Build_PC_setup)

    Issue the following commands:

    - From your work directory (5AJ.1.5 folder): 

    export YOUR_PATH=$PWD
    export MYDROID=${YOUR_PATH}/mydroid
    export PATH=$PATH:${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/
    export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
    export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4
    export KLIB=${KERNEL_DIR}
    export KLIB_BUILD=${KERNEL_DIR}
    

    - From /5AJ.1.5/mydroid/build folder:

      /5AJ.1.5/mydroid/build$ ./envsetup.sh 

    - Then issue the following commands to build:

    cd ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/
    make ARCH=arm
  • hi komal padia

    i have complete build android for omap5432 es.2. but i can see anything on screen, 

    screen /dev/ttyUSB0 115200 such below:

    [ 76.333343] rproc remoteproc0: Booting fw image ducati-m3-core0.xem3, size 13487335
    [ 76.559814] omap-iommu omap-iommu.1: ipu: version 2.1
    [ 76.571716] rproc remoteproc0: remote processor ipu_c0 is now up
    [ 76.579986] virtio_rpmsg_bus virtio24: rpmsg host is online
    [ 76.585845] rproc remoteproc0: registered virtio24 (type 7)
    [ 78.742156] omap-rproc omap-rproc.1: received echo reply from ipu_c0
    [ 78.749237] virtio_rpmsg_bus virtio24: creating channel rpmsg-omx1 addr 0x3c
    [ 78.757415] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
    [ 78.765228] virtio_rpmsg_bus virtio24: creating channel omaprpc addr 0x3b
    [ 80.532379] virtio_rpmsg_bus virtio24: creating channel rpmsg-resmgr addr 0x66
    [ 80.553649] rprm_regulator_request: regulator lookup failed, id 1
    [ 80.560058] rpmsg_resmgr rpmsg74: request for regulator failed: -22
    [ 80.566650] rpmsg_resmgr rpmsg74: resource allocation failed -22!
    [ 80.636260] omap-iommu omap-iommu.1: iommu fault: da 0x268be0 flags 0x0
    [ 80.643524] rproc remoteproc0: fatal error #49 detected in ipu_c0: error type mmufault
    [ 80.652221] omap-iommu omap-iommu.1: ipu: errs:0x00000002 da:0x00268be0 pgd:0xd216c008 *pgd:px95b00002
    [ 80.668609] rproc remoteproc0: trying to recover ipu_c0
    [ 80.674163] rpmsg_omx rpmsg-omx1: rpmsg omx driver is removed
    [ 80.681243] omap-rproc omap-rproc.1: omap rproc ipu_c0 crashed
    [ 80.687377] rproc remoteproc0: fatal error #50 detected in ipu_c0: error type device exception
    [ 80.708007] rproc remoteproc0: stopped remote processor ipu_c0
    [ 80.756103] rproc remoteproc0: powering up ipu_c0
    [ 80.808715] rproc remoteproc0: Booting fw image ducati-m3-core0.xem3, size 13487335
    [ 81.034484] omap-iommu omap-iommu.1: ipu: version 2.1
    [ 81.046783] rproc remoteproc0: remote processor ipu_c0 is now up
    [ 81.055297] virtio_rpmsg_bus virtio25: rpmsg host is online
    [ 81.061187] rproc remoteproc0: registered virtio25 (type 7)
    [ 83.218383] omap-rproc omap-rproc.1: received echo reply from ipu_c0
    [ 83.225891] virtio_rpmsg_bus virtio25: creating channel rpmsg-omx1 addr 0x3c
    [ 83.234069] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
    [ 83.241760] virtio_rpmsg_bus virtio25: creating channel omaprpc addr 0x3b

  • Hi, Luyen 

    Did you encounter any dss related errors in your boot log?

    and can you manage to get shell prompt after you hit enter right after the boot log. ( you can use minicom or Putty for terminal session)

    Regards, Boyko