wlan0 not show up on Luckfox pico ultra W after using complied buildroot image from luckfox SDK

2024-09-20 9:47

hello, I'm trying to build the custom buildroot image for luckfox pico ultra w, the system boots just fine but the wlan0 is not showing up. It seems like the driver is not working or missing. if I use the latest official release everything works fine. I only added a few packages for buildroot .config and some kernel drivers. I also pulled the latest update from the GitHub SDK repo but it's still not working. Is there anything I am missing? thanks!

2024-09-20 10:03

Hello, `wlan0` requires a driver to be loaded in order to appear. The relevant driver source code can be found at `<luckfox pico SDK>/sysdrv/drv_ko/wifi`. You can move the `/oem/usr/ko` from another image to your custom rootfs (since the luckfox pico ultra W needs to load firmware from a fixed location, you need to ensure that the `/oem/usr/ko` path also exists in your custom rootfs). After ensuring that all drivers are present, execute `/oem/usr/ko/insmod_ko.sh` (make sure to add executable permissions).

2024-09-20 13:03

I'm not sure where the custom rootfs will be, can you point to the exact location in the SDK? Also after executing the insmod_ko.sh I can rebuild the image, right? I just want to confirm thank you!

2024-09-21 2:20

I am not quite sure whether the "custom buildroot image" you mentioned refers to building an image by adding new packages based on the SDK, or constructing the rootfs using another buildroot version and then packaging the image back in the SDK.

The insmod_ko.sh script should be executed on the Luckfox Pico board. This step is performed after building the image.

To further clarify your issue, please provide the boot log information (preferably obtained via serial console).

2024-09-21 4:33

Crocodile wrote: ↑2024-09-21 2:20 I am not quite sure whether the "custom buildroot image" you mentioned refers to building an image by adding new packages based on the SDK, or constructing the rootfs using another buildroot version and then packaging the image back in the SDK.

The insmod_ko.sh script should be executed on the Luckfox Pico board. This step is performed after building the image.

To further clarify your issue, please provide the boot log information (preferably obtained via serial console).

hello, thank you for your help, the "custom buildroot image" I mentioned refers to building an image by adding new packages based on the SDK. And about the issues, I tested again, and the wlan0 seems to show up now but I need to make a slightly change to the insmod_wifi.sh script. I'm not sure why the original one does not work, but I might still need to find out why. all I did was remove the check for "W" Here is the code in insmod_wifi.sh

Code: Select all

#aic8800
	insmod cfg80211.ko
	insmod libarc4.ko
	insmod ctr.ko
	insmod ccm.ko
	insmod libaes.ko
	insmod aes_generic.ko
	insmod aic8800_bsp.ko
	sleep 0.2
	insmod aic8800_fdrv.ko
	sleep 2
	insmod aic8800_btlpm.ko
	sleep 0.1

i remove check for "W" and move this block to the top of the script after

Code: Select all

export PATH

then after the reboot wlan0 show up.

2024-09-21 4:45

I also have another question, I'm very interested in constructing the custom rootfs in the SDK, my goal here is to add the script files to /root/ (and other directories as well like /etc, /var...) so that after I burn the buidlroot image I don't have to re-copy it every time. or there is another way to back up the rootfs image from NAND flash of the luckfox. It would be very helpful if you could guide me through it. Thank you very much!

2024-09-21 5:55

The latest version of the SDK requires that after running ./build.sh or ./build.sh rootfs, you enter the <Luckfox Pico SDK>/output/out/rootfs_uclibc_rv1106 directory (the structure in this directory is almost identical to the final rootfs structure in Luckfox Pico). Make any necessary additions or modifications here. Then, return to the SDK root directory and execute ./build.sh firmware to package a custom image.

The principle is to modify the file structure in the final step before packaging it into a rootfs image. During the packaging process, the OEM partition content and app content will also be added, which is why the rootfs structure is “almost” identical to the one eventually flashed onto the Luckfox Pico.