Jump to content
New Wiki - User & Developer Guide ×

tooz

Tinker Engineer
 View Profile  See their activity

  • Content Count

    627

  • Joined

  • Last visited

  • Days Won

    42

Posts posted by tooz

  2. Posted

    hello @Frank, 

    On 4/10/2025 at 8:14 PM, Frank said:

    1. Do you have some kind of documentation for the commands of the asus-docker-env. We were not able to find something.

     

    To set up the environment: 

    1. Install docker and asus-docker-env
    2. Follow GitHub - asus-iot/asus-docker-env to run asus_docker_env_run
    3. Install necessary packages below : 
    sudo apt-get install libgmp-dev
sudo apt-get install libmpc-dev
sudo apt-get install bsdmainutils
sudo apt-get remove live-build
git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131
cd live-build
rm -rf manpages/po/
sudo make install -j8
    1. Use build.sh to build code base

  4. Posted

    hello @Frank 

    22 hours ago, Frank said:

    2. The other question is if there is a documentation about the changes from the v3.0.27 to the latest manifest?

     

    1. Disable auto login for the uart console and the dekstop environment.
    2. Force the user linaro to change its password at the linaro's next login
    3. Eable ROCKCHIP_EFUSE config for u-boot to set cpuid from efuse to fix the issue that all CPU has the same ID

  6. Posted

    if you're using a x86 wsl there might be something relates to architecture similar to: https://askubuntu.com/questions/1006846/chroot-onto-arm-based-image it's necessary to have qemu supported in aarch64/ arm64. some reference: https://www.cnx-software.com/2016/05/10/how-to-run-ubuntu-16-04-aarch64-64-bit-arm-cloud-images-on-your-intelamd-linux-computer/ 

    the easiest way to cross compile would be having a ubuntu host machine

  8. Posted

    hello @Frank, 

    34 minutes ago, Frank said:

    chroot: failed to run command '/usr/bin/env': Exec format error

    did this happen when you run ./build.sh? you might want to install qemu-user-static and then copy it to the mounted point e.g. /mnt/usr/bin  

    sudo apt install qemu-usr-static
sudo cp /usr/bin/qemu-arm-static /path/to/mount/usr/bin

    and then restart the system 

    systemctl restart systemd-binfmt.service

     

  13. Posted

    hello @HaTo, 

    if you're using a supported lte module and it's recognised by the os, there's no extra work in order to make the module work. i tried to use a quectel em05 m.2 lte + sim to reproduce the issue and i'm not able to present the issue. (you can use command networkcli or the network manager on the top right to check if the lte is working) 

    mgThXQW.png

    the design of nano sim slot connection of tinker board 3n follows the specifications of quectel lte modules. i'd recommend to check with quinton hazell for details, or try using another module that's officially supported: Tinker Board 

  14. Posted

    hello @Sebastian, 

    to compile the dtbo:  

    dtc -@ -O dtb -o disable-gpu-wifi.dtbo disable-gpu-wifi.dts

    (or, you can download the dts & dtbo from this link )

    once you have the dts and dtbo, move them to the /boot/overlays and modify the config.txt 

    cp disable-gpu-wifi.dtbo /boot/overlays/
sudo vim /boot/config.txt
overlay=disable-gpu-wifi
sudo reboot

    to verify that gpu is disabled: 

    check if the directory /sys/devices/platform/ffa30000.gpu/ exists; if it's non existent = gpu is disabled 

     this is what in the disable-gpu-wifi.dts:  

    /dts-v1/;

/plugin/;

 

/ {

    compatible = "rockchip,rk3288";

 

    fragment@0 {

        target = <&gpu>;

        __overlay__ {

            status = "disabled";

        };

    };

   

    fragment@1 {

        target-path = "/wireless-wlan";

        __overlay__ {

            status = "disabled";

        };

    };

};

     

×
×
  • Create New...