Hi again,
whats the correct way to enable debug?
i tried this (add #define DEBUG in common.h): https://stackoverflow.com/questions/31185603/enabling-debug-mode-for-denx-u-...
=> uboot does not load (version-line does get printed)
then i've found this:
https://lists.denx.de/pipermail/u-boot/2003-August/002196.html
but DBGFLAGS does not exist in config.mk, i found also no dbg,debug or similar in Makefile and config.mk
i found some debug-options in menuconfig, but don't know which is the right one for this...
maybe DEBUG_LL [=n] ?
regards Frank
Gesendet: Sonntag, 23. Juni 2019 um 12:46 Uhr Von: "Frank Wunderlich" frank-w@public-files.de An: u-boot@lists.denx.de Betreff: [U-Boot] bootloop with 2019-07 on Bananapi-r2
Hi,
i have an issue with 2019-07 (rc1 and rc4) on Bananapi-R2 (mt7623).
from the bootlog (seems like WDT triggers a reset):
U-Boot 2019.07-rc1-bpi-r2-00002-gb692d6e6b4 (Jun 23 2019 - 11:39:57 +0200)
CPU: MediaTek MT7623 E3 DRAM: 2 GiB WDT: Started with servicing (60s timeout)
[USBD] USB PRB0 LineState: 0
the last line "[USBD]" is first line after reset (= first line after power on).
No issue on 2019-04 final, here i see no WDT-line:
U-Boot 2019.04-bpi-r2-00003-g0870aec1fb (Jun 23 2019 - 12:36:20 +0200)
CPU: MediaTek MT7623 E3 DRAM: 2 GiB MMC: mmc@11230000: 0, mmc@11240000: 1 Loading Environment from MMC... Boot From SD(id:1)
*** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial Net:
any idea how to get the cause? it is between 2019-04 final and 2019-07-rc1
https://github.com/frank-w/u-boot/tree/2019-04-bpi-r2 <<< affected https://github.com/frank-w/u-boot/tree/2019-07-bpi-r2 <<< not affected (=rc1, but tested also rc4)
regards Frank
U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot