On Wed, May 9, 2012 at 2:44 PM, Xiaofan Chen <[email protected]> wrote: > On Wed, May 9, 2012 at 8:24 PM, Andreas Fritiofson > <[email protected]> wrote: >> On Wed, May 9, 2012 at 1:36 PM, Xiaofan Chen <[email protected]> wrote: >>> I just tested with TI/Luminary EK-LM3S1968 and here >>> are the results. >>> >>> There are actually no differences at all. >>> >>> mymacmini:build_mpsse xiaofanc$ cat myconfig_git.sh >>> LDFLAGS="-L/usr/local/lib -lusb-1.0" ../configure >>> --enable-maintainer-mode --prefix=/Users/xiaofanc/bin --enable-jlink >>> --enable-ftdi --enable-ft2232_libftdi --enable-stlink --disable-werror >>> >>> mymacmini:board xiaofanc$ cp ek-lm3s1968.cfg ek-lm3s1968_mpsse.cfg >>> mymacmini:board xiaofanc$ nano ek-lm3s1968.cfg >>> mymacmini:board xiaofanc$ pwd >>> /Users/xiaofanc/bin/share/openocd/scripts/board >>> mymacmini:board xiaofanc$ diff ek-lm3s1968.cfg ek-lm3s1968_mpsse.cfg >>> 13c13 >>> < source [find interface/ftdi/luminary.cfg] >>> --- >>>> source [find interface/luminary.cfg] > > This is the problem. I edited the wrong file. :-( > ek-lm3s1968.cfg is wronly edited for the > mpsse version and ek_lm3s1968_mpsse > is actually for the original version. > > mymacmini:lm3s1968 xiaofanc$ cat > ~/bin/share/openocd/scripts/board/ek-lm3s1968.cfg > # > # TI/Luminary Stellaris LM3S1968 Evaluation Kits > # > # http://www.luminarymicro.com/products/lm3s1968_evaluation_kits.html > > # NOTE: to use J-Link instead of the on-board interface, > # you may also need to reduce adapter_khz to be about 1200. > # source [find interface/jlink.cfg] > > # include the FT2232 interface config for on-board JTAG interface > # NOTE: using the on-board FT2232 JTAG/SWD/SWO interface is optional! > # so is using in JTAG mode, as done here. > source [find interface/ftdi/luminary.cfg] > > # include the target config > set WORKAREASIZE 0x2000 > set CHIPNAME lm3s1968 > source [find target/stellaris.cfg] > > mymacmini:lm3s1968 xiaofanc$ cat > ~/bin/share/openocd/scripts/board/ek-lm3s1968_mpsse.cfg > # > # TI/Luminary Stellaris LM3S1968 Evaluation Kits > # > # http://www.luminarymicro.com/products/lm3s1968_evaluation_kits.html > > # NOTE: to use J-Link instead of the on-board interface, > # you may also need to reduce adapter_khz to be about 1200. > # source [find interface/jlink.cfg] > > # include the FT2232 interface config for on-board JTAG interface > # NOTE: using the on-board FT2232 JTAG/SWD/SWO interface is optional! > # so is using in JTAG mode, as done here. > source [find interface/luminary.cfg] > > # include the target config > set WORKAREASIZE 0x2000 > set CHIPNAME lm3s1968 > source [find target/stellaris.cfg] > >> Impossible. My driver doesn't print that message, >> it's only in ft2232.c. >> >> andreas@naven:~/develop/openocd$ grep -r "read enough bytes" . >> ../src/jtag/drivers/ft2232.c: LOG_ERROR("couldn't read enough >> bytes from " >> >> I'm not sure what's happening, but you're still using the old driver. >> > > You are absolutely right. > > But the mpsse version does not work at all. > > It either hangs or give the errors. >
"Great", that's the type of feedback I need. The config file layouts are a bit of a guesswork from my side, so they may be wrong for luminary. I've tested with jtagkey.cfg, olimex-arm-usb-ocd.cfg and olimex-arm-usb-ocd-h.cfg. Do you have access to any of these or another adapter? Just to determine if the config or the code is to blame. Can you send a -d3 debug log? /Andreas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
