[Mill MYB-YT507 development board trial experience] + Summary of recent compilation problems, which have not yet been solved
[Copy link]
After the last experience, the compilation problem has been stuck on my side, because I have been thinking about testing the LVDS output signal to display a 7-inch screen. I am too persistent. I think the 7-inch display is more convenient because of its small size. It seems that I should prepare an HDMI screen in the future. Now there are more and more development boards with HDMI interfaces. In fact, I have also considered the compilation problem myself. I should be prepared from the beginning of using domestic chips. Our domestic chips are indeed not open enough. In addition, they usually add their own proprietary codes to the Linux kernel. This means that if you use a chip, you have to learn how to operate it. Well, I have gone too far. Let me talk about the packages I compiled this time.
In the development package given to me, we can get two SDK packages, one in the source directory, and one I stored separately, named Buildroot-downloads.tar.bz2. I compiled a very small package. After compilation, it can be downloaded and started, but when I tried to modify the device tree, there was no response.
The file named YT507H-buildroot-t5-4.9.170-1.0.0.tar.bz2 is large and contains the most complete information. You need to configure it yourself. You can see the Android package when configuring it. Although the Android package is not yet open, it should be supported in the future. I have compiled it now. It takes at least more than an hour to compile, but the compiled one cannot be used yet. The startup prompt is as follows:
I changed two virtual machine systems, one is Ubuntu 18.04 and the other is 20.04. Both can generate packages, but cannot be started.
This kind of package on Github has not been downloaded yet. It seems to have been removed from Github. There is nothing when I open the link. I will try to download and compile it later.
Finally, I used the original image and connected it to LVDS0.
But it seems that not everything he said can be displayed normally. I tested that I need to enter the data in the blue box. The display and wiring effects are as follows:
Sometimes the screen is distorted, and I don't know why. After so many tests, I'm not going to focus on compiling the system image next. I'll just go directly into the application experience and experience the Ubuntu system.
|