Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#38 Latest version of jtag do not compile

closed
Marcel Telka
jtag (26)
5
2011-07-08
2006-02-21
happycactus
No

The Latest version of jtag do not compile with the
latest version of include.
It compiles with the 0.3.2, because of the extra
detectflash argument introduced with the 0.4 version.
You should at least specify the required version on the
README and/or in the project page.

regards,

Discussion

  • ameziti
    ameziti
    2006-05-25

    Logged In: YES
    user_id=1526569

    You have to update the libbrux *.c files with that are in
    CVS repository
    http://openwince.cvs.sourceforge.net/openwince/libbrux/

    because the since include-0.4 release it updates the header
    files. but the jtag-0.5.1 doesn't contains the libbrux
    directory updated. you can find the last release of libbrux
    in CVS.

    I find the same problem and resolv it and understand it with
    reading that comment on wikipedia:

    "The openwince project produce the JTAG Tools supporting a
    large set of inexpensive IEEE 1284 parallel printer port
    cables (the project has made no releases since 2003 but its
    CVS repository is quite active)"

    http://en.wikipedia.org/wiki/JTAG

     
  • KW
    KW
    2007-02-14

    Logged In: YES
    user_id=639325
    Originator: NO

    I removed the second argument in the prototype of detectflash() in /usr/local/include/openwince/brux/flash.h and jtag now compiles cleanly. Not sure if this impacts its operation yet but I'm off to try that now and will report any issues I come across.

     
  • KW
    KW
    2007-02-15

    Logged In: YES
    user_id=639325
    Originator: NO

    I stepped down to the 3.x version of include since removing the extra arg didn't allow the detect to work so I thought the library was the issue. But alas the detect cmd still doesn't show anything for my strongarm eval board using the 3.x lib either. I am using the xilinx parallel (DLC5) cable and it initializes correctly but the detect returns nothing. Is there a jumper or sequence I'm missing when powering up the board that is preventing the detect from working correctly?

    If this should be a new bug entry please say so. Plus I'll go and check the history to ensure my problem wasn't addressed in another issue.

     
  • KW
    KW
    2007-02-15

    Logged In: YES
    user_id=639325
    Originator: NO

    Found the issue to address my last comment (1028971), sorry for the cross post.

     
  • Marcel Telka
    Marcel Telka
    2011-07-08

    The openwince project is no longer active.

    If this report is related to JTAG Tools, please try UrJTAG at http://urjtag.sourceforge.net/

     
  • Marcel Telka
    Marcel Telka
    2011-07-08

    • status: open --> closed