Search Results

Thanks a lot for the feedback. The problem was related to my attempt to use the GDB client to initialize DDR, whereas this should have been done on GDB server side. Now the flashing of u-boot binary via JLink debugger is almost successful. It fails only and always at the same single chunk. The relevant log is below: Source Code (101 lines) So, it fails always on this chunk: Source Code (1 line)The DDR is initialized with calibrated data. So, if it always fails at the same chunk, this is probably…

I could figure out that it was only the WDOG1 register with address 020BC000 that could not be read by JLink. All other registers were read and written without problem. However I have faced another problem when trying to debug u-boot. The u-boot is built to reside in external DDR at address 0x17800000. I have a proper GDB script to initialize DDR memory and the clocks. This GDB script starts with the following lines: Source Code (12 lines)The takes place at the first line which establishes conne…

Hi, We use a custom board with IMX6Q6 to deploy u-boot or Yocto OS via USB and all works fine so far. However, when we try to debug the u-boot from Ubuntu 22.04 host, we cannot convince our J-Link Ultra+ (with 10-pin JTag connected via the J-Link Adapter CortexM intermediate board) to flash it to the external DDR3 although we use the same clock and DDR3 initialization configuration which we used when flashing the u-boot by USB. To check simpler things we ran command line GDB server and supplied …