R.Doss schreef: > Hallo, > > I have also a AT91SAM9260 board. > Wich board do you have > I have found out a strange behaviour. > > case 1: > When the flash is empty it works fine. No problem. > > case 2: > When the board is configured to boot u-boot from parallel Flash. I get > also errors and the reset script does not work. > Wich error do you get? Do you have a log? > In the reset script is the configuration for the externel Flash and RAM. > Please include your config-file, including the reset script. > I need this for downloading. > The interesting is I can set the same commandos like in the reset script > over telnet step by step. > > I have just made a reset-init script for my board (Propox MMnet1001). It is not completely finished. I have to write some lines to setup my NAND-flash. That script works fine. I have tried the commands 'reset run', 'reset halt' and 'reset init' and they all work correctly (only the 'reset init' command runs my init script).
Ferdinand Postema > Rene Doss > > > Ferdinand Postema schrieb: > >> Hi Paul, >> >> The software first tells you it found a device with id-code 0xf074203f. Then >> it tries to tell you that an error has occured. The error is split up into 2 >> lines. Firt it less you wat it got and then it tells you what it had >> expected. >> I also have a board with an at91sam9260 chip. This one reports the ID-code >> that the software expects. It is strange that your board does not report >> this id-code. Are you sure you have a at91sam9260? >> Try changing the expected id-code by setting the CPUTAPID variable. You can >> do this with the following configuration file: >> >> ## Set interface >> source [find interface/signalyzer.cfg] >> >> ## Set TCP-port numbers: >> gdb_port 3333 >> telnet_port 4444 >> tcl_port 5555 >> >> ## Chip: >> set CHIPNAME at91sam9260 >> set CPUTAPID 0xf074203f >> set ENDIAN little >> >> source [find board/olimex_sam9_l9260.cfg] >> >> ## end of file >> >> I hope this works. >> >> Ferdinand >> >> >> ================== >> Paul Thomas wrote: >> >> hello, >> >> I'm trying to use openocd on our at91sam9260 board. This board works >> fine and a colleague has been using the j-link with the Segger >> software just fine. The output from starting is below. It looks like >> it's doing something, when I run it without the board connected I get >> "Error: JTAG communication failure". I'm confused by the "JTAG tap" >> line, the first "Info" line one looks OK, but then then almost the >> same line follows but as an error? Any help would be appreciated. You >> all are doing great work with openocd. >> >> thanks, >> Paul >> >> [root at blue >> <https://lists.berlios.de/mailman/listinfo/openocd-development> share]# >> openocd -f interface/signalyzer.cfg -f >> board/olimex_sam9_l9260.cfg >> Open On-Chip Debugger 0.3.0-in-development (2009-08-15-22:18) svn:2579 >> $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ >> For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS >> jtag_nsrst_delay: 200 >> jtag_ntrst_delay: 200 >> Info : JTAG tap: at91sam9260.cpu tap/device found: 0xf074203f (mfg: >> 0x01f, part: 0x0742, ver: 0xf) >> Error: JTAG tap: at91sam9260.cpu got: 0xf074203f (mfg: >> 0x01f, part: 0x0742, ver: 0xf) >> Error: JTAG tap: at91sam9260.cpu expected 1 of 1: 0x0792603f (mfg: >> 0x01f, part: 0x7926, ver: 0x0) >> Error: trying to validate configured JTAG chain anyway... >> Error: unknown EmbeddedICE version (comms ctrl: 0x00300000) >> >> _______________________________________________ >> Openocd-development mailing list >> Openocd-development@lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/openocd-development >> >> >> > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
