1. Modified file description
Because there are many modifications in each file in the previous chapters, it takes too much time to record them one by one, so I have talked about a lot of principles. Here I will summarize the files I have modified. The modified files mentioned here are relative to the u-boot platform code created in the first chapter.
1. /makefile
2. The entire sd_fuse folder. I copied the entire sd_fuse folder under the uboot provided by FriendlyARM. Because this file is used to burn the SD card, I copied it directly and used it.
3. /include/configs/zthtiny4412.h
4. /board/Samsung/zthtiny4412
5. /arch/arm/lib/board.c
6. /arch/arm/include/asm/arch-exynos/cpu.h
7. / arch/arm/include/asm/arch-exynos/movi_partition.h
8. / arch/arm/cpu/armv7/exynos/irom_copy.c Actually, this file does not need to be modified. I changed it for debugging.
These should be the files. Now we can compile the kernel.
2. Compile, burn and debug
The following commands are provided for reference:
cp -R /media/sf_share/u-boot_zth .
chmod –R 777 u-boot_zth /
cd u-boot_zth
make distclean
make zthtiny4412_config
make
The following is the SD card file provided by FriendlyARM.
cd sd_fuse/
make
cd zthtiny4412/
./sd_fusing.sh /dev/sdb
The serial port information after running is shown in the figure below:
Figure 14-1, u-boot debugging output information
To be honest, I didn't expect uboot to be able to run to the step of entering commands, and the output information can be said to be basically the same as that provided by FriendlyArm, except for the two places I marked above, the differences in other places were deliberately added when I modified the code.
To be honest, I feel surprised and happy at this point, but also a bit frustrated, because I didn't expect it to go this far at once. I thought I would have to change this and that to support the network, commands, etc. I didn't expect it to get to this point at once, so I had to change my plan. I don't have the courage and energy to get a source code from the UBOOT official website to port it, because I killed this idea at the beginning. I was still impatient, and my goals were different. I didn't have much time, so I always wanted to do it quickly. I don't want to do it again, so let's just leave it at that. The next step is to port the LCD.
One more point needs to be explained. I tried to find the reasons for the above two differences by comparing them with the codes provided by FrienlyARM. I didn't compare them in detail, so I didn't find the specific reasons and I'm still unsure.
Previous article:Chapter 13: Tiny4412 U-BOOT transplantation 13 DDR3 initialization source code analysis
Next article:Chapter 16: Android LCD (II): LCD Common Interface Principles
Recommended ReadingLatest update time:2024-11-16 19:48
Professor at Beihang University, dedicated to promoting microcontrollers and embedded systems for over 20 years.
- Innolux's intelligent steer-by-wire solution makes cars smarter and safer
- 8051 MCU - Parity Check
- How to efficiently balance the sensitivity of tactile sensing interfaces
- What should I do if the servo motor shakes? What causes the servo motor to shake quickly?
- 【Brushless Motor】Analysis of three-phase BLDC motor and sharing of two popular development boards
- Midea Industrial Technology's subsidiaries Clou Electronics and Hekang New Energy jointly appeared at the Munich Battery Energy Storage Exhibition and Solar Energy Exhibition
- Guoxin Sichen | Application of ferroelectric memory PB85RS2MC in power battery management, with a capacity of 2M
- Analysis of common faults of frequency converter
- In a head-on competition with Qualcomm, what kind of cockpit products has Intel come up with?
- Dalian Rongke's all-vanadium liquid flow battery energy storage equipment industrialization project has entered the sprint stage before production
- Allegro MicroSystems Introduces Advanced Magnetic and Inductive Position Sensing Solutions at Electronica 2024
- Car key in the left hand, liveness detection radar in the right hand, UWB is imperative for cars!
- After a decade of rapid development, domestic CIS has entered the market
- Aegis Dagger Battery + Thor EM-i Super Hybrid, Geely New Energy has thrown out two "king bombs"
- A brief discussion on functional safety - fault, error, and failure
- In the smart car 2.0 cycle, these core industry chains are facing major opportunities!
- The United States and Japan are developing new batteries. CATL faces challenges? How should China's new energy battery industry respond?
- Murata launches high-precision 6-axis inertial sensor for automobiles
- Ford patents pre-charge alarm to help save costs and respond to emergencies
- New real-time microcontroller system from Texas Instruments enables smarter processing in automotive and industrial applications
- Automotive/Industrial mmWave Radar Sensors
- Is it true that soft-switching EMI is smaller than hard-switching EMI?
- DAC3283 conversion formula
- Write a STEVAL-MKI109V3 Unico tool source code
- Questioning voice: Will Wi-Fi die in the 5G era?
- Application of Dacai UART screen in non-contact self-service temperature measurement system
- Weekly review information is here~~
- SimpleFOC open source project, with a full set of Chinese documents (officially recognized, Dengge is responsible)
- Analog Discovery 2 Review (8) Digital Input and Output Functions + Summary
- 2020-6-23-Took some time to draw a 3D printed shell for the work