Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Klaus Küchemann <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
> Am 27.09.2022 um 22:36 schrieb Mark Millard <[email protected]>: > > …..So, for the vintage of U-Boot source that the u-boot ports are > based on, DEBUG would need to be separately defined…. If you mean the freebsd u-boot port, I would suggest to completely ignore older versions/vintages . afaik Fbsd will not accept any device specific patch which didn’t made it (u-boot-) upstream. And u-boot also won’t accept such patches if not extensively validated. So you can use the port to compile but I suggest to use the master stream of u-boot as source ( I think that's what you had in mind anyway) > Am 27.09.2022 um 22:36 schrieb Mark Millard <[email protected]>: > > > So it may be best to always #define LOG_DEBUG in whatever > *.c file(s) before the line with: #include <log.h> Although that seems a bit unusual maybe u-boot planned it that way( placing the #define in line 1 of the files),I haven't investigated that yet … I would begin with a simple #define DEBUG in common/usb.c and then look what happens… and then I would continue with the other files you suggested if there’s no relevant output from usb.c debug… using the master stream of u-boot… Regards and good luck Klaus