On 14:06 Sun 22 May     , Bear wrote:
> hi,
> I am using a old version of u-boot. It seems like 1.3.2. This
> version of u-boot has been modified to suit my special board which
> has no NOR flash.
As far as I remember I had the support of the dcc in U-Boot much later

Do you use a mini2440?
> 
> BTW: I have done a lot of test these days.
> 1. wiggler: I can "reset" my board with "reset" command. But if I
> run "reset init" or "reset halt", my board would only reset but not
> halted. And OpenOCD would told me "timed out" waiting the board
> halt. But, what the strange thing is, if I just run "halt" command
> and NOT run any command related to "reset" BEFORE it, my board CAN
> enter halt status.
> 
> 2. jlink: I can run "reset", "reset halt", "reset init" command
> successfully, but I cannot download anything into my board, the DCC
> error occurred. If I run "arm7_9 dcc_download disable"(maybe the
> spelling is incorrect, I am not in Linux now) and then tried to
> debug my u-boot in eclipse, the download progress can finished
> without any error, but in fact, the program cannot be executed. It
> always stopped with a SIGNAL. Even I run resume in OpenOCD, it also
> cannot be executed.
> 
> 3. I don't know why this happened, but some days before, "reset"
> command cannot be done if I use wiggler cable to debug my board.
> There are always some errors when I execute "reset", "reset halt" or
> "reset init" and my board cannot be reset. But at that time, I can
> run "halt" command and debug my u-boot in eclipse, the only problem
> is the "current line" function cannot work property, I mean, the
> line which highlighted in eclipse is not the line currently run.
> Maybe you can find this in one of my before email. Maybe this is
> caused the upgrade of my Debian system?
It's looks like a pll init issue
are you about them?
> 
> I apologized for my bad English but I still hope you can understand
> what I talked about. :)
Don't worry I here much worse english everyday

Best Regards,
J.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to