We have received a nano module and wanted to build.BSP code Can we use nan stock BSP on it and make changes if needed while building from source

We have received a nano module and wanted to build.BSP code Can we use nan stock BSP on it and make changes if needed while building from source.

Not a full answer, but some thoughts on this:

  • If a carrier board layout differs, then you’ll need to modify the device tree.
  • In a command line flash you will find several “*.conf” files for the board target. These are human readable scripts, sometimes including files for subcomponents.
    • If the target example is jetson-nano-emmc, then the file used is jetson-nano-emmc.conf.
    • Each target file either directly or indirectly is divided into parts for the target module, plus parts related to the target carrier board (e.g., you might see a symbolic link or includes based numeric designations which are designations of particular carrier boards or modules).
  • You can easily copy those .conf files and make your own custom versions with any edits.
  • You can log a flash on command line and this tells you where every device tree and image comes from. Example for a dev kit with logging:
    sudo ./flash.sh jetson-nano-devkit mmcblk1p1 2>&1 | tee log_flash.txt
    (it is the " 2>&1 | tee log_flash.txt" which adds logging)
  • Most of the rootfs image is from “Linux_for_Tegra/rootfs/”, but kernel, extlinux.conf, and device tree will change based on the flash target. Check the flash log to know what is modified in “/boot” before creating the flash image. Or “reuse” the image (with the “-r” option) in “Linux_for_Tegra/bootloader/system.img” to avoid any modification of “/boot” content (it’ll use exaclty that image and not create one from “rootfs/”).
  • Getting the rootfs the way you want and then cloning is often a good idea. However, you do need to look out for everything being cloned; if you don’t want a user account and password added, then you’d have to remove it in the clone. Similarly if a network rule is based on a MAC address and the MAC is not the same one on different modules.

Expect to use a modified device tree, but everything else will likely be useful without modification. You might want to make other modifications, but most of those are optional.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.