************************START************************
#Brush system Required raw materials: development board, serial data cable, USB data cable
First, check whether the development board can be recognized by the PC. If it cannot be recognized, it means that our development board driver needs to be updated again. If it can be recognized, it is not necessary.
Plug in the serial cable and USB cable, and connect with SecureCRT
************************Destroy uboot********* *************
For the flashing of the linux+Qt system, we need to pay attention to the details:
First, understand a concept:
what is the system console? What is uboot console?
1. System console: It is the interface after entering the system without pressing it during the countdown.
2.uboot console: you press the key when the countdown is 3 2 1, and you will enter uboot.
Note that we destroy uboot under the system console. dilapidated. Secondly, we
need to learn how to burn SD card images. There are two ways to make SD cards: 1. Use Jiuding SD card tool to download files to SD card under Windows (convenient) 2. Use dd command under Linux The uboot in the inand is destroyed, but there is a problem. For different operating systems, our destruction methods are different. The way to destroy uboot is as follows: ------------------------------------ Android image: (again, pay attention to the destruction It is under the system console, not the uboot interface)
-> Input first: busybox dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 seek=1 count=1 conv=sync
will appear:
1+0 records in
1+0 records out -> input later :sync ------------------------------------- linux image: -> first enter: busybox dd if =/dev/zero of=/dev/mmcblk0 bs=512 seek=1 count=1 conv=sync will appear: 1+0 records in 1+0 records out -> then enter: sync At this point our destruction work is already done When it is over, we shut down and restart the development board again, and it cannot be started. At this time, the SecureCRT serial port prompts SD checksum error---indicating that the destruction is successful. **************************** Burn new uboot, kernel and root filesystems ********** **** 1. We must turn the DIP switch to EMMC 2. Use Jiuding's SD_Fusing tool to burn the uboot specified by Mr. Zhu to the SD card. 3. Then insert the SD card, start it again, interrupt the system operation, and enter the uboot interface. 3. Use a fastboot command of a uboot, fastboot is also a tool on the PC, you can use the command line to burn our files
Mr. Zhu pointed out that when programming the linux+Qt system, the disk needs to be partitioned first, that is, when entering uboot, enter: fdisk -c 0
and then enter: fastboot to let the development board enter the fastboot mode
4. We use the PC The fastboot tool (is a folder), enter the cmd command line, find this directory, and enter: fastboot. That is, running the fastboot tool on the PC.
This tool requires us to copy all the system files that need to be burned to the fastboot file (we use a linuxQT folder to talk about Qt's uboot, kernel, and root file system)
and then put the command on the PC line, enter: fastboot devices to see if our development board has been detected by the fastboot tool.
If it is detected, run the following codes to burn to inand in turn:
burn uboot: fastboot flash bootloader linuxQT/uboot.bin burn uboot and
wait for the uboot interface to display: okey
burn kernel: fastboot flash kernel linuxQT/zImage-qt burn linux kernel
Wait for the uboot interface to display: okey
to burn the root file system: fastboot flash system linuxQT/rootfs_qt4.ext3 to burn rootfs When the partition 'system' flashed appears on the development board or secureCRT, the programming is over. At this point, shut down and restart, and Qt should be able to run successfully at this time.
The above is the entire burning process of the operation. According to the reason, Qt can be run.
************************Following my personal problems ******************** ************
If the system restarts all the time, or the development board shows that Qt is incomplete, it is not that there is a problem with our burning system steps, but there may be a problem with our uboot.bin file.
We need to use the print command to print out all the environment variables and check if the bootcmd and bootargs are the following values. If not, it is wrong and needs to be corrected.
Our uboot supports modifying the environment variables of the file when it is running. The above problem is that some environment variables of uboot are set in addition to the problem.
The modification method is as follows:
set bootcmd 'movi read kernel 30008000; bootm 30008000'
set bootargs console=ttySAC2,115200 root=/dev/mmcblk0p2 rw init=/linuxrc rootfstype=ext3
Finally, don't forget to save: save.
At this point, go to shutdown and restart, and all problems are solved at this time.
****************************************END************ ************************
2018-4-15
#Brush system Required raw materials: development board, serial data cable, USB data cable
First, check whether the development board can be recognized by the PC. If it cannot be recognized, it means that our development board driver needs to be updated again. If it can be recognized, it is not necessary.
Plug in the serial cable and USB cable, and connect with SecureCRT
************************Destroy uboot********* *************
For the flashing of the linux+Qt system, we need to pay attention to the details:
First, understand a concept:
what is the system console? What is uboot console?
1. System console: It is the interface after entering the system without pressing it during the countdown.
2.uboot console: you press the key when the countdown is 3 2 1, and you will enter uboot.
Note that we destroy uboot under the system console. dilapidated. Secondly, we
need to learn how to burn SD card images. There are two ways to make SD cards: 1. Use Jiuding SD card tool to download files to SD card under Windows (convenient) 2. Use dd command under Linux The uboot in the inand is destroyed, but there is a problem. For different operating systems, our destruction methods are different. The way to destroy uboot is as follows: ------------------------------------ Android image: (again, pay attention to the destruction It is under the system console, not the uboot interface)
-> Input first: busybox dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 seek=1 count=1 conv=sync
will appear:
1+0 records in
1+0 records out -> input later :sync ------------------------------------- linux image: -> first enter: busybox dd if =/dev/zero of=/dev/mmcblk0 bs=512 seek=1 count=1 conv=sync will appear: 1+0 records in 1+0 records out -> then enter: sync At this point our destruction work is already done When it is over, we shut down and restart the development board again, and it cannot be started. At this time, the SecureCRT serial port prompts SD checksum error---indicating that the destruction is successful. **************************** Burn new uboot, kernel and root filesystems ********** **** 1. We must turn the DIP switch to EMMC 2. Use Jiuding's SD_Fusing tool to burn the uboot specified by Mr. Zhu to the SD card. 3. Then insert the SD card, start it again, interrupt the system operation, and enter the uboot interface. 3. Use a fastboot command of a uboot, fastboot is also a tool on the PC, you can use the command line to burn our files
Mr. Zhu pointed out that when programming the linux+Qt system, the disk needs to be partitioned first, that is, when entering uboot, enter: fdisk -c 0
and then enter: fastboot to let the development board enter the fastboot mode
4. We use the PC The fastboot tool (is a folder), enter the cmd command line, find this directory, and enter: fastboot. That is, running the fastboot tool on the PC.
This tool requires us to copy all the system files that need to be burned to the fastboot file (we use a linuxQT folder to talk about Qt's uboot, kernel, and root file system)
and then put the command on the PC line, enter: fastboot devices to see if our development board has been detected by the fastboot tool.
If it is detected, run the following codes to burn to inand in turn:
burn uboot: fastboot flash bootloader linuxQT/uboot.bin burn uboot and
wait for the uboot interface to display: okey
burn kernel: fastboot flash kernel linuxQT/zImage-qt burn linux kernel
Wait for the uboot interface to display: okey
to burn the root file system: fastboot flash system linuxQT/rootfs_qt4.ext3 to burn rootfs When the partition 'system' flashed appears on the development board or secureCRT, the programming is over. At this point, shut down and restart, and Qt should be able to run successfully at this time.
The above is the entire burning process of the operation. According to the reason, Qt can be run.
************************Following my personal problems ******************** ************
If the system restarts all the time, or the development board shows that Qt is incomplete, it is not that there is a problem with our burning system steps, but there may be a problem with our uboot.bin file.
We need to use the print command to print out all the environment variables and check if the bootcmd and bootargs are the following values. If not, it is wrong and needs to be corrected.
Our uboot supports modifying the environment variables of the file when it is running. The above problem is that some environment variables of uboot are set in addition to the problem.
The modification method is as follows:
set bootcmd 'movi read kernel 30008000; bootm 30008000'
set bootargs console=ttySAC2,115200 root=/dev/mmcblk0p2 rw init=/linuxrc rootfstype=ext3
Finally, don't forget to save: save.
At this point, go to shutdown and restart, and all problems are solved at this time.
****************************************END************ ************************
2018-4-15