百杰科技HelperA64开发板使用手册 - PubYun

HelperA64 development board the user manual

Shenzhen Baijie Technology

Address：306, Building 5, Zone A, Xixiang Internet Industry Base Mobile：+86-13510178868 Mr Chen

1

HelperA64 development board

The user manual

V1.3

2020-08

https://bjkj.en.alibaba.com/

www.szbaijie.cn

https://bjkj.en.alibaba.com/

http://www.szbaijie.cn/

http://www.szbaijie.cn/



Address：#306, Building 5, Zone A, Xixiang Internet Industry Base Mobile：+86-13510178868 Mr Chen

2

The revision history

The date

of

versio

n Revision note

The

author

2017.07.15 0.1 new The

string

2017.12.03 0.2 revised Chen Jun

2018.3.20 0.3 revised Cheng

ShiQiang


ShiQiang


ShiQiang


ShiQiang

2019.1.31 1.0 revised JiZiZiHe

2020.5.26 1.1 revised LiuWei

2020.5.27 1.2 revised JiZiZiHe

2020.8.25 1.3 revised liulei




3

Content The revision history ........................................................................... 2

Content ..................................................................................... 3

1 Introduction of the HelperA64 development board ....................................... 5

1.1 Introduction ......................................................................... 5

1.2 System features ...................................................................... 5

1.3 Hardware resource description ........................................................ 6

1.4 Hardware dimension diagram ........................................................... 8

2 Development board function testing ..................................................... 9

2.1 Xshell terminal simulation tool ................................................................................................................. 9

2.2 Hardware test .................................................................................................................................................... 11

2.2.1 SD card interface test .................................................. 11

2.2.2 Keyboard test ........................................................... 12

2.2.3 Ethernet port test ...................................................... 13

2.2.4 HDMI test ............................................................... 13

2.2.5 USB debugging test ...................................................... 14

2.2.6 WIFI test ............................................................... 14

2.2.7 Touch screen test ....................................................... 15

2.2.8 The mouse test .......................................................... 15

2.2.9 Headphone and speaker interface testing ................................. 16

2.2.10 Camera test ............................................................. 16

3 Develop board burning and writing tools ................................................ 17

3.1 Instal PhoenixSuit ................................................................. 17

3.2 Write the development board firmware using PhoenixSuit ............................................................... 19

3.3 Use PhoenixCard to make the SD card startup disk ........................................................................... 24

4 Compile the source code ............................................................... 27

4.1 Development environment setup ................................................................................................................... 27

4.2 Compiling kernel source code ..................................................................................................................... 28

4.3 Build the android SDK source code .......................................................................................................... 28

4.4 patch ..................................................................................................................................................................... 29

5 The screen operation .................................................................. 30

5.1 Screen adaptation ................................................................... 30

5.2 Modify the startup interface ........................................................ 30

5.3 Switch HDMI display ................................................................. 30

5.4 Modify resolution ................................................................... 31

6 Customize the Linux +qt system based on A64 .......................................... 32

6.1 Compiling the Linux kernel .......................................................... 32

6.2 Transplant dragonboard root file system ............................................. 32

6.3 Compile the QT application .......................................................... 33

6.4 Copy the file through SSH ........................................................... 33

6.5 Execute the Qt program .............................................................. 34

7 Make ubuntu core system .............................................................. 35

7.1 Compile the ubuntu core kernel ...................................................... 35

7.2 Porting the ubuntu core system with a graphical interface ........................... 35




4

7.3 Porting the qt version of ubuntu core ............................................... 35

8 Kernel configuration ............................................................................................................................................ 39

9 HelloWorld for Android apps ........................................................................................................................... 43

9.1.1 Download AndroidStudio .................................................. 43

9.1.2 Android Studio creates the HelloWorld project ........................... 43

9.2 Develop emulations to run Android applications using the Android Emulator.................. 47

9.2.1 Create a virtual appliance .............................................. 47

9.2.2 Run the application in the virtual appliance ............................ 49

9.2.3 Pre-installed APK ........................................ 错误!未定义书签。

10 About technical support ................................................ 错误!未定义书签。

11 About customized services .............................................. 错误!未定义书签。




5

1 Introduction of the HelperA64 development board

1.1 Introduction

HelperA64 development board is the second development board of the Helper series of Baijie technology. It inherits all the excellent features of Helper2416. It is simple, beautiful, stable and efficient.

HelperA64 development board is a low price and high performance quad core cortex-a53 64 bits reference board which is independently developed, produced and sold by our own company. With the latest 64 bit A64 from Allwinner, including abundant resources and interfaces, complete with driving and application software, it is an ideal choice for personal learning and product evaluation for the company.

1.2 System features

CPU: 64 bit 4 core A53 highest frequency: 1.1GHz

Memory: 1GB

Storage: 8G EMMC (MLC not TLC)

Decoding: 1080P@60Hz decoding

Display: support HDMI output 4K@30Hz, 1080P@60hz, LVDS 1366x768@60Hz, MIPI

1920x1080@60Hz, RGB 1920x1080@60Hz

2 -ch high-speed USB HOST, 1-ch high-speed USB OTG

4-ch TTL serial port (can be used as the ordinary IO port)

1-ch 40-pin RGB TTL LCD interface can support all kinds of RGB interface LCD screens, up

to 1920x1200@60Hz

1-ch 20-pin LVDS TTL LCD interface can support all kinds of LVD interface LCD screens, the

highest 1366x768@60Hz

1-ch leads to the TF card interface and 1-ch leads to the SDIO interface

1 -ch CSI camera interface, can do time-sharing before and after double shot, complete power

supply, maximum support of 5M pixels (camera needs to be equipped with another)

1 -ch headphone output

1 -ch LINEOUT output

1 -ch MIC interface

1 -ch PWM, can connect the backlight control

1pc buzzer

5 pcs normal buttons

Built-in USB to serial, directly plug in USB you will see the serial debugging information

1-ch 10/100 base Ethernet interface

1-chl 2.4g WIFI interface

Extended 24-pin IO interface, including 14 3.3v normal IO ports, 1-chl I2C, 4 1.8v normal IO

ports, two 3.3v power supplies and two ground ports

Power supply: DC 5V, battery 3.7v

1-ch speaker output interface, support external 4 -Ohm 2W output




6

1.3 Hardware resource description

○15

○9

○12

○11

○13

○14

○16 ○17 ○19 ○20 ○18

○10

○21

○1 ○29 ○2 ○6 ○7 ○8 ○3

○26

○25

○24

○23

○22

○4

○27

○28 ○5

○30




7

locat

ion describe

○1 Battery socket, single lithium battery, 3.7v

○2 buzzer

○3 USB to the serial port 0, used to check the debugging information

○4 RS232 serial port 0, same as○3

○5 Ttl-com0 (from outside to inside: vcc3.3, uart0-tx, uart0-rx, GND)



○8 WIFI/BT antenna

○9 USB WIFI/BT module (RTL8723BS)

○10 Dual camera interface

○11 40 pin LCD interface, including capacitive touch screen interface (according to

schematic diagram for pin definition)

○12 LVD touch screen with 20 pin interface

○13 SDIO interface

○14 Function keys

○15 Reset button

○16 The power button

○17 24 pin IO outlets (in the figure above, count from the far left, 1, 2 from the outside

to the inside.3, 4.....23, 24.

○18 The microphone

○19 Horn interface (Max. : 4 Ohm 2W)

○20 SIM card

○21 Headphone output port

○22 Usb-otg (generally used for burning programs or debugging)

○23 Extended USB HOST

○24 Gigabit Ethernet interface

○25 HDMI interface

○26 External dc power supply, 5V

○27 4G module PCI-E socket

○28 HelperA64 core board

○29 Dc power switch, does not act on the battery

○30 Backlight for ○12




8

1.4 Hardware dimension diagram




9

2 Development board function testing

The development board is default to burn Android 6.0 system. Firmware Shared on the network disk is firmware\ android_v2_uart0_lcd_7.0.tar.gz, which can be used for burning and writing after decompressing. It can be electrified for hardware system testing, so as to make sure the functional parts of the development board work normally as soon as you get the development board.

2.1 Xshell terminal simulation tool

In the figure in section 1.3 and (to be purchased by yourself) for the serial interface of the

development board.○3 ○4

You can download the Xshell setup board from the website.

First, after connecting the serial port interface of the development board with the USB interface of the PC with the serial port line, open the interface manager port to check whether the serial port exists as shown in the following figure.Here is an example of a serial port for com5.

Then download Xshell from the Internet and install it, click “file -> new”.

Change the “name” in “connection” to new session “com5-“.

Select “SERIAL” under the “protocols” contents.




10

When the protocol set up, select the "Category" contents and select "SERIAL".

The "port" item selects the RS232C serial port number "com5" on the PC.

Under "Baud Rate", Baud Rate is selected, and we choose 115200. Select 8 Bits in "Data Bits"."Stop Bits" select 1 bit.The last two terms are "none".




11

After successfully setting up the serial port, restart the machine and the following information will be printed. At this point you can use the "serial port" to operate the development board. Development board default for android system, if you want to know more about android commands and operations, please search the information by Google.

2.2 Hardware test

The following tests were performed on board hardware installed with the LINUX system provided by the company. All the tests success means the hardware pass the test

2.2.1 SD card interface test

HelperA64 supports an SD card interface.○13 After inserting the SD card, click "Storage & USB" in

"Settings". The SD card will be displayed inside.




12

2.2.2 Keyboard test

The keyboard of the development board is shown in the figure in section 1.3.○14 Each of the five

keys is defined.When the keyboard is pressed, we use the serial session in Xshell to see if the keys have data printing information.If each key has data, the test passes (the information in red mark is the key information).

Note: su is to switch to root user, getevent is to get the event print, it means the keyboard print here.




13

2.2.3 Ethernet port test

The Ethernet interface is shown in the figure in section 1.3.○24 Connect the Ethernet port of the

development board and the PC port with the normal network cable. Then click the browser application in the development board, browse the web, prove that the network and interface tests passed.

You can also enter the following command through the serial port session in Xshell (note: su is to switch root user, ping is to test network connectivity). You can see that if there is a response, if yes, the test passes.

2.2.4 HDMI test

In the figure in section 1.3 is the HDMI interface. The HelperA64 development board interface can

be displayed on the display by inserting the HDMI cable.○25 Below is a screenshot comparing

computer “PC HDMI" and "HelperA64", indicating that the test passed.




14

2.2.5 USB debugging test

The figure in section 1.3 is usb-otg (generally used for burning programs or debugging).○22 After

starting the development board, open the "Settings" and then select "developer options" in the interface, and then select the "USB debugging" button (which is turned on by default).When you open it, you will be prompted with the following message. Select "yes" to perform "ADB debugging" for android, indicating that the test passed.

This port can also be used as our recording port. Please refer to the content in section 3 for detailed recording steps.

Note: please study by yourself and Google for ADB debugging of android. The manual does not cover it.

2.2.6 WIFI test

HelperA64 supports WIFI module. After booting, the development board can pull down the

interface to turn on WIFI and turn off WIFI.○9

You can also enter the following order in Xshell serial port session to switch WIFI, indicating that the test passed.




15

Note: SVC wifi disable means turn off wifi, and SVC wifi enable means turn on wifi.

2.2.7 Touch screen test

HelperA64 supports an RGB interface LCD screen and an LVDS interface LCD screen.○11○12After starting up, the development board can be used in the interface by clicking application or sliding for touch testing.

You can also enter the following command through the serial port session in Xshell, and

touch data will be generated when you touch the screen. Then the test will pass.The action

command is the same as the key test command (su and getevent).

2.2.8 The mouse test

HelperA64 supports two USB HOST interfaces.○23 After starting the development board, you can

use the mouse to click application or slide on the interface for testing.

You can also enter the following command through the serial port session in Xshell. When

you move the mouse, data will be generated. Then the test is passed.The action command is

the same as the key test command (su and getevent).




16

2.2.9 Headphone and speaker interface testing

The speaker jack and headphone jack in the figure in section 1.3.○19○21 When the earphone

and speaker are plugged in, two buttons on the left of the five keys can be clicked to increase or

decrease the volume.○14 You can also download your own videos and music for testing.When you

hear the sound, means it passed the test.

Note: the microphone does not work properly when the headset is plugged in.The microphone works when the speaker is not plugged in or plugged in.

2.2.10 Camera test

The camera interface in the figure in section 1.3 (note: please plug the camera and screen in the

shutdown state).○10 After booting the development board, you can click "camera". if you can take

photos, the test is passed.




17

3 Develop board burning and writing tools

Use PhoenixSuit to burn the program online, in tools\ PhoenixSuit_EN.msi.

3.1 Instal PhoenixSuit

During the installation process, the interface of the installation driver will appear.




18




19

After installation, generate the PhoenixSuit icon on the desktop

3.2 Write the development board firmware using PhoenixSuit

The first time you open the software, an updated interface will appear,you can cancel it.




20

Click one button to brush the machine, then click browse, and select the firmware file to download, such as fireware\ android_v2_uart0_lcd_7.0.tar.gz (need to unzip into img file first),

Burn writing steps:

1、 Burning and writing USB port plugged into the development board (corresponding the

hardware number)○22

2、 Hold down any normal key (corresponding to the hardware number) before starting.○14

3、 Power on to boot the development board (you can also press the reset key after power

on)○15

4、 Press the power key repeatedly (corresponding to the hardware number) (press several

times, usually 3-5 times).○16

5、 The software enters into the following state, release all the keys, and click "yes" to enter the brush mode.

Note: do not disconnect the power supply of the development board, otherwise it may cause the failure of updating the firmware. Wait for a few minutes before downloading. The process shown as below.Restart the development board,It will be a little longer when the fist time too boot.




21




22

Note: due to the cause of Allwinner download the program, sometimes the progress bar will not move after a part of it is gone. In this case, you can just restart the board and repeat the above process.




23

After successful of burning and starting, you can see that the brush tool shows that the device has been connected successfully.

If the state shown above does not appear, the "driver" is not installed successfully. Uninstall the “Android ADB Interface” in “portable device” in “device manager”, as shown below.

Then restart the android system of the development board, and the driver will be loaded

automatically. The following drawing shows that the driver has been loaded successfully.




24

3.3 Use PhoenixCard to make the SD card startup disk

Locate phoenixcard_v310_20130618.rar under tools, download and unzip the phoenixcard_v310_20130618.rar, then go to the installation directory to find the program to run directly.

The interface is as follows:




25

Click "get the character" to automatically search for the card reader's character, and then select the boot disk you want to insert.

When the disk character is found, the mouse click "img file" will appear the img file selection dialog box, the user selects the img firmware to burn and write.

When the corresponding firmware img is selected, switch the burn and write mode to "card bulk production", and then click the "burn" button to burn and write the card, then you can burn the disk you inserted into the SD card startup disk, the following drawing indicates that the burn was successful.

Note: when you do not need to use the SD card startup disk, click "recovery card" to format the SD card startup disk into a normal card.

3.4 SDFormatter formats memory cards

When the card burning program fails to start properly, you need to use SDformatter to format the memory card, then re-burn the image to the memory card with PhoenixCard, and then burn the memory card to the development board with the card

Find Panasonic SDFormatter.7z under Tools directory, download , unzip and go to the

installation directory to find it Can run the program directly. After inserting the memory card, it will be read automatically. If it is not read, click refresh button to read the memory card. After reading the memory card, click Format button, and use default options to format.




26

Please check whether the interface is damaged, whether the memory card is properly inserted and whether there is a loose situation; The following interface will be formatted successfully.




27

4 Compile the source code

This chapter mainly introduces the source code compilation of android 6.0.1 SDK and the

source code compilation of the Linux kernel corresponding to Allwinner, based on the 64-bit

operating system ubuntu14.04 (you can also use 12.04, but it is better not to use the later

version, otherwise you may encounter problems).

4.1 Development environment setup

In order to simplify the development process, I created a virtual machine image of ubuntu 14.04, which I have installed necessary software, as well as a 64-bit GCC compiler (v6.3.0) for Linux.

Installation of virtual machine software vmware12 is very simple, there are corresponding installation files in the share network disk, please install by yourself, virtual machine image in the network disk share directory: tools\vmware12\ub14.04.7z, after decompression can be used.The following section describes the process of configuring the development environment in vmware12.

Open the vmware 12 software, click the menu: file -> open, and select the file corresponding to the uncompressed virtual machine image: Ubuntu 14.04.vmx, as shown below:

I default configuration is a CPU, dual core board, 1 gb of memory, 300 g hardware, you can make appropriate adjustment according to your requirements, such as increasing memory, or increase the CPU core plate number, I use the CPU is the i7 6700 k, you may make a mistake, when running the virtual machine can choose to copy the virtual machine, then automatically configured to your corresponding CPU should be ok.

Then click the button in the vmware 12 toolbar to launch ubuntu 14.04.

When making Linux development, the corresponding 64-bit compiler is at: /opt/toolchain/aarch64/ (note: this toolchain cannot compile "Qt" program, please refer to section 6.3 for "Qt" compilation), and the path has been set automatically.

Note: the user name and password used in ubuntu14.04 both are szbaijie.




28

4.2 Compiling kernel source code

In the content of sources: lichee_helpera64_v2.tar.gz, is the u-boot code and kernel code corresponding to A64, as well as the plate-level configuration file, etc. Copy the file to the virtual system, extract the file, such as under ~/workspace/a64/, and execute the following command:

$ mkdir -p ~/workspace/a64/

$ cd ~/workspace/a64

$ tar –xvf lichee_helpera64_v2.tar.gz

After decompression, execute the follo~wing command to select the corresponding board configuration:

$ cd lichee

$ ./build.sh config

Select "0", sun50iw1p1, corresponding to A64

Then select "0", android, corresponding to the android system.Note: if you want to compile into Linux system, you can choose dragonboard or Linux. Dragonboard is relatively perfect, and Linux is the simplest system, so generally recommended to choose dragonboard.

Then select "0", corresponding to the 3.10 kernel, we have not tested 3.4, we are not sure whether 3.4 is normal.

Finally, select "16", v2, corresponding to the HelperA64 development board hardware configuration .

Then start compiling by executing the following command:

$ ./build.sh

It only takes a few minutes to compile the kernel. For a deeper level of kernel configuration, please look up the Allwinner file..

4.3 Build the android SDK source code

The android_helpera64_v2_0.tar.gz and android_helpera64_v2_1.tar.gz are the SDK source code of android 6.0.1. Copy the file to the virtual system ~/workspace/a64 directory, unzip it under ~/workspace/a64 (note: it must be in the same directory as lichee), and execute the following command:

$ tar –xvf android_helpera64_v2_0.tar.gz

$ tar –xvf android_helpera64_v2_1.tar.gz




29

Set the development environment:

$ cd android

$ source build/envsetup.sh

Run the lunch

$ lunch

Select the configuration of the development board (helpera64_v2-eng):22, and then execute:

$ extract-bsp

Then start compiling:

$ make - j8

Then there's the long wait, which can range from an hour to several hours, depending on your computer's configuration, until the compile is complete.

Note: if the compilation does not pass, remove -j and the following Numbers (representing multi-threading compilation, the maximum number of threads used is 8, which can be twice the number of CPU cores), and the more tasks you add, the more memory you need.

After compiling, you can package and generate an android burn and write image with the following command:

$ pack

The resulting image in the lichee/tools/pack/sun50iw1p1_android_v2_uart0 img, then you can use the burning tool (see section 3) to burn and write it into the developement board.

4.4 patch

The following command is used for patching on Linux. For example, we need to patch the example.patch.

$ patch -p1 < example.patch




30

5 The screen operation

For different projects, different LCD or hdmi screens may be used. The A64 supports three kinds of LCD interfaces, RGB (18bit), LVDS(single-channel only), and MIPI. Only one of the three interfaces can be used at the same time, among which RGB and LVDS interfaces are pin multiplexed.

5.1 Screen adaptation

For RGB panel and an LVDS panel adapter, we usually only need to modify the configuration file, namely: lichee/tools/pack/chips/sun50iw1p1/configs/v2/sys_config.fex, the lcd0 inside the primary key is on the LCD panel configuration information, specific parameters, please refer to screen plant data.

5.2 Modify the startup interface

For user want to modify the boot pictures, can replace: lichee/tools/pack/chips/sun50iw1p1/ configs/v2/bootlogo.bmp. Note: the resolution of the image is not greater than the resolution of the screen, the picture of the number of 32 bits.

5.3 Switch HDMI display

For users who want an HDMI display, plug in an HDMI cable if you're burning android.

If the burned system is linux_qt version (refer to section 6): download linux-qt-hdmi-config in sources>patch>, and directly replace the .config file in linux-3.10.The command is as follows:

$ cd ~/workspace/a64/lichee/linux-3.10

$ mv linux-qt-hdmi-config .config

If the burned ubuntu_core version system (refer to section 7): download ubuntu_core_18.04_config in sources>patch> and directly replace the .config file in linux-3.10.The command is as follows:

$ cd ~/workspace/a64/lichee/linux 3.10

$ mv ubuntu_core_18.04_config .config

And then modify the configuration file: lichee/tools/pack/chips/sun50iw1p1/configs/v2/sys_config fex, in turn, change information is as follows:

screen0_output_type = 3

screen0_output_mode = 5

screen1_output_type = 0

screen1_output_mode = 5

output_disp = 1

output_type = 3

output_mode = 5

hdmi_used = 1

lcd_used = 0

After modifying sys_config.fex, go back to the lichee directory and execute the following command, recompile, and then burn to the development board for HDMI display.

$ cd ~/workspace/a64 /lichee

$ ./build.sh && ./build.sh pack




31

Note: if you want the HDMI display switch back to the LCD display, the : lichee/tools/pack/chips/sun50iw1p1/configs/v2/sys_config fex screen parameters change back to the first LCD display information by default.Reburning will allow you to switch from an HDMI display to an LCD display.

5.4 Modify resolution

In addition, for the android SDK, you need to set up different screen resolution different font size, according to the following Suggestions to modify files: android/device/softwinner/helpera64-v2/ helpera64_v2.mk in value, you can also try other values, but some values may lead to system collapse:

LCD 800 x480: ro.sf.cd_density = 120

LCD 960 x640: ro.sf.lcd_density = 160







Note: every time you change the font size you need to make installclean and then make




32

6 Customize the Linux+qt system based on A64

Since android and Linux use the same kernel, you can customize the Linux file system just as you did with helper2416.

Linux+qt system has been compiled and put in the firmware directory: android_v2_uart0_lcd_7.0.tar.gz. After decompression, you can use the burn writing tool to burn and write to the board.

To run your own qt application on the board, you can compile the qt application directly by reference to 6.3.

Note: please refer to section 2 of the HealperA64_FAQ documentation if you want to purchase a 256M+4G version of the board.

6.1 Compiling the Linux kernel

When compiling Linux kernel source code as per 4.2, select "1" dragonboard configuration, other configuration unchanged. Compile once you're done, and then you can start porting the root file system.The command is as follows:

$ ./build.sh

6.2 Transplant dragonboard root file system

Copy rootfs.tar.gz in the sources directory, to lichee/tools/buildroot/target/dragonboard directory, delete the original default rootfs of the root file system. Unzip rootfs.tar.gz then it new rootfs file system will be generated.The command is as follows:

$ cd ~/workspace/a64 lichee/tools/buildroot/target/dragonboard/

$ rm rootfs -rf

$ tar -xvf rootfs.tar.gz

Find dragonboard_extra.tar.gz in the source content. Copy the dragonboard_extra.tar.gz to lichee/tools/buildroot/target/dragonboard directory, delete the extra folder, decompression dragonboard_extra.tar.gz, the extra replaced dragonboard_extra.tar.gz the extra in gz (note: didn't replace the file system not running). After the substitution is successful. You can compile and package and use the following command.

$ cd ~/workspace/a64/lichee/tools/buildroot/target/dragonboard

$ rm extra -rf

$ tar -xvf dragonboard_extra.tar.gz

Recompile and package to use the dragonboard file system, and execute the following command:

$ cd ~/workspace/a64/lichee


Note: if the system compilation failed, execute the following command and then compile and package.

$sudo apt install android-tools-fsutils

The final image in the lichee/tools/pack/sun50iw1p1_dragonboard_v2_uart0.img, burn it and then you can use the burining tools burn and write to the board.The development board account is rooted, no password.

The dragonboard_extra.tar.gz exsist in the default in gz qt demo, if it need to start the other demo




33

you can modify qt_run.sh in ~/workspace/a64/lichee/tools/buildroot/target/dragonboard/extra Modify the demo path in qt_run.sh (refer to section 6.5). Then compile and burn (refer to 6.2) to the development board, you can see the effect.after booting.

6.3 Compile the QT application

In the tools>tool_chains_for_linux directory: aarch64_linux_gcc_v6.3.0.tar.gz. Copy aarch64_linux_gcc_v6.3.0.tar.gz to the /opt/toolchain directory, unzip the file and set the environment variables, as following:

$ sudo mkdir/opt/toolchain

$ cd/opt/toolchain

$ sudo tar -xvf aarch64_linux_gcc_v6.3.0.tar.gz

$ export PATH=/opt/toolchain/aarch64/usr/bin:$PATH

Since the /opt directory is not a personal directory, operating on the /opt directory requires root access.

Copy example program from QT source code and compile.

$ cd ~/workspace

$ mkdir calculator

$ cd calculator

$ cp ~/workspace/a64lichee/tools/buildroot/target/dragonboard/rootfs/usr/

lib/qt/examples/widgets/widgets/calculator/* ./

$ qmake

$ make

After compiling finished without errors, the "calculator" executable file is generated in the calculator directory.Then copy to the development board to execute (copy via 6.4 SSH).It can also be copied by other copying methods (such as using an "SD card").

6.4 Copy the file through SSH

Enter the command “ifconfig” in the development board to view the development board IP address (note: the development board IP address is required for SCP).

Then ping it to see if the network is working.

$ ping www.baidu.com

If there is a flow of data, the network is fluently. The diagram as below:




34

Once the network is fluently, use the following command to restart the SSH service.

$ /etc/init.d/S50sshd restart

Then copy the "calculator" executable file into the development board "root directory" using SCP in the virtual machine ubuntu, and execute the following command:

$ cd ~/workspace/calculator

$ sudo scp calculator root@(development board IP address):/

6.5 Execute the Qt program

The default qt_run.sh is in the "root" directory.Before running "calculator" executable file needs to be modified qt_run.sh, the /usr/lib/qt/examples/widgets/animation/animatedtiles into the path of the calculator.The diagram below:

After successfully modifying the path, we need to execute this script, and then we can see the effect of our Qt program. The command is as follows:

$ cd /

$ . /qt_run.sh




35

7 Make ubuntu core system

7.1 Compile the ubuntu core kernel

Refer to section 4.2 for kernel source code compilation. Ubuntu core is modified based on dragonboard, so select "1" dragonboard when compiling Linux.

Download the ubuntu_core_18.04_config in the source>patch, directly replace the. Config file in linux-3.10, copy the ubuntu tu_core_18.04_config into the linux-3.10 directory, and execute


$ mv ubuntu_core_18.04_config .config

7.2 Porting the Xfce version ubuntu core system

Download from the network disk sources directory: ubuntu_core_18.04_xfce.tar.gz and ubuntu_core_18.04_xfce_extra.tar.gz, the ubuntu_core_18.04_xfce.tar.gz and ubuntu_core_18. 04_xfce_extra.tar.gz file package copy to the virtual machine system ~/workspace/a64 lichee/tools/buildroot/target/dragonboard/ directory, unzip to ~/workspace/a64 lichee/tools/buildroot/target/dragonboard/ below, delete the original file system rootfs and extra, excute the following commands:


$ rm rootfs -rf

$ rm extra -rf

$ tar –xvf ubuntu_core_18.04_xfce.tar.gz

$ tar –xvf ubuntu_core_18.04_xfce_extra.tar.gz

Once unzipped, the ubuntu core file system exceeds the default rootfs file system and partition size (default size is 512M).At this point we need to manually modify the "rootfs file system" size and the

"rootfs partition" size.（reference Chapter 7.4）

After the modification is completed, you can compile the package for use. The command is as follows:



Note: if the system compilation failed, execute the following command line and then compile the package.

$ sudo apt install android-tools-fsutils

The final image in the lichee/tools/pack/sun50iw1p1_dragonboard_v2_uart0.img, burn it and then you can use the writing tools to the board. The development board account is root or szbaijie, and the password is szbaijie.

The system default is LCD output, please refer to section 5.3 if you need hdmi output.

7.3 Porting the qt version of ubuntu core

The steps are the same as in section 7.2.Only need to download from the network disk sources directory:ubuntu_core_18.04_qt5.63.tar.gz and ubuntu_core_18.04_qt5.63_extra.tar.gz, The ubuntu_core_18.04_qt5.63.tar.gz and ubuntu_core_18.04_qt5.63_extra.tar.gz file package copy to the virtual machine system ~/workspace/a64/lichee/tools/buildroot/target/dragonboard/ directory. Unzip to ~/workspace/a64/lichee/tools/buildroot/target/dragonboard/ below, only need to delete the original file




36

system rootfs, other steps and configuration of the same.Execute the following command:


$ rm extra -rf

$ rm rootfs -rf

$ tar –xvf ubuntu_core_18.04_qt5.63.tar.gz

$ tar –xvf ubuntu_core_18.04_qt5.63_extra.tar.gz

Once unzipped, the ubuntu core file system exceeds the default rootfs file system and partition size (default size is 512M).At this point we need to manually modify the "rootfs file system" size and the

"rootfs partition" size.（reference Chapter 7.4）

After executing the command, compile the package and burn it to the development board.


$ ./build.sh &&./build.sh pack

Note: if the system compilation fails, execute the following command line and then compile the package.

$sudo apt install android-tools-fsutils

The resulting image in the lichee/tools/pack/sun50iw1p1_dragonboard_v2_uart0.img, burn it and then you can use the writing tools to the board.The development board account is root or szbaijie,password is szbaijie.

The system default is LCD output, please refer to section 5.3 if you need hdmi output.




37

7.4 Modify the partition size

7.4.1 Static partitioning

Once 7.2 and 7.3 ubuntu core file unzipped,the default rootfs file system and partition size (default size is 512M).At this point we need to manually modify the "rootfs file system" size and the "rootfs partition" size.

We need to pay attention to the size of the rootfs file system, use the following command to check the size of the rootfs (in M),

$ du -sm rootfs | awk '{print $1}'

Modify the size of the file system in: ~/workspace/a64/lichee/tools/buildroot/target/dragonboard directory

In the build.sh file, open build.sh and find NEW_NR_SIZE to modify its value (the default unit is M). The command is


$ vi build.sh

Rootfs partition size change is in ~/workspace/a64/lichee/tools/pack/chips/sun50iw1p1/ configs/default/ directory sys_partition_dragonboard.fex. Find name = rootfs and modify the size (unit sector) of the size. Since the size of the sector is 512, the size value needs to be multiplied by 512.The command is as follows:

$ cd ~/workspace/a64/lichee/tools/pack/chips/sun50iw1p1/configs/default

$ vi sys_partition_dragonboard.fex

The file system partition size is 10485760* 512/1024/1024/1024*4 = 2048M.

Note: if you buy a 256M+4G version, do not modify the rootfs in sys_partition_dragonboard.fex and NEW_NR_SIZE in build.sh to exceed 4G.

7.4.2 Dynamic partitioning

1 、 Under the network disk /patch directory, http://szbaijie.f3322.net:8088/v2.5/sources/patch/

download rootfs.cpio.gz to the Linux-3.10 directory.

2、Go to the dragonboard directory, and open build.sh


$ vi build.sh

Modify the following：

http://szbaijie.f3322.net:8088/v2.5/sources/patch/




38

Note: Change the number here to a multiple of 16, for example: NEW_NR_SIZE = $(((($NR_SIZE + 64)/16)*16)), if memory problems cause compilation errors, increase the number here.

3、Once modified, enter the configs/default directory, and open sys_partition_dragonboard.fex

$ cd ~/workspace/a64/lichee/tools/pack/chips/sun50iw1p1/configs/default

$ vi sys_partition_dragonboard.fex

Find the location of name=rootfs, set the size to 12582912 and modify it as follows:

4、Go back to the Lichee directory and compile the package





39

8 Kernel configuration

All of the kernel configuration for this chapter has been completed, and the following examples are intended to make users familiarize with the kernel configuration process.

The default configuration can be loaded before kernel configuration, and then modified. The modified configuration contents will be saved to the kernel directory

In the. Config file, enter the following command to enter the configuration environment:


$ make ARCH=arm64 menuconfig

If entering the kernel configuration failed, execute the following command:

$ sudo apt-get install build-essential

$ sudo apt-get install libncurses5

$ sudo apt-get install libncurses5-dev

Note: you can see in the text description in the first few lines of the figure above that Y represents selection, N is deselect, M is compiled into modules and other information.




40

Example: add a PCF8563 model RTC clock and remove the default clock.

First, after the development board starts successfully, enter the following command into the serial port session in Xshell, and you can see the clock information.

Note: the burning here is Linux system, hwclock is the view hardware clock.

Then the main screen selects Device Drivers and pulls to the middle of the about to select the Real Time Clock.




41

Pull down to the bottom of the Real Time Clock and find ALLwinner sun4i/8i/sun50i RTC.

Then press "N" to deselect, as shown below, and save to exit

When the save exits, execute the following command to compile the package

$ cd ~/workspace/a64/lichee/


After the burn is successful, restart and type the following command on the board to see that there is no clock information.

$ hwclock




42

The next step is to add the PCF8563 RTC clock, as shown in the figure below.

The default PCF8563 driver is not turned on. Press "Y" to select it, as shown below.

When the kernel is configured and the save exits, execute the following command to compile the package.

$ cd ~/workspace/a64/lichee/


After the burn is successful, restart and type the following command on the board to see the clock information come out again.

$ hwclock

Note: learn more about kernel configuration by yourself.




43

9 HelloWorld for Android apps

9.1 Download AndroidStudio

With a download address: https://developer.android.google.cn/studio/index.html

Download the required platform for AndroidStudio. Install AndroidStudio after downloading

To start Studio for the first time, you need to install the necessary SDK as follows

9.2 Android Studio creates the HelloWorld project

File - > New - > New Project..

Select the Minimum SDK no higher than Android 6.0 in the following procedure to fill in and set as needed elsewhere.

After creating the hello world project, you can connect to the development board interface, open Settings -> developer option ->USB debugging (ADB debugging), and then find the development board device, click run-> Run App to download the application to the development board and start

running.○22

Note: the development board needs to burn the android system and open ADB for debugging.




44




45

After opening the ADB connection on the HelperA64 board, Android Studio will connect the device as shown below.




46

Click to run hello word and you'll see the effect on the development board.




47

9.3 Develop emulations to run Android applications using the Android

Emulator

For most applications, you can verify it under a virtual machine. Here's how to run your App under a virtual machine.

9.3.1 Create a virtual appliance

Click create virtual device, as shown below.




48




49

Click Finish to create the virtual appliance

9.3.2 Run the application in the virtual appliance

Run --> Run App will pop up to select the device to run, select the virtual device you just created, and the program will start running on the virtual device as shown in the following procedure




50




51

10 FAQ

10.1 Android

10.1.1 How to use Ov5640 camera

Modify "init.sun50iw1p1.rc" in Android to disable the default GC2145.ko and GC0312. ko, and then load the OV5640 driver into it.As shown in figure:

Modify the command as follows:

$ vi android/device/softwinner/helpera64-v2/init.sun50iw1p1.rc

Then modify the "Camera. CFG" as shown below:

Modify the command as follows:

$ vi android/device/softwinner/helpera64-v2/configs/camera.cfg

At last modified configuration file: lichee/tools/pack/one/sun50iw1p1 / configs/v2 / sys_config fex

The modification parameters are as follows:

csi0_dev0_mname = "ov5640"

csi0_dev0_pwdn = port:PE15<0><0><1><0>

csi0_dev1_used = 0

10.1.2 Modify the startup LOGO

Boot logo image name using bootlogo. BMP, replace the lichee/tools/pack/one/sun50iw1p1 / configs/v2 directory bootlogo. BMP (name error, also can appear when packaging errors), and modify the permissions:

$ chmod 664 bootlogo.bmp

Note: When converting BMP format, the depth is 32 bits. The image format can be converted using the conversion software. I used PS conversion, as follows:




52

After the replacement, go back to the Lichee directory and compile:

$ ./build.sh

After compiling, go back to the Android directory and set up the development environment:

$ cd android

$ source build/envsetup.sh

Run the “lunch”

$ lunch

Select the configuration of the development board pair (Helpera64_V2-ENG):22, then execute:

$ extract-bsp

Then start compiling and packaging:

$ make -j8

$ pack

In case of package failure or replacement failure, first check whether the image in the directory lichee/config/v has been replaced successfully. Run the replacement successfully and then compile the package:

$ make installclean

10.1.3 Modify boot animation

Production of bootanimation. Zip compressed file:

Bootanimation.zip contains the part0 Part1 folder and the desc.txt file.The part0, part1 folder contains animated split images in PNG or JPG format.

Bootanimation directory example:




53

Example part0 directory:

The contents of DESc.txt file are as follows:

Note: The first line 500, 350 is consistent with the resolution of the image. 500 is the width of the image and 350 is the height of the image. The resolution of the image should not exceed the resolution of the screen and 20 is the number of frames.The second line begins with P as the identifier, followed by the second column as the number of cycles (0 as an infinite loop), the third column as the number of frames between cycles, and the fourth column as the corresponding directory name. When the animation is played, it automatically plays in the order of picture file names.

Enter the Bootanimation directory under Linux and use the following command to compress:

$ zip -0 -r ../bootanimation.zip ./*

The Linux command uses -0 to specify the lowest level of compression stored, which means the archive is stored without compression, otherwise the animation may appear as a black screen due to a package format problem.Will be packed file to replace the android/device/softwinner/helpera64 - v2 / media directory bootanimation. Zip, and modify the permissions:

$ chmod 775 bootanimation.zip

Go back to the Android directory, clear the previous compilation configuration before packaging:

$ make installclean

$ make -j8

$ pack

The packed files are in the Lichee/Tools/Pack directory




54

10.2 Ubuntucore

10.2.1 Ubuntucore_qt connect wifi

Since Android and ubuntucore+xfce can open wifi directly from the interface, only the Qt system's wifi startup method is described here.

First, LSMOD checks whether the wifi driver is loaded. If not, load it manually.(Note: network card driver is 8723Bs.ko.

After the driver is loaded, check whether wifi can be searched (note: if the signal is not searched, try adding an antenna). This wifi does not support 5G, and 5G frequency band cannot appear during the search. The search command is as follows:

1. Search:

$ iwlist wlan1 scan | grep ESSID

2. Connect to wifi:

$ nmcli device wifi connect "wifi name" password "wifi password" name wifi

3. After connecting to wifi, if you need to change the wifi user name and wifi password, the command is as follows:

$ nmcli connection modify wifi. ssid "changed user name"

$ nmcli connection modify wifi- sec.psk "changed password"

Restart after changing the password

$ nmcli connection up wifi

4. Check status:

$ ifconfig

10.2.2 Ubuntucore_QT sets the hotspots and self-starts

1. Set the name and password of the hot spot

$ nmcli device wifi hotspot con-name hotspot ifname wlan1 ssid "wifi name

"password "wifi password"

2. Setup self-starting

$ nmcli connection modify hotspot connection.autoconnect yes

3, hot IP address modification

$ nmcli Connection Modify Hotspot ipv4.addresses "IP/subnet mask in need of

Modification"

Note: Sample IP address/subnet mask 192.168.20.22/24

4. Reboot

$ nmcli connection up hotspot




55

5. Finally, check the status and the command is as follows:

$ ifconfig

10.2.3 Ubuntucore_xfce starts Bluetooth

1. Update the source first, and then install the necessary software:

$ apt update

$ apt-get install bluetooth rfkill bluez blueman

2. Start the Bluetooth device

$ start_bt.sh ttyS1

$ rfkill unblock 3

3. Open the terminal and enter the following command to match bluetooth.

$ blueman-assistant

Or after restarting, the right upper foot has the Bluetooth flag, and click "Setup New Device" to match the Bluetooth

10.2.4 Ubuntucore_xfCE starts 4G

Click in the top right corner find "New Mobile Broadband Connection" to create a New connection device.

Power on is slow, it will appear after a while, click on the following figure.

Then click next->region(choose China)-> operator (e.g. China unicom)-> next.

Select and then click , drag to the end, find "Edit Connections", click on the "China Unicom Default" you just created, then set the password as shown below.

(Note: the password is the same as the user name, this is China Unicom, so the user name and password are both uninet)




56

At this point, I'm gonna click again Logo, select "China Unicom Default" to connect, if prompted for password, put it above

Enter the password again (uninet above), and after dialing successfully, you will be connected to the network successfully.




57

10.3 linux_qt

10.3.1 The 256MB memory version of the development board kernel boot failure

solution

Many people develop board burning linux_QT system, and then at the time of boot will fail, if the following picture failed to boot, because the purchase of 256MB of memory core board:

Solutions:

Download the patch 256m_memory.patch from the brandy directory: v2->sources->patch-> 256m_memory.patch.

$ cd lichee/brandy/

$ patch -p1 < 256M_memory.patch

When the patch is applied, we need to recompile uboot.

$cd lichee/brandy/u-boot-2014.07/

$ make sun50iw1p1_config

$ make

2. Modify the env.cfg file. The diagram below:

The order is as follows:

$ vi tools/pack/chips/sun50iw1p1/configs/default/env.cfg

3. Recompile and package


10.3.2 The Linux_qt command on the system starts wifi

First, LSMOD checks whether the wifi driver is loaded. If not, load it manually.(Note: HelperA64_V1 network card driver is 8188EU.ko, for HelperA64_v2 network card driver is 8723bs.ko)

After the driver is loaded, check whether wifi can be searched (note: if the search is not possible, the signal is not strong, try adding an antenna). The search command is as follows:

$ iwlist wlan0 scan




58

Set the wifi name and password of Wlan0, modify /etc/wpa_supplicant.conf, no one can be created manually, the configuration file format is as follows:

Execute the following command:

$ wpa_supplicant -c /etc/wpa_supplicant.conf -i wlan0 &

$ dhcpcd wlan0

Finally, check whether wifi has been started successfully. The command is as follows:

$ ifconfig wlan0




59

10.4 Dragonface

Dragonface currently only supports the android system changes, in http://szbaijie.f3322.net:8088/v2.5/tools/ download DragonFace_V2. 2.5.7 z to the local, decompression and installation;

10.4.1 Change the Android startup logo

Open Dragonface:

1、 Select the firmware to change the startup logo and wait for the firmware to load;

2、 After the firmware is loaded, select the screen music

3、 Click replace bootlogo, select the bootlogo to be replaced,

4、 After the replacement, select the lower right corner to save, select the save path.

Note: BMP, PNG, JPG images will be displayed by default when selecting images. If other formats are needed, All Files can be selected in the lower right corner.

10.4.2 Change boot animation

Open Dragonface:

1、 Select the firmware to change the startup logo and wait for the firmware to load;

2、 After the firmware is loaded, select the screen music

3、 Click Replace Boot Animation (ZIP) and select the boot animation zip package that needs to be replaced

4、 After the replacement, select the lower right corner to save, select the save path

Note: See 10.1.3 for the making process of bootanimation.zip




60

Power on music:

To change the boot music, place the boot music in the part0 directory and name it Audio.wav.Add audio_conf.txt to the root directory

It is as follows:

Packaging format requirements:




61

Windows uses Winrar packaging, select ZIP format, compression standard to choose "save"; That is, only archive without compression, otherwise the animation might appear black due to a package format problem. Packaged files can be used directly in Dragonface without modifying permissions, which would be required under Linux with commands.

Animation directory packaging format is as follows:

Bootanimation consists of several images, which need to be packaged as bootanimate.zip. Windows uses the compression tool to package, select zip format, and select "save" as the compression standard:

Note: do not package in the root directory. To enter the bootAnimation directory, select all files and then package, otherwise the bootanimation directory will still be the Bootanimation directory instead of the file. When replacing the animation, a package format error will appear

10.4.3 Add a built-in APK

Open dragonface:

1、 Select the firmware

2、 Select the built-in APK

3、 Right-click in the white space in the preview area and select Add APK, and select the APK that you want built in

4、 Click the save button in the lower right corner




62




63

11 About Technical Support

For all users who purchase our development board, you can obtain permanent free technical support (only for functions already provided on the development board) by:

Mail: [email protected]

Telephone: 0755-86017779

Mobile Phone: 13510178868(Mr. Chen)

QQ group: 74306575

Please contact me during working hours if you need technical support.

Date post:	07-Dec-2021
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

百杰科技HelperA64开发板使用手册 - PubYun

Documents