Jump to content
IGNORED

TIImageTool on Github


mizapf

Recommended Posts

In my case it is just an Ant project, so you actually don't have to do anything else but run ant. I did run into some trouble when building other people's projects, especially when they are using more complex tools like Maven ... and don't even tell you that you have to install Maven first, so you first need to figure out what build tool it more or less obviously seems to require.

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

Michael, it seems that there is a small bug in the TIMT GPL disassembler. This statement

.

MOVE  12,@>8300,G@>7000

.

generates the byte code

.

25 00 0C 70 00 00

.

but your latest TIMT disassembles to

.

601F: MOVE  >000C BYTES FROM @>8300 TO GRAM@>8370                25 00 0C 70 00 
6024: RTN                                                        00 

.

Not sure what happens, but the GROM address takes two bytes, not just >70 (meaning >8370 for CPU addresses).

Link to comment
Share on other sites

You seem to be right. For the lack of GPL code using GRAM destinations, I never fully checked that part of the disassembler.

You should run the Souce code of RXB GRAM into our GPL Assembler and see if it checks out.

 

I only use the RYTE DATA GPL Assembler myself.

Link to comment
Share on other sites

  • 11 months later...
  • 9 months later...

Hi Michael, when I "view files as text" with TIImageTool, it seems that two periods are displayed for each period in the file. I first noticed this oddity while viewing source COPY directives such as this one:

COPY "HDS1..DU1..EQUATES"
COPY "HDS1..DU1..DSKU-MAIN"
COPY "HDS1..DU1..COMPARE"
COPY "HDS1..DU1..FILE-COMP"
COPY "HDS1..DU1..COPY-BACK"
COPY "HDS1..DU1..COPY-BIT"

 

This effect is not limited to source files. I am reviewing some files on an old XP machine so perhaps this issue is specific to some OS versions?

Link to comment
Share on other sites

  • 2 years later...

Hi mizapf,

 

I am trying to compile tiimagetool from your github source on the latest version of Raspberry Pi OS (formerly Raspbian).  I have RXTXcomm.jar copied into the 'ext' folder and run the 'ant' command from the main tiimagetool folder.  Here's what I see:

 

pi@raspberrypi:~/source/tiimagetool $ ant
Buildfile: /home/pi/source/tiimagetool/build.xml

init:
    [mkdir] Created dir: /home/pi/source/tiimagetool/build

tiimagetool:
     [echo]
     [echo]      ****    Building TIImageTool  ****
     [echo]
    [javac] Compiling 158 source files to /home/pi/source/tiimagetool/build
    [javac] warning: [options] bootstrap class path not set in conjunction with -source 7
    [javac] /home/pi/source/tiimagetool/src/de/mizapf/timt/TIImageTool.java:488: error: cannot find symbol
    [javac]                             gnu.io.DriverManager.getInstance().loadDrivers();
    [javac]                                   ^
    [javac]   symbol:   class DriverManager
    [javac]   location: package gnu.io
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] 1 error
    [javac] 1 warning

BUILD FAILED
/home/pi/source/tiimagetool/build.xml:36: Compile failed; see the compiler error output for details.

Total time: 15 seconds
 

 

The RXTXcomm.jar file I'm using comes from the package 'librxtx-java' (from the Raspberry Pi OS software repository).

Any help you can provide would be appreciated and thank you!

 

Link to comment
Share on other sites

There is a newer RXTX; have a look at github. I'll add some more information later.

 

https://github.com/rxtx/rxtx

 

OK, quite easy, quick job for a short break:

- Get the source code from git

- Install Apache Maven

- Enter the source directory, run mvn clean and mvn package -Pwith-linux-armhf

- Be told by the compiler that you cannot build that on a Raspi itself, need to use e.g. Ubuntu on a x86 / x86_64

- Delete the stuff on your Raspi, redo the above steps on an Ubuntu machine, don't forget to install the cross compiler toolchain

- If everything has been properly built (no red error messages), copy the files rxtx-api.jar and rxtxSerial-2.2-stabilize-SNAPSHOT.jar to your Raspi

- If you don't want the hassle, take the attached tar file and unpack that on your Raspi (curse me for the lengthy description from above). Note that I renamed the two jars in there.

- Add the two jar files to the CLASSPATH for TIMT, e.g. java -classpath rxtx-api.jar:rxtxSerial-2.2-stabilize-SNAPSHOT.jar:tiimagetool.jar de.mizapf.timt.TIImageTool
 

And the advantage to the older RXTX? Well, the older one had some quirks and issues in it, and was more or less abandoned. The newer one has active maintainers (not least because I urged to get a fixed version).

raspi-rxtx.tar.gz

Edited by mizapf
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...