1. The problem of the font display being too large and inappropriate
point brightness
Choose never to lock the screen, personal habit
Click Display, go in and choose a resolution and scaling ratio that suits you. It will look more comfortable. Click Apply to take effect. The display will not be abnormal next time you turn on the computer.
2. The copy-paste key cannot be used.
Install the VMware-tools tool, find your Ubuntu path, delete all files with the suffix .lck, and the problem is solved.
3. Expanding the virtual machine capacity is a little troublesome. I recommend a useful blog to everyone. It can be used for personal testing.
When transplanting, pay attention to check the connection status of the development board. Be sure not to connect it backwards. It is easy to burn. If the development board is burned, it will be obviously hot, there will be a buzzing current sound, and the serial port will print garbled characters. The USB cannot be recognized. Just change the interface and re-plug and unplug it a few times. Pay attention to the order of steps and don't be impatient.
4. The network cable is directly connected to the development board and cannot be recognized by the computer.
This time I am using MP157a. When burning the image, please pay attention to whether the development board is v2 or v3.
When querying the IP of the development board, there is network card eth0 but no ipv6 netaddr. This may be due to a network cable problem. The default v3 version uses a Gigabit network cable. If you replace it with a 100M network cable, there will be no problem and it can be recognized normally.
5.Wireless connection method
- ipconfig queries Windows IPv4 gateway
2. Check the Windows network adapter and its corresponding name.
3. Select the corresponding virtual network settings for the virtual machine ubuntu
4. Create a new network connection for the virtual machine and set it to the same network segment.
5. If the virtual machine pings the development board and there is a reply, no network cable is needed, but the speed may be a little slower than the network cable, which is enough for learning.
6.Qt cross-compilation problem
Qt under Linux does not have qcharts and qtexttospeech modules.
If the error shown below occurs, you must first close the original interface of the development board before the new interface can be displayed. command (psplash-drm-quit). There is also the fact that the code has not been changed. It can run the first time, but it cannot run the second or third time. When an error occurs, restart the virtual machine to solve the problem. Or reconfigure the project and compile it. Delete the built directory and recompile. Resource display problems can also be solved in this way. There are many questions, and you need to explore them slowly by yourself.
When Qt deploys the project, the above situation occurs, and the serial port suddenly reports a lot of errors. Restart the development board to solve the problem. (reason unknown)
It crashed when compiling the project.
Without a network cable connection, qt cross-compilation is very slow, taking a minute or two; if a network cable is connected, it only takes more than ten seconds, which is much more efficient.
7. When using mqtt, the development board needs to be connected to the network.
Otherwise communication will not be possible. Turn off the VPN, otherwise you will not be able to log in.
8. The file name of the development board cannot contain Chinese characters
When opening a file containing Chinese characters, an error will be reported and the file cannot be parsed, causing problems.
9. Qt5.14 version and Qt5.9 version resource file compilation problem
The resource files of Qt5.9 version can be in Chinese, but the resource files of Qt5.14 version cannot be in Chinese, and an error will be reported during compilation, as shown below
