ASSERT TerminalConIn.c(2078): ((BOOLEAN)(0==1))

Hi,

  1. as my previous question, “what” did you change? I mean we all know device tree change is needed, but we don’t know if you change the correct thing.

  2. The flash log will tell you which device tree is in use for bootloader, you can share the flash log too.

I have set the
serial@3100000 (and the other uarts) status to disabled

Let me check the flash log

Please directly attach the finalized dts converted back from dtb.

tegra194_disabled_uart.dts (390.0 KB)

need to check your flash log too.

Please also share a video which records the issue you saw.

Also, are you sure the UART console does not print anymore?

When we send uart data it will do this, once we stop sending uart data it will stop.

still need your flash log to check.

Yes looking to get it.

1 Like

Here is the flash log,
It seems it is using a different dtb file for the tbcdtb?
copying tbcdtbfile(/home/ubuntu/Linux_for_Tegra/kernel/dtb/tegra194-p3668-0001-p3509-0000.dtb)... done.

Here are my steps
I take above mentioned dts file
dtc -I dts -O dtb -q -o Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000_disabled_uart.dtb /home/ubuntu/tegra194_disabled_uart.dts

And my p3668.conf.common changes:

Flash command:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_l4t_t194_qspi_p3668.xml" --showlogs jetson-xavier-nx-devkit-emmc internal

It seems its taking tegra194-p3668-0001-p3509-0000.dtb as the dtb file, but I dont understand why?
In jetson-xavier-nx-devkit-emmc.conf it does mention DTB_FILE=tegra194-p3668-0001-p3509-0000.dtb; so for the kernel dtb file I can understand why, as this overwrites the setting in p3668.conf.common, but why for the bootloader?

FlashLogDisabledUarts.txt (179.3 KB)

could you use flash.sh to flash emmc first to see which parameter does flash.sh take?

This also seems to use the wrong dtb file
copying tbcdtbfile(/home/ubuntu/Linux_for_Tegra/kernel/dtb/tegra194-p3668-0001-p3509-0000.dtb)... done.

Flash command:
sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

FlashLogEmmc.txt (56.3 KB)

Please add that field to jetson-xaiver-nx-devkt-emmc config too.

Tried it but still uses the other one.
FlashLogEmmcAddedBTCDTBToJetsonConfig.txt (54.1 KB)

May I check your jetson-xavier-nx-devkit-emmc.conf?

# Copyright (c) 2019-2022, NVIDIA CORPORATION. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#  * Redistributions of source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#  * Redistributions in binary form must reproduce the above copyright
#    notice, this list of conditions and the following disclaimer in the
#    documentation and/or other materials provided with the distribution.
#  * Neither the name of NVIDIA CORPORATION nor the names of its
#    contributors may be used to endorse or promote products derived
#    from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY
# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
# OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# p3509-0000+p3668-0001-qspi-emmc.conf: configuration for "P3668(SKU1) + P3509"
# (T194 P3518).

# Sourced by bash script.
# Disable unused variable check. Most of these variables are used in an outer
# script that sources this file.

source "${LDK_DIR}/p3668.conf.common";
EMMC_CFG=flash_l4t_t194_spi_emmc_p3668.xml;
DTB_FILE=tegra194-p3668-0001-p3509-0000.dtb;
TBCDTB_FILE=tegra194-p3668-all-p3509-0000_disabled_uart.dtb;
EMMCSIZE=17179869184;
RECROOTFSSIZE=100MiB;

# Rootfs A/B:
if [[ "${ROOTFS_AB}" == 1 && "${ROOTFS_ENC}" == "" ]]; then
        rootfs_ab=1;
        EMMC_CFG=flash_l4t_t194_spi_emmc_p3668_rootfs_ab.xml;
# Disk encryption support:
elif [[ "${ROOTFS_AB}" == "" && "${ROOTFS_ENC}" == 1 ]]; then
        disk_enc_enable=1;
        EMMC_CFG=flash_l4t_t194_spi_emmc_p3668_enc_rfs.xml;
# Rootfs A/B + Disk encryption support:
elif [[ "${ROOTFS_AB}" == 1 && "${ROOTFS_ENC}" == 1 ]]; then
        rootfs_ab=1;
        disk_enc_enable=1;
        EMMC_CFG=flash_l4t_t194_spi_emmc_p3668_enc_rootfs_ab.xml;
fi;

Let us try on our side.

Thanks! Thanks for the quick help! :)

Any updates?

Also I was wondering, we have never had this issue(UEFI reacting to uart data) before updating to Jetpack 5.1.1. We were on 4.6.2 before. Could this be an issue in itself? Also tested it on a Nvidia dev kit carrier board with Xavier NX and it has the same issue. So its not hw related.

It needs more time as we have lots of issue on queue waiting for testing.

And jp4.6.2 does not have UEFI at all. So there is no need to discuss about this with jp4.6.2 actually.