Source: Fira BarcelonaīARCELONA, Spain - Qualcomm Technologies Inc., a subsidiary of Qualcomm Inc., today announced at the Mobile World Congress here its Qualcomm Robotics RB3 Platform – the company’s first integrated, comprehensive offering designed specifically for robotics. The following lines should be added to device/linaro/dragonboard/manifest.xml: Īs usual, this is only a part of the whole picture: to really enable the Dragonboard 845c AOSP phone capabilities, a native RIL implementation suitable for the modem in use should be added, usually provided by the modem vendor.Ī reference implementation of the RIL based on AT commands, though a bit outdated, can be found in hardware/ril/ qmi_wwan with Dragonboardīy default the Dragonboard 845c does not support /dev/cdc-wdm device creation, so if you are going to use a Qualcomm modem with qmi_wwan the change db845c: Add usbmisc support is needed (see also sysfs qmi_wwan files writing in AOSP native code).Qualcomm made its RB3 announcement at the 2019 Mobile World Congress. In this example I will use 1.4 for radio and 1.2 for nfig. Since Dragonboard is supported in master, a possible way is to use the version suggested for latest official version completely available in AOSP. Those versions should also be in sync with the ones needed by the Android version to be built. The last step is to change the radio and nfig HAL versions to the ones supported by the native RIL implementation you are using. Should be added to the networkAttributes string array. Then, customize the overlay found in device/linaro/dragonboard/overlay/frameworks/base/core/res/res/values/config.xml changing lines
To $(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base_telephony.mk) in file device/linaro/dragonboard/db845c.mk change line $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk) Enabling phone capabilities on Dragonboard 845cĪs usual, the first step is to derive the db845c main makefile from a telephony makefile, e.g. The main drawback for the Dragonboard is the price, a few hundreds dollars more than the Hikey.īuild steps for AOSP and kernel are really straightforward, so that it’s super-easy to have a working setup. Dragonboard 845c AOSP support in master has been in a very good state since a while, so it’s time to change my AOSP reference board from the Hikey960 to the Dragonboard and start enabling its phone capabilities.īesides having better specs than the Hikey960, the Dragonboard has an important edge, that is the possibility of having at the same time both host and device capabilities through USB, very useful for debugging issues through adb.
0 kommentar(er)
