[U-Boot] How to debug uboot code on Samsung S5pv210 chip by eclipse and JTAG?
I have found some tutorials to debug uboot an samsung 2440 and 6410 chip by JTAG .I also known I must write a init program or script first .But I don't known to debug uboot on S5pv210 and write the init DDR script.Anyone gives me a guide to establish the process. Thanks.
Dear 坚石,
I have found some tutorials to debug uboot an samsung 2440 and6410 chip by JTAG .I also known I must write a init program or script first .But I don't known to debug uboot on S5pv210 and write the init DDR script.Anyone gives me a guide to establish the process. Thanks.
What does eclipse have to do with it?
What debugger do you use? OpenOCD/BDI/Peedi/... ?
Best regards, Marek Vasut
Dear =?GB2312?B?vOHKrw==?=,
In message CAKM5mEg9rbi8yLsQfjawE74gh-eu9p7prSgP=TSX7P9RJiMQAw@mail.gmail.com you wrote:
I have found some tutorials to debug uboot an samsung 2440 and 6410 chip by JTAG .I also known I must write a init program or script first .But I don't known to debug uboot on S5pv210 and write the init DDR script.Anyone gives me a guide to establish the process.
Why would you need to initialize DDR though the JTAG debugger?
The common use of a JTAG debugger to debug U-Boot is _not_ to initialize the system at all though JTAG, as this will be done by U-Boot. Just start the CPU out of reset.
Actually on quite a number of architectures U-Boot expects to find a virgin CPU right out of reset, and any previous meddling with the configuration may have unexpected (and usually adverse) effects. Better don't do it.
Best regards,
Wolfgang Denk
Dear Wolfgang Denk,
Dear =?GB2312?B?vOHKrw==?=,
In message <CAKM5mEg9rbi8yLsQfjawE74gh-
eu9p7prSgP=TSX7P9RJiMQAw@mail.gmail.com> you wrote:
I have found some tutorials to debug uboot an samsung 2440 and6410 chip by JTAG .I also known I must write a init program or script first .But I don't known to debug uboot on S5pv210 and write the init DDR script.Anyone gives me a guide to establish the process.
Why would you need to initialize DDR though the JTAG debugger?
The system has some BootROM, which does the DDR init. But without special header in the NAND, the DDR won't be inited ... that was my point about initing it via the debugger.
The common use of a JTAG debugger to debug U-Boot is _not_ to initialize the system at all though JTAG, as this will be done by U-Boot. Just start the CPU out of reset.
Actually on quite a number of architectures U-Boot expects to find a virgin CPU right out of reset, and any previous meddling with the configuration may have unexpected (and usually adverse) effects. Better don't do it.
Best regards,
Wolfgang Denk
Best regards, Marek Vasut
Dear Marek Vasut,
In message 201205301309.23163.marex@denx.de you wrote:
Why would you need to initialize DDR though the JTAG debugger?
The system has some BootROM, which does the DDR init. But without special header in the NAND, the DDR won't be inited ... that was my point about initing it via the debugger.
That's actually a different topic - how to install a U-Bootimage to NAND. The question here was how to debug U-Boot, so it seems a valid assumption that there is actually some code to debug. And in this case the JTAG debugger is supposed not to mess with the initialization, but leave the system alone so it run the same code you actually want to debug.
Best regards,
Wolfgang Denk
participants (4)
-
Marek Vasut -
Marek Vasut -
Wolfgang Denk -
坚石