Core-3399-JD4编译的内核启动失败
当前硬件是Core-3399-JD4核心板以及配套底板，使用官网下载的固件能正常启动。此时使用SDK编译得到的内核则无法正常启动。官网下载的SDK已更新，且无修改，编译方式为http://wiki.t-firefly.com/zh_CN/Core-3399-JD4/Linux_development.html#bian-yi-sdk。仅编译内核。将内核写入0x00280000后，启动失败。报错打印一：此处仅报错，未停止运行
[ 4.028549] systemd: Detected architecture arm64.
[ 4.036898] EXT4-fs error (device mmcblk1p5): ext4_iget:4434: inode #42191: comm systemd: bad extended attribute block 3942645823
[ 4.038814] Aborting journal on device mmcblk1p5-8.
报错打印二：在Started D-Bus System Message Bus.成功后，系统停止。
Started Apply Kernel Variables.
Started udev Coldplug all Devices.
Started udev Kernel Device Manager.
Mounted POSIX Message Queue File System.
Mounted Kernel Debug File System.
Mounted Kernel Configuration File System.
Mounted FUSE Control File System.
Started Flush Journal to Persistent Storage.
Started Set the console keyboard layout.
Reached target Local File Systems (Pre).
Reached target Local File Systems.
Starting Create Volatile Files and Directories...
Starting Set console font and keymap...
Starting Tell Plymouth To Write Out Runtime Data...
Started Dispatch Password Requests to Console Directory Watch.
Reached target Local Encrypted Volumes.
Created slice system-systemd\x2dbacklight.slice.
Starting Load/Save Screen Backlight鈥ghtness of backlight:backlight...
Failed to start Load/Save Screen Ba鈥rightness of backlight:backlight.
See 'systemctl status systemd-backlight鈥klight:backlight.service' for details.
Started Tell Plymouth To Write Out Runtime Data.
Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Reached target Host and Network Name Lookups.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Reached target System Time Synchronized.
Starting Update UTMP about System Boot/Shutdown...
Started Set console font and keymap.
Stopped Network Time Synchronization.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Stopped Network Name Resolution.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Found device /dev/ttyFIQ0.
Stopped Network Time Synchronization.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Stopped Network Name Resolution.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Stopped Network Name Resolution.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Stopped Network Time Synchronization.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Reached target Sound Card.
Failed to start Update UTMP about System Boot/Shutdown.
See 'systemctl status systemd-update-utmp.service' for details.
Dependency failed for Update UTMP about System Runlevel Changes.
Stopped Network Time Synchronization.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Stopped Network Name Resolution.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Reached target System Initialization.
Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Listening on D-Bus System Message Bus Socket.
Starting Socket activation for snappy daemon.
Starting Docker Socket for the API.
Reached target Paths.
Listening on Socket activation for snappy daemon.
Stopped Network Time Synchronization.
Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
Stopped Network Name Resolution.
Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
Listening on Docker Socket for the API.
Reached target Sockets.
Reached target Basic System.
Starting Dispatcher daemon for systemd-networkd...
Starting LSB: automatic crash report generation...
Started D-Bus System Message Bus.
追加：固件使用的是AIO-3399-JD4-LVDS-UBUNTU18.04-GPT-20190904-1740.img，但是SDK是Ubuntu16的，不知道是否存在匹配问题。
另外使用./build.sh全编译时，在编译过程中需要联网下载资源，不知此现象是否正常？ 首先看看device/rockchip/rk3399/parameter-ubuntu.mk这个文件中，boot分区的地址，不知道是不是0x28000，我查看的地址好像不一样。
全编译时，根文件系统默认编译buildroot根文件系统，所以当然会联网下载资源
页:
[1]