What to do if your Minimorph doesn’t appear as a device on your Linux host

Tagged: 

This topic contains 0 replies, has 1 voice, and was last updated by  alastair 5 years ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #30981

    alastair
    Moderator

    When connected to your Linux host PC via a USB cable, your Minimorph should appear as /dev/ttyACM0.

    If it doesn’t try checking the cable, the USB device notes and restarting the cdc module on your host.

    Wrong cable

    The Minimorph has a USB OTG-compliant port. You must use a cable with a Mini B connector (as supplied with the Minimorph).

    USB device nodes not accessible

    The host system must be able to access the USB device nodes created for the Minimorph.

    A udev file suitable for adding the device nodes is supplied with the SDK.

    Copy 61-imgtec-slaveboot.rules to /etc/udev/rules.d/.

    Make sure this file is readable by all users, and then reconnect or reset the board for it to take effect. As an alternative to setting up this udev rule you could manually chmod a+rw the appropriate USB device node (the tool will output its name if opening fails).

    cdc_acm needs restarting

    Restart the cdc_acm module on your host system:


    # sudo /sbin/modprobe –r cdc_acm
    # sudo /sbin/modprobe cdc_acm

    cdc modules absent

    If you have rebuilt your Minimorph’s kernel and filesystem , you need to copy the g_cdc.ko cdc module into your filesystem before rebuilding the kernel.

Viewing 1 post (of 1 total)
You must be logged in to reply to this topic.