• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 318 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM5729: AM5729 BeagleBone AI opencl-init: could not get device IDs

Daniil Maltsev
Prodigy 30 points
Part Number: AM5729

I've already asked 2 questions connected with running darknet with OpenCL on BeagleBone AI AM5729 Debian image (am57xx-eMMC-flasher-debian-10.9-lxqt-tidl-armhf-2021-05-28-6gb.img.xz) from (https://rcn-ee.net/rootfs/bb.org/testing/2021-05-28/) and I handled previous issues :

  1. TIOCL WARNING: Opening Linux shared memory: No such file or Directory.
  2. TIOCL FATAL: The TI Multicore Tools daemon (/usr/bin/ti-mctd) is not running. To start daemon, rm /dev/shm/HeapManager (if exists); ti-mctd. Re-run application. Refer User Guide for details. Aborted

And then I had one more : ti-mct-daemon.service does not exist.

I installed darknet with guide from isowa (https://iblog.isowa.io/2020/04/29/darknet-in-opencl-on-beagleboard-ai/), however I did not installed extra packages, only ocl-icd-opencl-dev and in src/opencl.h wrote #define CL_TARGET_OPENCL_VERSION 120 .

Then I called my custom nn YOLOv4 with sudo ./darknet detector test..... And have a new issue : opencl_init: could not get device IDs. I really need help badly, tried to find answer in the internet, however I failed in my attempts.

Hope to get answer really fast.

  • 0
    TI__Expert 3705 points

    Hi Daniil,

        I am not sure I understand the connection between YOLOv4 or darknet with OpenCL.  Is darknet implemented with OpenCL kernels?  From the "isowa guide" that you linked, it seems the guide was using OpenCL on Arm.   The OpenCL you had issues are from TI's OpenCL product.  TI's OpenCL product only supports DSP and EVE as devices.

    -Yuan