On 2017-05-11 14:12, Jagan Teki wrote:
On Wed, May 10, 2017 at 7:11 PM, Manfred Schlaegl manfred.schlaegl@ginzinger.com wrote:
Using u-boot-2017.05 on i.MX6UL we ran into following problem: Initially U-Boot could be started normally. If we added one random command in configuration, the newly generated image hung at startup (last output was DRAM: 256 MiB).
I've observed the similar issue where the startup hang before relocating [1], couldn't get any abort or panic message on the console. Do you have any suggestion on 'how to debug' I've tried gdb but couldn't succeed.
[1] https://patchwork.ozlabs.org/patch/760018/
thanks!
Hi!
I'm sorry for the late answer but, as you can see by my last message, I'd also had problems to identify my problem correctly...
Generally my experience from the last 10 years in embedded systems is, that with using u-boot and linux a physical debugger (like BDI or even some FTDI things with OpenOCD) is very rarely needed. BUT: finding problems at u-boot low-level is definitively a thing were such a debugger is necessary ;-).
I used a Segger JLink and gdb. You can try to use http://www.openocd.de/
Hope it helped .. a bit.
Best regards, Manfred