Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 21 Aug 2018 02:51 PM by  William Deninger
Mainstream DM37x Linux
 17 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Adam Ford



Advanced Member


Posts:788
Advanced Member


--
22 Jul 2016 12:55 PM

    A beta BSP has been released for the DM3730 / AM3703 Torpedo and Torpedo Wireless products with mainstream Linux 4.4.x kernel.   This BSP has not been fully tested, not all features on the baseboard are enabled, but it can provide a nice starting point for users wishing to have a newer kernel and libraries.  This BSP uses vanilla kernel with a device tree for the Torpedo + Wireless which can be modified to support the non-wireless Torpedo.  Kernel 4.4 was selected because of its long-term-support in the Linux community.

     

    With this release the following new files have been posted:

    • DM37x Mainstream Linux BSP User Guide
    • Virtual Machine SDK for the DM37x Mainstream  Linux BSP
    • Virtual Machine SDK for the DM37x Mainstream Linux BSP ReadMe

    You can download these documents from the DM3730 / AM3703 Torpedo or Torpedo Wireless, product pages on Logic PD's support site, or at:

    https://support.logicpd.com/ProductDownloads/DM3730AM3703TorpedoSOM.aspx

    https://support.logicpd.com/ProductDownloads/DM3730AM3703TorpedoWirelessSOM.aspx

     

    As new features are added, the above documents will be updated.

     


    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    12 Aug 2016 10:28 AM
    Kernel 4.6 has an updated device tree that supports PWM LCD backlight, and touch screen, but it doesn't have long-term-support.

    If you need those features, you may want to consider migrating to 4.6, but 4.4.x is probably more stable.

    adam

    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    12 Aug 2016 09:56 PM
    To enable the sleep mode, remove the 'no console suspend' boot argument from the optargs in U-boot.

    This will permit the main core to sleep and the SOM will sleep.

    To further enhance the sleep mode:

    make sure twl4030-pwrbutton is loaded so you can wake it.

    Mount debugfs: mount -t debugfs none /sys/kernel/debug

    Enable off mode: echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode

    Now Sleep

    echo 1 > /sys/power/state

    Press S2 to wake



    Anton Strootz



    New Member


    Posts:5
    New Member


    --
    31 Aug 2016 08:07 AM

    Hi Adam,

    I am wondering if the DM3730 HSUSB via PMIC is supported in mainstream 4.4.9.

    When I boot the demo image it on my SOMDM3730-31-2780AKCR mounted on the Launcher board, I do not see any USB devices other than the following:

    Bus 003 Device 001: ID 1d6b:0002  
    Bus 002 Device 001: ID 1d6b:0002  
    Bus 001 Device 001: ID 1d6b:0001  

    which are the host controller and the root hub, even when I do connect a USB device to the OTG port on the Launcher board.

    Were you able to see a USB device connected to the OTG port (not to the ISP1763 host)?

    Thanks!

    Anton


    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    31 Aug 2016 08:14 AM
    You'll need to modprobe one of the gadgets for the OTG to work. I used g_zero, but the ethernet or storage gadgets should work too. Once a gadget has been loaded, the OTG can also act as a host.

    It appears to be by design, but I am not sure why they made that decision.

    For more details, see: http://processors.wiki.ti...ular_testing_on_MUSB

    adam



    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    31 Aug 2016 08:17 AM
    FYI, the kernel has been updated in the mainstream community to 4.4.19. You can download the incremental patches here:

    https://cdn.kernel.org/pub/linux/kernel/v4.x/incr/

    For example patch-4.4.9-10 makes the jump from 4.4.9 to 4.4.10 and patch-4.4.10-11 makes the jump from 4.4.10 to 4.4.11, and so forth.

    If you download them all, you can patch your kernel to 4.4.19 9 or whatever the latest 4.4.y kernel is

    adam

    Anton Strootz



    New Member


    Posts:5
    New Member


    --
    31 Aug 2016 08:42 AM

    Thanks Adam,

    Works as a charm!


    Anton Strootz



    New Member


    Posts:5
    New Member


    --
    31 Aug 2016 02:08 PM

    Adam,

     

    also, do you happen to know about support of the Ethernet controller on the Launcher by the mainstream?

    I am trying to pump high-speed isochronous USB data through USB, and while getting -121 on every usb_submit_urb(), which would require its own investigation, I see that wifi eventually disconnects.

    Just want to connect to the SOM reliably and launch the application in an SSH session to separate dmesg output from the application output.

    Thanks!

    Anton


    Anton Strootz



    New Member


    Posts:5
    New Member


    --
    31 Aug 2016 02:29 PM
    Adam,

    sorry for asking. Found that it is indeed supported. Just needed to add eth0 to /etc/network/interfaces

    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    31 Aug 2016 02:59 PM
    I am glad you found it so quickly. I have done some Ethernet benchmarks showing it was over 94Mb and on a 100MBbconnection, I thought that was pretty good.

    If you have any issues with it, please let me know, and I'll look into or or push the question to the open source community.

    I am not sure what to think about the WiFi or the USB. If you can give me some more background on your setup or what you're trying to do, I can try to replicate it.

    adam

    Anton Strootz



    New Member


    Posts:5
    New Member


    --
    31 Aug 2016 03:23 PM
    I am trying to connect a Point Grey Chameleon3 camera to the Torpedo. It is a USB3 camera, but it does work on USB2 (tested it on Intel Edison). The default app tries to grab images at the max possible framerate (which is about 16 in this case, as the resolution is 2048x1536x8bit). It probably still clogs USB, so I am going to set the frame rate to a lower value and turn on binning to lower the resolution. That might just work. I will keep you posted.

    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    10 Oct 2016 11:02 AM
    Running some benchmarks using the GCC cross compiled for the Corext a8, hard floating point, an 800MHz DM3730, we found some preliminary benchmarking numbers encouraging:


    Running the speedtest app for VFPv3, the preminiary performance gains appear to be around 1.6 to 1.9x faster than the BSP2.4-4 running the CodeSourcery 2009 toolchain.

    Running the speedtest app for NEON, the preminiary performance gains appear to be around 1.2 to 1.6x faster

    The Dhrystone 10000000 benchmark is approximately 1.7x faster

    Whetstone 60000 yielded a 3x improvement in performance.

    Linpack yielded a 1.2x improvement in performance.


    Overall the 4.4.y Kernel with GCC 5.4 build from Buildroot seems to be a good setup.

    adam

    Scott



    New Member


    Posts:8
    New Member


    --
    03 Oct 2017 03:15 PM

    I have a similar question with respect to OTG and a gadget driver (e.g. g_zero).

    Clearly when I modprobe the g_zero driver I'm able to get MUSB into host mode. The user guide published in 8/17 suggests that the driver can included in the kernel. That said with the usb gadget drivers included in the kernel, it does not appear that MUSB enters host mode. I there something else that must be configured to make this work?

     

     


    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    04 Oct 2017 07:16 AM
    Scott,

    I'm going to have to look into this. I am not 100% certain, but I believe if you have multiple gadget devices is doesn't know which to load since they can only only one at a time. Are you looking to only do host mode without the gadget support or did you have a specific gadget you wanted to use?

    adam

    Scott



    New Member


    Posts:8
    New Member


    --
    04 Oct 2017 09:21 AM

    I changed the configuration to host mode only and was able to mount the root file system during boot.


    Adam Ford



    Advanced Member


    Posts:788
    Advanced Member


    --
    06 Oct 2017 01:53 PM
    If you decide you want to go back to using the modules, /etc/init.d/ has a series of scripts. You can add your own to modprobe or rmmod on startup and shutdown. This gives you a little flexibility for some gadgets who require extra parameters when they are loaded.

    The the scripts are supposed to be loaded numerically, (ie S01 loads before S10), so if you have certain dependencies, you should be able to load them in the correct order by naming the scripts with higher or lower names.

    adam

    William Deninger



    New Member


    Posts:22
    New Member


    --
    21 Aug 2018 01:22 PM
    Hi Adam,
    When I try to place the Torpedo DM3730 SOM (w WIFI) into a sleep state under Mainstream Linux 2018.05.x using 4.4.76-rt, I receive a write error to /sys/power/state. I had modified the u-boot environment by removing "no console suspend" from bootargs (not optargs) using nand unlock, setenv ... and saveenv. Has there been a change in the branch 2018.05.x that might cause this?? If not, I'll go though and reattempt it by reverting the RT patch on the kernel. (The RT patch is small and quite simple).
    -William

    # modprobe twl4030-pwrbutton
    # mount -t debugfs none /sys/kernel/debug
    # echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode
    # echo 1 > /sys/power/state
    sh: write error: Invalid argument


    William Deninger



    New Member


    Posts:22
    New Member


    --
    21 Aug 2018 02:51 PM

    (change to u-boot optargs yeilds same result)

    -W

    You are not authorized to post a reply.