Whe Edge2 doesn’t have M2 key slot using diff switch between 3.1 usb and M2 like VIM3/VIM3L done?
Also can i somehow get PCIe M2 by USB3.1 it looks like it has 4 useful lines but missing PCIE20_CLKP & PCIE20_CLKN that are under RK3588s soc.
Hello @Vinky
You can’t do this, because it missed CLK signals.
If you need M.2 slot you can consider our another RK3588 SBC.
The buy now button is dead. Also, please provide a link to the BSP / yocto build and the .dts/.dtsi for this board. Looking at the picture it is very impressive and well laid out.
Update: the dead buy now is in the link posted, going into the shop it is active.
Very impressive add-on board.
Hello @foxsquirrel ,
About the manuals we have uploaded to Namtso Downloads, you can check the development manual to download the code and it also includes how to build the image. And the user manual you can check in this website.
Good Morning @Jacobe
Thank you for posting that information. We need the actual yocto build environment, not the yocto sdk for the board. We use core-image-weston and build upon it with our own layers. Github is having some issues and the repo is hanging up, that might clear up later in the day.
We need the actual yocto build environment, not the yocto sdk for the board. We use core-image-weston and build upon it with our own layers.
I’m not for sure the yocto build environment means…? The tools which were installed by apt?
About the DTS you mentioned last time, you can find it in NAMTSO github repo.
@Jacobe I was referring to the build set up that was used to create the actual yocto SDK. It would be what spawned the SDK. It is much simpler to maintain and modify than the sdk. I will look over the repo again to see if I missed it.
How to compile SDK:
./build.sh lunch select namtso_a10_3588_defconfig
export RK_ROOTFS_SYSTEM=yocto
./build.sh
Maybe you can refer to device/rockchip/rk3588/namtso_a10_3588_defconfig
Thank you for providing assistance on this.
How would I build core-image-weston. Typically when everything needed is setup its $ bitbake core-image-weston.
We must build up from core-image-minimal and core-image-weston using our meta-layers. Typically, I don’t recall using the yocto produced SDK, it has always been in the top level build environment.
Try the following command:
cd yocto
source oe-init-build-env
bitbake core-image-minimal -C rootfs -R conf/rksdk_override.conf
A big thank you to the helpful member on the Khadas forum! We appreciate the guidance and will be trying out this command later today as suggested:
@Mark-Wan-Namtso
Would you have the link to the actual libmali that was used. The mirror has issues and I would like to clean that up before digging into fixing the patch issues.
WARNING: rockchip-libmali-1.0-r0 do_fetch: Failed to fetch URL git://github.com/JeffyCN/mirrors.git;protocol=https;branch=libmali;, attempting MIRRORS if available
ERROR: linux-rockchip-5.10-r0 do_patch: Could not apply patches for namtso-a10-3588.
ERROR: linux-rockchip-5.10-r0 do_patch: Patch failures can be resolved in the linux source directory /home/fred/yocto/namtso/yocto/build/tmp/work-shared/namtso-a10-3588/kernel-source)
ERROR: linux-rockchip-5.10-r0 do_patch: ExecutionError('/home/fred/yocto/namtso/yocto/build/tmp/work/namtso_a10_3588-poky-linux/linux-rockchip/5.10-r0/temp/run.do_patch.1039213', 1, None, None)
ERROR: Logfile of failure stored in: /home/fred/yocto/namtso/yocto/build/tmp/work/namtso_a10_3588-poky-linux/linux-rockchip/5.10-r0/temp/log.do_patch.1039213
Maybe you can refer to: yocto/build/conf/include/rksdk$ cat libmali.conf
Its source is: external/libmali