Home > Debian, Hardware, Linux, Linux 4.x, Qualcomm Snapdragon, Testing, Video > Debian on DragonBoard 410c Development Board

Debian on DragonBoard 410c Development Board

I purchased Qualcomm DragonBoard 410c development board last year, and first tested it and run some benchmark on the 96Boards compliant hardware with Android. I found that it was still work-in-progress, and decided to wait before trying Debian on the board. I’ve now done so, and will report by experience installing Debian Linux, playing with the board, and running Phoronix benchmarks to compare it to other ARM Linux boards.

Installing Debian on DragonBoard 410c

The first challenge is to navigate through the documentation that is not always clear or up-to-date. I eventually ended up on DragonBoard 410c Wiki on Github.

DragonBoard_410c_Debian_Android_Opearting_SystemsYou then have to decided which image you want. While there are two official operating systems with Android and Debian, you can three “entities” releasiong their own images. For Debian specifically, you have the Linaro image, and Reference Platform Build (RPB) image. I could not find any changelog or known issues with the former, but the latter as its own Wiki with the latest release being RPB 16.03 (March 2016), and the next one scheduled to be RPB 16.06 in June.

That’s the current list of known issues

  • bug 285 USB host doesn’t detect any plugged devices
  • bug 121 [RPB] Cannot soft power off or shutdown db410c
  • bug 284 [RPB] Dragon board Display sleep not working
  • bug 289 [RPB] USB devices don’t work after reboot
  • bug 207 [RPB] Bluetooth does not work on Dragon board debian
  • bug 153 [RPB] Missing information about hwpack usage

USB host not working did not inspire confidence, so I first tested the Linaro image. The (other) Wiki points to the “latest version”, but the link would point to Linaro Debian 16.02 release, while I could find a more recent Linaro Debian 16.04 which I downloaded in a terminal:


I used a micro SD card to install it. If you use Windows, simply use Win32DiskImager, but in computer running Linux or in Windows via Windows subsystem for Linux, you may want to do it in the terminal. First check the SD card device with lsblk. Mine was /dev/sdb, but your may be different, and I use /dev/sdX in the command below tp flash the Debian installer to a micro SD card:


Now remove the micro SD card from your computer and insert it in to the board, set the jumper to boot from SD card on the DragonBoard 410c, and connect the power. I could see LED 1 blinking, but nothing on my HDMI TV. Last time, I did not  manage to make the serial console (requiring a 1.8V USB to TTL board or cable) using Hardkernel ODROID board, so I went to the support forums, and after several minutes of reading, I found that the RPB image is recommended, as well as a clear explanation between the Linaro and RPB images:

Use the Reference Platform Build instead of the Linaro release. The Reference Platform is an integrated build with support for multiple boards, and that is where all engineering effort is going. The Linaro build is the old single-platform image that we’re not working on anymore.

The reference platform will run on all 96boards CE (Consumer Edition) and EE (Enterprise Edition), while the Linaro image is built specifically for a given board, and they are not really working on it. [Update: This answer was specific to Hikey board, and for DragonBoard 410c there are two images provided by Qualcomm Landing Team and the Reference Platform team]

So let’s start again from scratch using the RPB image, and download the bootloader, Linux kernel and rootfs to my Ubuntu computer:


Now find a micro USB to USB cable to connect to DragonBoard 410c, install fastboot…


.. and check the device is detected:


Good. After making sure the jumper switch is set to 0000 on the board again, we can  extract the three files, and install Debian as follows:


That was a lot of commands to install the operating system… Now you can unplug the board, remove the micro USB cable, and connect the power again. After a few seconds, you should see the kernel log, and eventually LXDE desktop environment.

Click to Original Size

Click to Original Size

You’ll be asked to configure WiFi, and you’re basically done.

DragonBoard 410c Debian System Info

I’ve then run a few command to learn more about the image and system:


One of the main advantage of 96Boards should be recent Linux version,and that’s exactly what we have here with Linux 4.4 running on the board. Out of a total of 866MB reported RAM, 64MB is free, and the 6.9GB rootfs has 4.8 GB available to the user. Snapdragon 410 SoC is correctly reported as being a quad core Cortex A53 (0xd03) processor.

I used file utility to make sure a 64-bit rootfs is being used here:


Finally, there’s a bunch of modules pre-loaded on the board:

Testing Debian on DragonBoard 410c

The thing that often do not work on ARM Linux board are 3D graphics and hardware video decoding, so I’ve specifically tested these two, and also played with the pre-installed Chromium browser.

If I understand correctly the debian image comes with Freedreno open source graphics driver, and if that’s the case I have the first ever platform with working open source 3D graphics drivers:


So that means both framebuffer and X11 3D graphics acceleration are working. Nice !

I also tried to play Tuxracer as it was part of the board’s test results provided by Linaro.


It works, but it’s so slow that it’s barely playable (see video below).

I installed VLC to play 1080op h.264 videos, but based on the CPU usage the system is clearly using software decoding, and there’s no audio via HDMI. I’ve asked about those two issues on the forums about 24 hours ago, but I have yet to get a reply.

Chromium loads OK, but I did notice some freezes during use, and YouTube will struggle at full screen at 1080p, in similar way to many other low end ARM Linux platforms.

DragonBoard 410c Linux Benchmarks

Let’s install the latest version of Phoronix…


…and run some benchmarks to compare against other development boards:


After over 3 hours the results are in. Bear in mind that the board does not have heatsink, just a metallic shield, and this may affects the performance. It’s also running an OS with a 64-bit ARM rootfs, while platforms like Raspberry Pi 3 features a 64-bit processor running 32-bit code.

Click to Enlarge

Click to Enlarge

I like to check John the Ripper for multi-threaded performance.

DragonBoard_410c_Phoronix_John_The_RipperWhile FLAC audio encoding is nice to single threaded performance.

DragonBoard_410c_Phoronix_FLAC

In theory the CPU performance of Snapdragon 410 and Broadcom BCM2837 (as found in RPi 3) should be equal since both are quad core Cortex A53 processors @ 1.2 GHz, but for some reasons DragonBoard 410c is a little slower in the multi-threaded benchmark, and quite faster during FLAC audio encoding likely due to software differences (Aarch64 vs Aarch32).

You can find the full results @ http://openbenchmarking.org/result/1605068-GA-1604204GA12

  1. May 7th, 2016 at 00:10 | #1

    Excellent review, looks like the end-user experience could use some documentation and workflow cleanup, but seems like the software itself is maturing and coming along nicely.

  2. blu
    May 7th, 2016 at 01:00 | #2

    Excellent review indeed! This part in particular brought a tear to my eye:

    ‘If I understand correctly the debian image comes with Freedreno open source graphics driver, and if that’s the case I have the first ever platform with working open source 3D graphics drivers’

    I thought I’d never live to see the day. Upstream kernels and OSS GL stacks – the way those devices were meant to be run. /raises teacup

    @cnxsoft, can you comment on the heat dissipation of the board – does it come with a sink, and do the CPU cores throttle notably?

  3. blu
    May 7th, 2016 at 01:35 | #3

    Hey, that’s a r0p0 part – the very first A53 revision! It features some funky errata, like the this one: http://comments.gmane.org/gmane.comp.compilers.clang.scm/109670

  4. Karl Johnson
    May 7th, 2016 at 02:19 | #4

    Will you be testing Android?

  5. May 7th, 2016 at 09:07 | #5

    @Karl Johnson
    I’ve shortly played with Android last December @ http://www.cnx-software.com/2015/11/21/dragonboard-410c-development-board-quick-start-guide-and-android-benchmarks/

    If you mean a review like for TV boxes, then I don’t have plan for this. I think that board is mostly interesting for app development with the latest Android version.

  6. May 7th, 2016 at 09:10 | #6

    @blu
    You can see what the board looks like @ http://www.cnx-software.com/wp-content/uploads/2015/11/96Boards_Power_Adapter.jpg

    So no proper heatsink. I think it’s throttling a little based on John the Ripper results, but I have not checked it formally. RPI monitor would be a nice thing to run, but I’m not sure it supports that board.

    I did try to check the temp with an IR thermometer, and temp was only about 45 C, but the metallic shield is a bit shiny, so it may have skewed the results.

  7. Ricardo
    May 7th, 2016 at 09:35 | #7

    Sorry for the confusion at the documentation side, it’s a lot better but still not perfect. The RPB is a general effort that Linaro is doing for the multiple boards we support, in a way to exercise the idea of a common kernel and rootfs, which is why we recommend it.

    On the other side, we also have another Debian build for DB410c, which is maintained by the Qcom Landing Team. That build can be found at https://builds.96boards.org/releases/dragonboard410c/linaro/debian. The message in the forum recommending RPB and saying that the Linaro build is not supported was only for HiKey, for DB410c that build is still active.

    I know it is confusing, but currently we have 2 Debian builds for DB410c, one maintained by the Qcom Landing Team and the other part of the Reference Platform Project (which consumes a lot from what the Qcom Landing Team also provides, but tries to make it general and common across other boards).

    And thanks a lot for your post, really nice to see the results (and we expect performance to improve quite a bit with the next releases).

  8. Ricardo
    May 7th, 2016 at 09:37 | #8

    Regarding the huge amount of commands to flash, that is only required for a clean flash (or when switching between Debian and Android). After that is done, you can keep updating only the boot and rootfs images (via fastboot).

  9. tkaiser
    May 7th, 2016 at 16:30 | #9

    @cnxsoft
    If /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq is available RPi-Monitor will already graph throttling behaviour. My first steps when trying to support a new board to get thermal and voltage values if available are then as follows:

  10. May 11th, 2016 at 11:21 | #10

    I’ve been asked to test Retroarch game emulator:

    But it won’t build:

  11. gouchi
    May 11th, 2016 at 15:46 | #11

    FFmpeg is needed to record or live streaming video you can disable it for now by adding –disable-ffmpeg

    ./configure –enable-kms –enable-egl –disable-ffmpeg && make -j4

    Thank you for your test.

  12. May 11th, 2016 at 16:39 | #12

    @gouchi
    Same problem after disabling ffmpeg. Does RetroArch build on other ARM platforms?

  13. gouchi
    May 11th, 2016 at 18:02 | #13

    @cnxsoft
    Yes it compiled fine on other ARM platform.

    Can you git pull to get last update because there was buildfix for compiling without ffmpeg just 3 hours ago 😉

    git pull
    make clean
    ./configure –enable-kms –enable-egl –disable-ffmpeg && make -j4

  14. May 11th, 2016 at 19:24 | #14

    @gouchi
    It’s OK now. It runs.

  15. gouchi
    May 11th, 2016 at 19:33 | #15

    @cnxsoft
    Great !

    You can check this tutorial for getting started :
    http://www.libretro.com/index.php/getting-started-with-retroarch

    Don’t forget to get assets and core from Online Updater.

  16. May 11th, 2016 at 20:06 | #16

    @gouchi
    Accessing the Core Updater does nothing. The other part Core Info Files, Assets, etc… can all be downloaded. But since I can’t load any cores I’m stuck.

  17. May 11th, 2016 at 20:24 | #17

    @cnxsoft
    @gouchi
    One reason could be that aarch64/arm64 is not supported, only armhf and armel -> http://buildbot.libretro.com/nightly/linux/

  18. gouchi
    May 11th, 2016 at 20:35 | #18

    @cnxsoft
    I see.

    Can you try to compile test gl core ?
    cd RetroArch/cores/libretro-test-gl
    make -j2

    Then you can Load the core (testgl_libretro.so) and then Start core to see if it is working.

  19. Beta-Pictoris
    May 13th, 2016 at 00:19 | #19

    About your audio/video issue, I see there is an answer on the forum. Have you tested it ?

    Otherwise, there is a solution for cooling and boosting your dragonboard’s performance, I think: https://www.element14.com/community/community/designcenter/single-board-computers/blog/2016/02/01/cooling-the-dragonboard-410c-and-ifc6410p. what do you think about it ?

    Can you test supertuxkart and tell us if it works well ? 🙂

  20. May 14th, 2016 at 11:47 | #20

    @gouchi
    I’ve built it but it won’t show in the list of cores.

    @Beta-Pictoris
    Yes, I had already tried that image, but it would not boot at all.
    That’s hack has a massive heatsink, even bigger than the board. 🙂

    I’ve moved on to other boards right now, so I’m not sure when I’ll be able to do further tests.

  21. gouchi
    May 15th, 2016 at 02:12 | #21

    @cnxsoft

    The default path for the cores is ~/.config/retroarch/cores so you need to copy testgl_libretro.so to this path. You can load it with Load Core then start it with Start Core.

  22. blu
    May 16th, 2016 at 16:54 | #22

    @cnxsoft Can you, please, check if there are any OpenCL libs on the fs? Something along:

    ldconfig -p | grep OpenCL

  23. May 17th, 2016 at 09:41 | #23

    @blu
    Nothing.

  24. May 17th, 2016 at 09:44 | #24

    @gouchi
    All I get is a black window with the title “RetroArch TestCore GL v1”.

  25. May 17th, 2016 at 10:06 | #25

    @Beta-Pictoris
    I’ve installed SuperTuxKart, and it was quite playable, quite smoother than TuxRacer.

  26. blu
    May 17th, 2016 at 13:33 | #26

    @cnxsoft Thanks. Oh well, some day.. Baby steps.

  27. gouchi
    May 17th, 2016 at 15:53 | #27

    @cnxsoft

    Can you try to launch it with :
    retroarch –verbose -L ~/.config/retroarch/cores/testgl_libretro.so > /tmp/log.txt 2>&1

    And paste the log.txt to hastebin ?

    Thank you very much for your tests.

  28. Beta-Pictoris
    May 18th, 2016 at 04:42 | #28

    @cnxsoft
    Ok, thanks.

    It seems Raspberry pi 3 could be used as mini-pc: http://www.pcworld.com/article/3057888/computers/raspberry-pi-3-review-the-revolutionary-35-mini-pc-cures-its-biggest-headaches.html
    Do you think the same think for dragonboard ?

  29. May 18th, 2016 at 09:17 | #29

    @Beta-Pictoris
    Both boards have about the same performance, so if RPi 3 is acceptable as a mini Desktop PC to you, Dragonboard will be too.

    If you are used to faster machines, the user experience may still be frustrating at times.

  30. November 19th, 2016 at 23:32 | #30

    Has anyone gotten gamepads/joysticks to work on the Dragonboard? I’m porting my SmartGear multi-system emulator to it and the code runs fine, but the system won’t recognize any USB gamepads or bluetooth gamepads. If someone would like to test my game emulator, please let me know ([email protected]

  31. November 20th, 2016 at 10:24 | #31

    @Larry Bank
    Enabling joystick support is often just a matter of enabling drivers in the kernel. The post http://www.cnx-software.com/2012/09/11/building-kernel-modules-for-allwinner-a10-devices-android/ might help as it shows a list of drivers to enable for joystick support. It was written in 2012, so there might be newer drivers to enable for more recent joysticks but it should give an idea of what to do.

  32. November 26th, 2016 at 10:25 | #32

    Kodi on DragonBoard 410c -> http://www.96boards.org/project/kodidragonboard/
    No source code updates for nearly a year though.

  1. No trackbacks yet.