Giter VIP home page Giter VIP logo

Comments (11)

tkammacher avatar tkammacher commented on June 3, 2024

I assume you have downloaded and flashed both the APP and EBT partitions, as described in https://github.com/InES-HPMM/linux-l4t/wiki/l4t_prebuilt_image.

One thing that may be different is the environment variables of U-Boot. Could you hit a key when U-Boot is starting to interrupt booting. Then enter printenv to show the environment variables and show them here?

Also could you try to boot Kernel 3 (hdmi2csi (HDMI-B disabled))? Just hit the 3 and Enter after you see this in U-Boot:

p2371-2180 eMMC boot options
1: primary kernel
2: hdmi2csi
3: hdmi2csi (HDMI-B disabled)
Enter choice:

from linux-l4t.

ivanovean avatar ivanovean commented on June 3, 2024

I have a same problem.
Trying to boot with other options - not successfull.
This is result of printenv:

Tegra210 (P2371-2180) # printenv
arch=arm
baudrate=115200
board=p2371-2180
board_name=p2371-2180
boot_a_script=load ${devtype} ${devnum}:${bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_extlinux=sysboot ${devtype} ${devnum}:${bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=mmc1 mmc0 usb0 pxe dhcp
bootcmd=run distro_bootcmd
bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi
bootcmd_usb0=setenv devnum 0; run usb_boot
bootdelay=2
cpu=armv8
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
fdt_addr_r=0x82000000
fdt_copy_node_names=/memory-controller@7001b000
fdt_copy_src_addr=0x83080000
fdt_high=ffffffffffffffff
fdt_remove_property_names=/pinmux@700008d4/pinctrl-names
initrd_high=ffffffffffffffff
kernel_addr_r=0x80080000
loadaddr=0x80080000
lp0_vec=0x1000@0xff2bf000
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
nvdumper_reserved=0xff23f000
pxefile_addr_r=0x90100000
ramdisk_addr_r=0x83100000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${bootpart} bootfstype; then run scan_dev_for_boot; fi; de
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x90000000
soc=tegra210
stderr=serial
stdin=serial
stdout=serial
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi
vendor=nvidia
Environment size: 2436/8188 bytes

from linux-l4t.

tkammacher avatar tkammacher commented on June 3, 2024

Hi @ivanovean
Could you enter U-Boot and enter these commands:

Tegra210 (P2371-2180) # setenv fdt_remove_property_names
Tegra210 (P2371-2180) # saveenv

Then reboot. Does this help?
(Source: #1)

from linux-l4t.

ivanovean avatar ivanovean commented on June 3, 2024

Hi @tkammacher
It really helped. Now everything works fine.

Many thanks!

from linux-l4t.

tkammacher avatar tkammacher commented on June 3, 2024

Good to hear. Maybe @sergey789 you could try this workaround too?

from linux-l4t.

rrcarlosrodriguez avatar rrcarlosrodriguez commented on June 3, 2024

Hi! I have the same problem described. I'm working based on https://github.com/InES-HPMM/linux-l4t/wiki/l4t_prebuilt_image.

My files checksums are:
68279df473154c3fe6e3d34e8d9f9a40dc4c9f82 tx1_hdmi2csi_l4t_r24_2.1_g1685ac7.img
8330467319791ba018c6d4568d916c6213e85553 tx1_hdmi2csi_l4t_r24_2.1_gdd13899-dirty_EBT.img

My u-boot environment is:

arch=arm
baudrate=115200
board=p2371-2180
board_name=p2371-2180
boot_a_script=load ${devtype} ${devnum}:${bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_extlinux=sysboot ${devtype} ${devnum}:${bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=mmc1 mmc0 usb0 pxe dhcp
bootcmd=run distro_bootcmd
bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi
bootcmd_usb0=setenv devnum 0; run usb_boot
bootdelay=2
cpu=armv8
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
fdt_addr_r=0x82000000
fdt_copy_node_names=/memory-controller@7001b000
fdt_copy_src_addr=0x83080000
fdt_high=ffffffffffffffff
initrd_high=ffffffffffffffff
kernel_addr_r=0x80080000
loadaddr=0x80080000
lp0_vec=0x1000@0xff2bf000
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
nvdumper_reserved=0xff23f000
pxefile_addr_r=0x90100000
ramdisk_addr_r=0x83100000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${bootpart} bootfstype; then run scan_dev_for_boot; fi; done
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x90000000
soc=tegra210
stderr=serial
stdin=serial
stdout=serial
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi
vendor=nvidia

I already tried with the fdt_remove_property_names hack mentioned in here

But it didn't work! Any suggestion about something else to try?

Thanks!

from linux-l4t.

tkammacher avatar tkammacher commented on June 3, 2024

Hi @rrcarlosrodriguez

I have diffed your Uboot environment to mine, and it's pretty much the same:

diff ubootEnvRR.txt ubootEnvZhaw.txt
11c11
< boot_targets=mmc1 mmc0 usb0 pxe dhcp
---
> boot_targets=mmc1 mmc0 usb0 pxe dhcp

Do you get the exact same error messages in U-Boot as in the first post of this issue?
Since you have the same environment as me, you should not get this error.
If you have different error messages, could you post them (best would be the complete U-Boot log)?

And which version of L4T have you been running on your TX1 before flashing our prebuilt images? Was it R24.2.1?

from linux-l4t.

rrcarlosrodriguez avatar rrcarlosrodriguez commented on June 3, 2024

Hi @tkammacher !

This is the complete boot log:
tegra-boot-fail.txt

I've been using 24.2 in all my tests! Should I move to 24.2.1 for any specific reason?

from linux-l4t.

tkammacher avatar tkammacher commented on June 3, 2024

As far as I am aware, an important change from 24.2 to 24.2.1 is the handling of the devicetree in Uboot, specifically for pinmux configuration. See #1 and [1].

We had issues before with 24.2 and a kernel/dt for 24.2.1. It appears that somewhere on the TX1 there is still some file or environment variable that causes issues, when you are combining 24.2 and 24.2.1. I thought we had solved the problem by overwriting the EBT partition with our custom Uboot (CONFIG_OF_REMOVE_PROPERTIES disabled), but it seems that is not sufficient.

I would suggest you either flash the TX1 first with 24.2.1 and then our custom images, or you try to reset this environment variable in uboot:

Tegra210 (P2371-2180) # setenv fdt_copy_node_names
Tegra210 (P2371-2180) # saveenv

Please let me know if any of these solutions helps..

[1]
http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/u-boot.git;a=commit;h=ec1720cded3a3e89967f2f70294b84ae3c29dfc8

from linux-l4t.

rrcarlosrodriguez avatar rrcarlosrodriguez commented on June 3, 2024

I flashed a 24.2.1 image and then I tested your image again and it works. That mismatch between versions was causing the error.

Thanks a lot!

from linux-l4t.

tkammacher avatar tkammacher commented on June 3, 2024

It is now necessary to first flash the TX1 to the official L4T 24.2.1 by Nvidia. Users can use the Jetpack tool.
After this, our pre-built image can be flashed.

The instructions on https://github.com/InES-HPMM/linux-l4t/wiki/l4t_prebuilt_image have been adjusted to include this prerequisite.

from linux-l4t.

Related Issues (7)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.