Thanks a lot Thierry for considering this thread. On Mon, Mar 4, 2019 at 7:25 PM Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > > Or it could indicate that something is > wrong when loading files from the root filesystem. When I used the downstream kernel and L4T filesystem, there was no problem regarding filesystem mounting. > All of the memory related configuration is part of a file called the > BCT. I think if you could provide that it would be very useful to have. Please find the link to our BCT: https://drive.google.com/open?id=1Az4nDIImCm14cnDSfHeBPlQYlYijGMrS > Also, it looks like you're using the Jetson TK1 device tree to boot, so > can I assume you haven't modified it at all? Yes, I modified the downstream kernel's dtb by generating new pinmux using Nvidia's dts generation tool but for upstream kernel I haven't modified any dts. > Other bits of information that would be good to know are how you are > generating the BCT and your boot images, what exactly you do to flash > the board and which release of L4T you use. We run Shmoo memory characterization tool and get cfg file from that. Then we convert that cfg to BCT (using mkbct command I guess). We were never able to flash the board using nvflash/flash.sh utility. So 1. We build and flash u-boot & BCT using tegra-uboot-flasher. 2. We build kernel using make separately using sources available on Nvidia download center. 3. We use apply_binaries.sh to copy tegra related files to sample file system downloaded from Nvidia download center. 4. We mount the emmc/SD-card using u-boot's ums command on our Linux host, and copy the whole filesystem, kernel and DTB to it. We are using R21.7 > Perhaps also try to run a recent linux-next just to exclude any issues > that may have been part of the 4.8.0-rc7 that you tested. Ok I will build kernel using linux-next and update here. Thanks again.
