The good news is that I compiled u-boot to a state that it does not put out anything on UART0: git diffĭiff -git a/arch/arm/mach-tegra/board186.c b/arch/arm/mach-tegra/board186.c Unfortunately, I haven’t found a solution that works as described and hopefully can post a git diff of u-boot here, once I figured it out… Since I found a couple of threads regarding the disabling of UART logging here and all around the internet for other devices, we may not be the only ones with that requirement. We are aware, that this reduces the possibilities of in field diagnosis but when there are problems in the final product some day, customers would have to send in the system anyway and we will have the means to switch to a bootloader with debug messages. We intend to use all the UARTS available on the board to connect devices that may get confused when they receive stuff that is not meant for them. I’m currently in the process of compiling u-boot and of finding the correct combination of CONFIG_switches that ill finally silent the UART logging.Ĭompiling already works fine but I still havn’t found the correct switches, because I already (literally) set a handful of them, but still the messages are the same. Somewhere here I found a post, where they were discussing re-compiling the bootloader as last resort. cfg file for the bootloader does not switch off the messages. This is more or less what I already feared by browsing this form: the switch in the. Obviously it’s just the u-boot, meaning the kernel is silenced. Reserving fdt memory region: addr=80000000 size=10000 Retrieving file: /boot/extlinux/nfĢ2051696 bytes read in 571 ms (36.8 MiB/s)Īppend: root=/dev/mmcblk0p1 rw rootwait console=none OS=l4t fbcon=map:0 net.ifnames=0 memtype=0 video=tegrafb no_console_suspend=1 nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2.1 rialno=1422920005935 sdhci_tegra.en_boot_part_access=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 Net: eth0: any key to stop autoboot: 2 1 0 *** Warning - bad CRC, using default environment Thanks again Wayne for your extended help!
0 Comments
Leave a Reply. |