页次: 1
如题,最近有空搞一下啊f1c200s,准备移植一个esp-hosted玩玩是使用spi控制,成功编译出驱动文件,加载驱动文件的时候报如下错误,请教一下看看是什么错误。
# ls
esp32_spi.ko
# modprobe esp32_spi.ko
[ 117.876915] esp32_spi: loading out-of-tree module taints kernel.
[ 118.101904] sun6i-spi 1c06000.spi: cs135 >= max 4
[ 118.106646] esp32_spi: spi_dev_init: Failed to add new SPI device
[ 118.551630] esp32_spi: spi_init: Failed Init SPI device
通过初始化函数可以知道是死在了spi_new_device里面
static int spi_dev_init(int spi_clk_mhz)
{
int status = 0;
struct spi_board_info esp_board = {{0}};
struct spi_master *master = NULL;
strscpy(esp_board.modalias, "esp_spi", sizeof(esp_board.modalias));
esp_board.mode = SPI_MODE_2;
esp_board.max_speed_hz = spi_clk_mhz * NUMBER_1M;
esp_board.bus_num = 1;
esp_board.chip_select = 135;
master = spi_busnum_to_master(esp_board.bus_num);
if (!master) {
esp_err("Failed to obtain SPI master handle\n");
return -ENODEV;
}
spi_context.esp_spi_dev = spi_new_device(master, &esp_board);
if (!spi_context.esp_spi_dev) {
esp_err("Failed to add new SPI device\n");
return -ENODEV;
}
status = spi_setup(spi_context.esp_spi_dev);
if (status) {
esp_err("Failed to setup new SPI device");
return status;
}
不是太明白这个un6i-spi 1c06000.spi: cs135 >= max 4是啥意思,难道不能定义大于4的cs引脚吗
楼主你好,你用的是什么芯片阿,这个ft6336的驱动是那里获取的,内核好像没有。我找了个驱动Focaltech_Touch_FT5436_Driver_for_Qualcomm_V2.2_20180321,将文件夹整个复制进内核编译后打开报错,日志如下:
[ 1.028443] [FTS]fts_ts_init: Enter
[ 1.032049] [FTS]fts_ts_init: Exit(1679)
[ 1.035968] i2c /dev entries driver
[ 1.040274] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pe not found, using dummy regulator
[ 1.053051] [FTS]fts_ts_probe: Enter
[ 1.056651] [FTS]fts_parse_dt: Enter
[ 1.060371] [FTS][Info]display x(0 480) y(0 480)
[ 1.065093] [FTS][Info]max touch number:5, irq gpio:128, reset gpio:0
[ 1.071587] [FTS]fts_parse_dt: Exit(1194)
[ 1.076026] [FTS]fts_input_init: Enter
[ 1.080544] input: fts_ts as /devices/platform/soc/1c27000.i2c/i2c-0/0-0038/input/input0
[ 1.089444] [FTS]fts_input_init: Exit(997)
[ 1.093549] [FTS]fts_gpio_configure: Enter
[ 1.097857] [FTS]fts_gpio_configure: Exit(1058)
[ 1.102385] [FTS]fts_reset_proc: Enter
[ 1.357761] [FTS]fts_reset_proc: Exit(254)
[ 1.362810] [FTS]verify id:0x6426
[ 1.366132] [FTS]TP not ready, read:0x6426
[ 1.488676] [FTS]verify id:0x6426
[ 1.492000] [FTS]TP not ready, read:0x6426
[ 1.608670] [FTS]verify id:0x6426
[ 1.611986] [FTS]TP not ready, read:0x6426
[ 1.728663] [FTS]verify id:0x6426
[ 1.731982] [FTS]TP not ready, read:0x6426
[ 1.848644] [FTS]verify id:0x6426
[ 1.851964] [FTS]TP not ready, read:0x6426
[ 1.968657] [FTS]verify id:0x6426
[ 1.971976] [FTS]TP not ready, read:0x6426
[ 2.088656] [FTS]verify id:0x6426
[ 2.091978] [FTS]TP not ready, read:0x6426
[ 2.208663] [FTS]verify id:0x6426
[ 2.211980] [FTS]TP not ready, read:0x6426
[ 2.328658] [FTS]verify id:0x6426
[ 2.331978] [FTS]TP not ready, read:0x6426
[ 2.448227] random: fast init done
[ 2.451990] [FTS]verify id:0x6426
[ 2.455304] [FTS]TP not ready, read:0x6426
[ 2.577746] [FTS][Info]fw is invalid, need read boot id
[ 2.608580] [FTS][Error]read boot id fail
[ 2.612593] [FTS][Error]not focal IC, unregister driver
[ 2.619293] [FTS]fts_ts_probe: Exit(1452)
[ 2.623385] fts_ts: probe of 0-0038 failed with error -5
[ 2.630924] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
设备数是这样的:
focaltech@38{
compatible = "focaltech,fts";
reg = <0x38>;
// interrupt-parent = <&msm_gpio>;
// interrupts = <13 0x02>;
// focaltech,reset-gpio = <&msm_gpio 12 0x01>;
// focaltech,irq-gpio = <&msm_gpio 13 0x02>;
interrupt-parent = <&pio>;
// interrupts = <4 0 IRQ_TYPE_EDGE_FALLING>; // PA1
focaltech,irq-gpio = <&pio 4 0 GPIO_ACTIVE_HIGH>; // PA1
focaltech,reset-gpio = <&pio 0 0 GPIO_ACTIVE_HIGH>; // PA0
focaltech,max-touch-number = <5>;
focaltech,display-coords = <0 0 480 480>;
// pinctrl-names = "pmx_ts_active","pmx_ts_suspend","pmx_ts_release";
// pinctrl-0 = <&ts_int_active &ts_reset_active>;
// pinctrl-1 = <&ts_int_suspend &ts_reset_suspend>;
// pinctrl-2 = <&ts_release>;
// focaltech,have-key;
// focaltech,key-number = <3>;
// focaltech,keys = <139 102 158>;
// focaltech,key-y-coord = <2000>;
// focaltech,key-x-coords = <200 600 800>;
};
可以借用一下你的驱动吗
@future
Symbol: DRM_PANEL_SIMPLE [=y] │
│ Type : tristate │
│ Prompt: support for simple panels │
│ Location: │
│ -> Device Drivers │
│ -> Graphics support │
│ (7) -> Display Panels │
│ Defined at drivers/gpu/drm/panel/Kconfig:31 │
│ Depends on: HAS_IOMEM [=y] && DRM [=y] && DRM_PANEL [=y] && OF [=y] && BACKLIGHT_CLASS_DEVICE [=y] │
│ Selects: VIDEOMODE_HELPERS [=y]
找到了,应该是这个,但是已经打开了,屏幕还是没有亮,这个板子以前我点亮过的,时间长了,忘记原先怎么设置的了。
看你一楼的信息,没有勾选 DRM SIMPLE PANEL
参考这个吧:
buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *
https://whycan.com/t_5221.html
您好我就是用的tiny200开发包,也是屏幕没亮,您说的这个DRM SIMPLE PANEL是在那个里面,我在uboot和kerner里面都没有找到。
楼主的补丁确认好用,使用的是串口1,pa2和pa3引脚,荔枝派的u-boot
git clone https://github.com/Lichee-Pi/u-boot.git
git checkout nano-v2018.01
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- licheepi_nano_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j12
sunxi-fel uboot ./u-boot-sunxi-with-spl.bin
然后就可以看到log输出了。
U-Boot SPL 2018.01-05679-g013ca457fd-dirty (Mar 03 2024 - 13:11:13)
DRAM: 64 MiB
Trying to boot from FEL
U-Boot 2018.01-05679-g013ca457fd-dirty (Mar 03 2024 - 13:11:13 +0800) Allwinner Technology
CPU: Allwinner F Series (SUNIV)
Model: Lichee Pi Nano
DRAM: 64 MiB
MMC: SUNXI SD/MMC: 0
Card did not respond to voltage select!
mmc_init: -95, time 23
*** Warning - MMC init failed, using default environment
In: serial@1c25400
Out: serial@1c25400
Err: serial@1c25400
Net: No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 24
starting USB...
No controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No controllers found
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
starting USB...
No controllers found
No ethernet found.
No ethernet found.
=>
将驱动复制到内核后编译打包烧录,ifconfig会显示wlan0
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 0C:C6:55:11:32:03
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:5 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#
然后配置wifi
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
ssid="wifi"
psk="123456789"
}
#
通过下面命令连接wifi
# wpa_supplicant -D wext -c /etc/wpa_supplicant.conf -i wlan0
会一直弹下面这些信息,这是什么问题,希望大佬们帮忙指导下。
# wpa_supplicant -D wext -c /etc/wpa_supplicant.conf -i wlan0
Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wlan0: Trying to associate with dc:fe:18:11:11:12 (SSID='wifi' freq=2437 MHz)
Failed to add supported operating classes IE
wlan0: Authentication with dc:fe:18:11:11:12 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=dc:fe:18:11:11:12 reason=3 locally_generated=1
wlan0: Trying to associate with dc:fe:18:11:11:12 (SSID='wifi' freq=2437 MHz)
Failed to add supported operating classes IE
wlan0: Authentication with dc:fe:18:11:11:12 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=dc:fe:18:11:11:12 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wifi" auth_failures=1 duration=10 reason=CONN_FAILED
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="wifi"
wlan0: Trying to associate with dc:fe:18:11:11:12 (SSID='wifi' freq=2437 MHz)
Failed to add supported operating classes IE
wlan0: Authentication with dc:fe:18:11:11:12 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=dc:fe:18:11:11:12 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wifi" auth_failures=2 duration=23 reason=CONN_FAILED
@only_you
老哥,我使用你上面说的命令生成bmp图像直接打不开阿,成jpg打开是花的,这是什么情况阿。是我那里需要修改一下吗.图片传不上来,我是这样执行的。
# fswebcam -d /dev/video0 -S 3 -p UYVY test.bmp
--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
--- Capturing frame...
Skipping 3 frames...
Capturing 1 frames...
Captured 4 frames in 0.12 seconds. (34 fps)
--- Processing captured image...
Unable to load font 'sans': Could not find/open font
Disabling the the banner.
Writing JPEG image to 'test.bmp'.
# [ 588.638546] configfs-gadget gadget: high-speed config #1: c
# fswebcam -d /dev/video0 -S 3 -p UYVY test.jpg
--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
--- Capturing frame...
Skipping 3 frames...
Capturing 1 frames...
Captured 4 frames in 0.21 seconds. (19 fps)
--- Processing captured image...
Unable to load font 'sans': Could not find/open font
Disabling the the banner.
Writing JPEG image to 'test.jpg'.
# [ 623.712339] configfs-gadget gadget: high-speed config #1: c
cheng880126 说:触屏调起来了么???o(* ̄︶ ̄*)o
https://whycan.cn/t_1008.html#p4839
支持 4.3寸 480x272 液晶屏了.
只是屏幕显示还有点点问题。
晕哥,请教下,我使用荔枝派用tiny200驱动480*272的屏,显示演示不对,偏灰,然后有很多条纹,这个是啥情况,是引脚不对还是屏参不对啊
显示效果:
设备树配置:
屏参:
网友的配置例子:
我是没有明白那个hsync_start和hsync_end这些参数后面为什么要用800+20这样的写法,不知道代表什么样的意思。
上面那个显示灰色的已经是我测试显示最好的效果了,荔枝派这个板子,i2c0是复用为lcd的引脚了,不知道这个有咩有影响,我再设备树里屏蔽I2c0也是一样显示灰色。
我记得 uboot那个脚本实现了自动检测启动介质,实现了不同的bootargs。
下面那个问题检查一下dts设备树,可能默认是spi nand,而不是spi nor。
我尝试过再配置中使能bootargs,但是好像没有生效,那我想从tf卡启动应该怎么设置,将设备树flash的status都改为disable?
从flash启动我看有同学改过设备树,我尝试过修改nor的 status = "okay";将nand 的status = "disabled";还是一样的效果,这个是linux设备树,uboot的设备树也要改嘛?
原先这样:
&spi0 {
status = "okay";
spi-nor@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "winbond,w25q128", "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <50000000>;
status = "disabled";
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "u-boot";
reg = <0x000000 0x70000>;
read-only;
};
partition@1 {
label = "kernel";
reg = <0x70000 0x590000>;
read-only;
};
partition@2 {
label = "rom";
reg = <0x600000 0x700000>;
read-only;
};
partition@3 {
label = "overlay";
reg = <0xd00000 0x300000>;
};
};
};
spi-nand@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "spi-nand";
reg = <0>;
spi-max-frequency = <50000000>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "u-boot";
reg = <0x000000 0x100000>;
read-only;
};
partition@1 {
label = "kernel";
reg = <0x100000 0x500000>;
read-only;
};
partition@2 {
label = "rom";
reg = <0x600000 0x2a00000>;
read-only;
};
partition@3 {
label = "vendor";
reg = <0x3000000 0x1000000>;
};
partition@4 {
label = "overlay";
reg = <0x4000000 0x3000000>;
};
};
};
};
大家好,我使用的是论坛里buildroot-tiny200 (F1C100/200s) 开发包
使用
cd buildroot-tiny200
make widora_mangopi_r3_defconfig
得到镜像后使用Win32DiskImager将镜像下载到sd卡后启动如下图所示:
就卡在这里了,重启后在uboot命令行手动输入
setenv bootargs 'console=tty0 console=ttyS0,115200 panic=5 rootwait root=/dev/mmcblk0p2 rw'
然后boot
就能正常进系统了,但是uboot里面没有saveenv指令,下次启动还是会卡死,除非再输入一遍上面的指令。
然后使用spi flash启动后也是卡在这里不动:
希望知道的老哥指定一下哈。
请教一下老哥,这个编译成功后在显示这些是什么意思,文件的下载地址吗?
INFO: cmd: "mkdir -p "/home/xiang/linux/buildroot-tiny200/output/images"" (stderr):
INFO: flash(sysimage-nor.img): writing image partition 'u-boot' (0x80000@0x0)
INFO: flash(sysimage-nor.img): writing image partition 'splash' (0x80000@0x80000)
INFO: flash(sysimage-nor.img): writing image partition 'kernel' (0x500000@0x100000)
INFO: flash(sysimage-nor.img): writing image partition 'rom' (0xa00000@0x600000)
board/allwinner/generic/genimage-nand.cfg:33: no sub-section title/index for 'config'
INFO: cmd: "mkdir -p "/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp"" (stderr):
INFO: cmd: "rm -rf "/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp"/*" (stderr):
INFO: cmd: "mkdir -p "/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp"" (stderr):
INFO: cmd: "cp -a "/tmp/tmp.tQn4VicX1u" "/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp/root"" (stderr):
INFO: cmd: "find '/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp/root' -depth -type d -printf '%P\0' | xargs -0 -I {} touch -r '/tmp/tmp.tQn4VicX1u/{}' '/home/xiang/linux/buildroot-tiny200/output/build/genimage.tmp/root/{}'" (stderr):
INFO: cmd: "mkdir -p "/home/xiang/linux/buildroot-tiny200/output/images"" (stderr):
INFO: flash(sysimage-nand.img): writing image partition 'u-boot' (0x80000@0x0)
INFO: flash(sysimage-nand.img): writing image partition 'splash' (0x80000@0x80000)
INFO: flash(sysimage-nand.img): writing image partition 'kernel' (0x500000@0x100000)
INFO: flash(sysimage-nand.img): writing image partition 'rom' (0x7a00000@0x600000)
然后在output\images\生成的文件是啥意思,咋使用。
我的板子是
我烧录执行sudo sunxi-fel -p spiflash-write 0 ./output/images/u-boot.bin和sudo sunxi-fel -p spiflash-write 0 ./output/images/u-boot-sunxi-with-nand-spl.bin
后在串口上都没有输出
@future
大佬,你这个project要在这个makefile的上一个文件目录下存在。
这个project就是ssd202开发板的一个project的压缩包解压出来的文件夹。
这个我已经解决了,库文件引入路径不对,但是现在屏幕上没有任何显示,就会显示一个log,下面试日志:
/mnt/usb # ls
aml_up~1.img demo dwin_set ld platfo~1.rar system~1
code_1~1.deb demossd lanter~1.deb mindmo~1.pac setup_~1.rar tvcabi~1
/mnt/usb # ./demo
client [881] connected, module:panel
[MI_PANEL_Iclient [881] connected, module:disp
nit][332]LCD env[MI_SYSCFG_GetPanelInfo 50] eTiming = 4, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 2, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 8, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 9, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 10, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 6, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 7, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 11, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 13, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 12, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 14, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 5, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 3, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 38, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 50, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 40, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 43, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 41, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 44, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 42, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 46, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 50, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 45, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 50, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 22, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 23, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 30, hdmiTx = 1 Not Fund!!!
[MI_SYSCFG_GetPanelInfo 50] eTiming = 32, hdmiTx = 1 Not Fund!!!
ironment is Invalid
sstar_FB_SetBlending 402 u8GOP=1,u8win=0 aType=1 u8constAlpha=255
The framebuffer device was opened successfully.
800x480, 32bpp
The framebuffer device was mapped to memory successfully.
么有lvgl的画面显示。
按照说点屏之前初始化,我main函数是这样改的,其他地方没有更改:
.......................
int main(void)
{
MI_PANEL_Init(E_MI_PNL_LINK_TTL); //panel 初始化
MI_DISP_Enable(0); //fb最终还是得经过disp,所以得初始化disp
/*LittlevGL init*/
lv_init();
/*Linux frame buffer device init*/
fbdev_init();
.................
楼猪,我在移植的时候,链接动态库的时候,提示我
/usr/bin/ld: 当搜索用于 ../project/release/nvr/i2m/common/glibc/8.2.1/mi_libs/static/libmi_disp.a 时跳过不兼容的 -lmi_disp
/usr/bin/ld: 找不到 -lmi_disp
/usr/bin/ld: 当搜索用于 ../project/release/nvr/i2m/common/glibc/8.2.1/mi_libs/static/libmi_panel.a 时跳过不兼容的 -lmi_panel
/usr/bin/ld: 找不到 -lmi_panel
collect2: error: ld returned 1 exit status
这是啥情况啊
页次: 1