HI,

        I try a mini2440 recently and it's work fine

        I've not access to a 2410 board but I try on at91 ditto

        I went take a look in shenzhen if I can foud on but did not

Best Regards,
J.
On 10:16 Mon 23 May     , Bear wrote:
> hi,
> > As far as I remember I had the support of the dcc in U-Boot much later.
> I am sorry but I can't understand your meaning. Are you mean only
> the version of u-boot > 1.3.2 support dcc?
> 
> > Do you use a mini2440?
> Oh no. I use Uptech2410 board based on samsung s3c2410. I think you
> can hardly find information about this board. Uptech is a Chinese
> company and the service it provided is very very bad. The only thing
> it provided me useful is the modification patch for u-boot 1.3.2.
> According to that patch, I believe this board is very similar to
> smdk2410, the difference is uptech2410 has no NOR flash and it also
> has a cheaper NIC.
> 
> > It's looks like a pll init issue
> > are you about them?
> I wrote the initialization code of PLL and SDRAM in the procedure
> "reset-init", so if I cannot execute "reset init", my initialization
> code woun't be executed. You can see that code from my previous
> emails. I extracted that code from the example project provided by
> the CD disk of that board. Those example projects are written by
> ADS.
> 
> I think I have to say something more. If I wrote
> "
> init
> halt
> "
> 
> in openocd.cfg, the board can be halted as I said before. But when I
> download u-boot image into my board with wiggler, the "current line"
> feature is unavailable(I also said this in the previous post). But I
> missed one thing in that email: the "disassemble window" told me all
> instructions are UNKNOWN(0xffffffff). I think although wiggler can
> download image to board, the image is still incorrect.
> 
> On 100/5/23 上午 02:53, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >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
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to