PDA

View Full Version : Sony B55...Is it NoZKT'd yet ??


PC_works
04-23-2004, 12:55 AM
I was wondering if it has been done?

Do you flash it inline with a Jtag (where do you connect it up to)

Any insight would be appreciated.....Thnanx

nagolcj
04-23-2004, 04:14 PM
yes, it has be nozkted with a JTAG.

there's a thread over at id-discussions dealing with this

PC_works
04-23-2004, 05:07 PM
nagolcj...the only thing I found is this thread

http://www.dssftp.com/forum/upload/showthread.php?t=13291

and it seems to be a works in progress. The jtag hook up seems to be for a B65. Are they the same inside as to hook ups. I'll have to go to my friends house to open one up and see.

Do we know where to patch it. If anyone has this please let me know..Thanx as always.

nagolcj
04-23-2004, 05:45 PM
this is not for the faint at heart, you need a Linux box etc.

I did this about a month ago on my B55 & it has been working like a charm.

http://id-discussions.com/forum/showthread.php?t=53464

PC_works
04-23-2004, 06:47 PM
this is not for the faint at heart, you need a Linux box etc.

I did this about a month ago on my B55 & it has been working like a charm.

http://id-discussions.com/forum/showthread.php?t=53464


I am flipping through the Forum slow page to page changing. Do you have the short and sweet version .

nagolcj
04-23-2004, 07:43 PM
I am flipping through the Forum slow page to page changing. Do you have the short and sweet version .

nope, no such beast exists. you'll have to read thru the whole mess & figure it out for yourself.

PC_works
04-23-2004, 08:31 PM
I read through that post and it is far above my knowledge. I am not scared to solder but changing things in the software to get it to work is another story.


I gathered that you have to run in Linux and not use the Cygwin (doesn't work)

I am still unclear as to the pin layout for the Jtag.

Did you use a buffered jtag?

I downloaded the file from Fluxman sony B55 v2, is that what you used?

I also downloaded the Jtagger prog for B55.

Please help as I am not knowledgeable as that group. Thanx for any help..

nagolcj
04-24-2004, 03:27 AM
I read through that post and it is far above my knowledge. I am not scared to solder but changing things in the software to get it to work is another story.


I gathered that you have to run in Linux and not use the Cygwin (doesn't work)

I am still unclear as to the pin layout for the Jtag.

Did you use a buffered jtag?

I downloaded the file from Fluxman sony B55 v2, is that what you used?

I also downloaded the Jtagger prog for B55.

Please help as I am not knowledgeable as that group. Thanx for any help..

1. jtagger would not work for me when I tried it with Cygwin. It may work okay for you, but you'd be the first to my knowledge.

2. it's there in a post by flash411.

3. yes -- an unwink one

4. no, I used the original nozkt file. seems to me fluxman released v.2 to enable access to the low speed data port to resolve some issues with his a55. for my b55 the first file works perfectly.

keep reading & re-reading that thread...all the info you need is there

PC_works
04-25-2004, 05:02 AM
nagolcj,

Why do you need to use Linux with Jtagger.

Doesn't Jkeys work in Windows with the B55.

also a favor, can you upload that first b55 NoZKT file....Thanx

nagolcj
04-25-2004, 03:46 PM
I couldn't get jtagger to compile with cygwin, that's why I went the linux route. if you read that thread closely you'll also know that I couldn't get it to compile using mandrake either... red hat 9.0 worked for me.

to my knowledge jkeys has not been updated to work with the b55.

IMO until a p4/p5 hack is available there really isn't much use in persuing this.

PC_works
04-26-2004, 05:31 PM
nagolcj

I am not as talented as the ppl in that thread and would greatly appreciate a little help.
Someday this would be worthwhile, maybe not today but I just thought it would be a good idea anyways....some free time.

I could not find the original b55 NoZKt file just version 2.

This is my understanding after reading and re-reading, am I on the right track?


TMS - Test Point 173
TDI - Test Point 165
TDO - Test Point 167
TCK - pin 33 (CLK40)
nTRST - pin 13(nISPEN)

All that is required is a JTAG interace, and to connect
the two pads ( TP180 and TP181 ) on the top-right of IC160 to enable
the WE line to the flash.

software required:
------------------
JTagger 0.1.0
Red Hat Linux v9.0

address=0x2c000000 --length=0x80000
-------------------------------------------------------------------------------------------

Is there a way to write protect the eeprom as in the RCA 420 cutting a trace?

The only thing I am not sure of is when you connect the two pads TP180 and TP181, does the led light up when flashing.

nagolcj
04-26-2004, 07:51 PM
I am not as talented as the ppl in that thread and would greatly appreciate a little help.


no problem helping when I have time


I could not find the original b55 NoZKt file just version 2.


so go with version 2 then. if I wasn't so lazy I'd update mine.


This is my understanding after reading and re-reading, am I on the right track?


check out the pictures, they're worth a thousand words. Notice on the TP180-TP181 instead of removing the jumper wire I cut it instead. Toldja I'm lazy.


All that is required is a JTAG interace, and to connect
the two pads ( TP180 and TP181 ) on the top-right of IC160 to enable
the WE line to the flash.


yep


software required:
------------------
JTagger 0.1.0
Red Hat Linux v9.0

address=0x2c000000 --length=0x80000


yes, BUT don't forget you have to modify JTagger as per flash411's instructions to allow your DSS/DVB JTAG to work with the program. Not to mention adding the definition for your flash as well. and before you ask, my modded JTagger source is on a hard drive that isn't installed in a computer at the moment. You'll have to do this yourself.

don't erase the entire flash, do only the sectors that change. flashing is an extremely slow process -- about 10 minutes per sector. There are 32 sectors...do the math. I believe it was reported that it took around 16 hrs to complete!


-------------------------------------------------------------------------------------------

Is there a way to write protect the eeprom as in the RCA 420 cutting a trace?

The only thing I am not sure of is when you connect the two pads TP180 and TP181, does the led light up when flashing.

I didn't worry about the eeprom protection. I think the led lights up, can't remember off-hand.

PC_works
04-26-2004, 08:21 PM
nagolcj

Thanks for the help and the pics. definitely helped me out. I maybe a little over my head. I am a simple person and I'll have to read that section over again.

You also noted in the posts something about a "marlin". What was that about?

After this is all done and said I'm going to make a "how to" document on this.

Thanks tons for all your time, patience and help.

nagolcj
04-26-2004, 08:45 PM
nagolcj
You also noted in the posts something about a "marlin". What was that about?

means I found a platinum subbed CAMID to use

PC_works
04-26-2004, 09:34 PM
nagolcj

things are starting to make more sense.

You mentioned that to only write sectors instead of the whole thing (makes sense) but the b55 v2 is one 2mb file.

Don't erase the entire flash, do only the sectors that change.

I compared the factory to the original and got 12 differences. How do I write just the differences? Doesn't the checksum get thrown off...or it doesn't it matter (like the Phillips)

------------------------------------------------------------------------------------------------
this is the post you were referring to by Flash411. This is all done with the Jtagger hooked up, WE connected. is this right?

Fllash411:
Here are the changes I made to the jtager-0.1.0 src from sourceforge.net.
You should then be able to type ./configure and then make and then run src/jtager.
Typing idcode at the JTAGER:> prompt should return
Reading the JTAG Device ID code ... [OK]
Device ID = 0x1100E02F
bit[0] = 1, always be 1, required by IEEE Std 1149.1
Manufacturer (bit[11:1]): unknown
Part number (bit[27:12]): 0x100E
Version (bit[31:28]) : 0x1

Typing mem --read -start-address=0x2c000000 --length=0x80000 --output=flash.bin

should get a dump of your flash in little-endian format. The AV7100 is Big-Endian though.
-------------------------
Code:
DSS
JTag B55
TMS 14
nTRST 1
TDI 13
+5V 12
TDO 11
TCK 9
GND 6
-------------------------
# diff jtag.c jtag.c.orig
49c49
< static unsigned char dataport_value = JTAG_TRST_MASK; /* JTAG_TRST_MASK */
---
> static unsigned char dataport_value = 0; /* JTAG_TRST_MASK */
105,106d104
< return 1;
< else
107a106,107
> else
> return 1;
177c177
< value = JTAG_TRST_MASK; /* JTAG_TRST_MASK; */
---
> value = 0; /* JTAG_TRST_MASK; */
427c427
< outb(0, par_dataport); /* LOW */
---
> outb(JTAG_TRST_MASK, par_dataport); /* LOW */
429c429
< outb(JTAG_TRST_MASK, par_dataport); /* HIGH */
---
> outb(0, par_dataport); /* HIGH */

# diff jtag.h jtag.h.orig
87,90c87,90
< #define JTAG_TMS_MASK 0x01
< #define JTAG_TCK_MASK 0x02
< #define JTAG_TDI_MASK 0x04
< #define JTAG_TRST_MASK 0x08 /* optional TAP reset signal */
---
> #define JTAG_TMS_MASK 0x02
> #define JTAG_TCK_MASK 0x04
> #define JTAG_TDI_MASK 0x08
> #define JTAG_TRST_MASK 0x01 /* optional TAP reset signal */
92c92
< #define JTAG_TDO_MASK 0x10
---
> #define JTAG_TDO_MASK 0x80 /* remember this signal is inverted */

================================================== ======

nagolcj
04-26-2004, 10:18 PM
you're very much on the right track :)

You notice on your report something like this :

Offsets: hexadec.

7467E: 00 C0
7467F: F0 46
74680: 19 C0
74681: F8 46
B8C7E: 0F C0
B8C7F: D1 46
C108A: 80 C0
C108B: E0 46
1FFFFC: 45 52
1FFFFD: A3 68
1FFFFE: 72 38
1FFFFF: B6 24

This report tells me there are 4 sectors that need to be reflashed (look at the offsets) :

SA14 0x07000-07FFFF
SA18 0x08000-08FFFF
SA19 0x0C000-0CFFFF
SA38 0x1F0000-1FFFFF

The above assumes you've got an ATMEL AT49LV1614 flash.

For your convenience I've attached the 4 files you need to flash your IRD.

are we having fun yet?

PC_works
04-26-2004, 11:18 PM
THANK YOU nogolcj!!!!!!

this makes my life easier.

Another little Question do I C & P that source code from flash411 (on my previous post) to the "Tools" C file 5kb in the "jtager-0.1.0flux1\src" folder?

I can not get Cygwin to work either, getting error message

"jtager.exe - Unable To Locate Component "
"This application has failed top start because cygwin1.dll was not found. Re-installing the application may fix this problem."

I am going to try re-installing because I don't hasve red hat. I'm working on it. Or I'll have to see who has Linux setup round here.

I attached a txt from fluxman I think that answers my question about settings by flash411. Please confirm...

Once again, Thank You so much for your help nagolcj....you are patient. Great example of what a community is all about. This stuff is too far beyond me.

PC_works
04-27-2004, 12:45 AM
I got jtager to start up with cygwin without errors.
I'll test it out and let you know if it works.

Thanks again nagolcj

PC_works
04-28-2004, 09:04 PM
Cygwin did not work for me... I Installed ioperm and activated it in cygwin . soldered the jtag to the pins @Cn130, jumper wire to TP180 &181, typed in IDcode and got "failed". Going to install Red hat. and try again. Let ya know. PC

PC_works
04-28-2004, 09:33 PM
nagolcj

this is the commands for jtager

*** BASIC COMMANDS GROUP:
help.........................Show all JTAGER commands list, or verbose help info
reset........................Reset the jtag TAP controller
idcode......................Read the jatg IDCODE of your target
exit..........................Exit or quit -- Exit JTAGER program
quit..........................Exit or quit -- Exit JTAGER program

*** DEBUG COMMANDS GROUP:
halt .........................Halt the target, and makee it into the debug state
restart.....................Restart the halted target from the last halted point
ice........................... Read/write the registers of EmbeddedICE-RT logic
reg...........................Read/write the core registers of the target in the debug state
mem.........................Read/write the memory units of the target
flash.........................Read/write the flash chip on the target

JTAGER:>

---------------------------------------------------------------------------------------------------
you mentioned writing only sectors
"From what I can see there's 2 ways to read the flash with JTAGER :

> mem --read start-address=0x2c000000 --length=0x80000 --output=/path/to/file

That should dump the entire flash.

> flash --read start-address=0x000000 --length=0x80000 --output=path/to/file

This should do the same as above, but it doesn't work for me.

and also I used Fluxman's original B-55 nozkt file as a base and only wrote sectors 070000-

07FFFF and 1F0000-1FFFFF"


Which command do you use (mem)? How did you type that in the JTAGER:> prompt

You cut up the file into 4 sectors but how do you write it in Jtager to do each flash. This is all new to me. Thanks PC

nagolcj
04-29-2004, 06:18 AM
Somehow the file split in my previous message got messed up. Use the files I've attached to this one. Sorry about that.


If you followed the install instructions in Chapter 2 of the JTAGER manual, it would be installed in /usr/local/bin/jtager.

Open up a terminal window as root and enter the following to start JTAGER (the # sign is sort of like the C: prompt in a DOS window) :

#cd /usr/local/jtager/bin
#./jtager

Once JTAGER starts, here's the command sequence (as I remember it anyway -- my memory is suspect at the best of times so don't get pissed at me if I forgot something) :

JTAGER:> idcode
JTAGER:> halt
JTAGER:>mem --read start-address=0x2C000000 --length=0x80000 --output=/path/to/backup_file
JTAGER:> flash --detect at49lv1614a
JTAGER:> flash --info
JTAGER:> flash --erase-sector 0x070000
JTAGER:> flash --write --start-address=0x070000 --input=/path/to/sa14.bin
JTAGER:> flash --erase-sector 0x080000
JTAGER:> flash --write --start-address=0x080000 --input=/path/to/sa15.bin
JTAGER:> flash --erase-sector 0x0C0000
JTAGER:> flash --write --start-address=0x0C0000 --input=/path/to/sa19.bin
JTAGER:> flash --erase-sector 0x1F0000
JTAGER:> flash --write --start-address=0x1F0000 --input=/path/to/sa38.bin
JTAGER:> exit

Don't forget it takes about 10 minutes for each of the flash --write commands to complete. The idcode and flash info steps are just to reassure you it's working. Oh, and one last thing...if you're using a battery powered JTAG make sure they're fresh batteries. Hate to get half way through the flashing procedure and have it die on you.

good luck!

PC_works
04-29-2004, 08:38 PM
Nagolcj

Okay I placed the jtager folder in /usr/local/bin/jtager

I logged on as root, opened a terminal window main menu -> system tools -> terminal

terminal window pops up and entered # cd /usr/local/bin/jtager/src

I typed in "ls" to display contents in the folder and it shows jtager.exe

[root@localhost src]# cd /usr/local/bin/jtager/src
[root@localhost src]# ls
cmd------- jtager.exe------Makefile-------------sa14.bin---------sa38.bin---------ttools.o
flash------main.c-----------Makefile.am--------sa15.bin----------target
jtag -------main.o----------Makefile.in----------sa19.bin----------tools.c

(I put in the '-------' to space these out or it condenses when you post )

So I typed in at the # ./jtager and got the following

[root@localhost src]# ./jtager
bash: ./jtager: No such file or directory

I tried for the hell of it with the .exe on the end:
[root@localhost src]# ./jtager.exe
bash: ./jtager.exe: cannot execute binary file

augggggg!!!!!!!!!!!!! What am I doing wrong?

thanks for all your help as always it is very appreciated........PC

nagolcj
04-29-2004, 10:23 PM
Okay I placed the jtager folder in /usr/local/bin/jtager

how exactly did you compile it?

I followed the instructions in Chapter 2 of the JTAGER User Manual to the letter & it worked perfectly :

First, download the JTAGER package and place it in some directory, such as the /tmp directory. Follow the following steps to unpack it.


#cd /tmp
#tar zxvf jtager-0.1.0.tar.gz
#cd jtager-0.1.0

Then, run configure script and compile:

#configure --prefix=/usr/local/jtager
#make all

Finally, run make install to install JTAGER to your specified path (the default path is /usr/local):

#make install

To run JTAGER, type ./jtager and press <ENTER>:

#cd /usr/local/jtager/bin
#./jtager

PC_works
04-30-2004, 01:14 AM
Nagolcj

Do you have a copy of the manual? I never came across any manual.

I tried to compile the file and the terminal window shuts down after this. It goes really fast and displays about eight line and shuts down to main desktop. I updated Red hat with every update and rebooted. same thing. any ideas. I have a friend who I sent the file to and he was able to compile the program. he walked me through over the phone what he did and it still crashed. the original folder had 18 files after it crashed I have 19 (config.log...is new)

When I say it crashed it just goes directly to the desktop and shuts down the terminal.

I am not having any fun!!!! PC

nagolcj
04-30-2004, 01:27 AM
Manual should be in a folder called /docs. Online version is at http://jtager.sourceforge.net/doc/jtager.html

Have you looked at the config.log file to see what it says?

hey, this is fun. know what really sucks...being a Montreal Canadiens fan these days (all you make-believes fans find another thread to pollute -- I still say Flyers in 6)

PC_works
04-30-2004, 05:28 PM
Nagolcj

This is what I did I downloaded a new jtager from : http://umn.dl.sourceforge.net/sourceforge/jtager/jtager-0.1.0.tar.gz

Then I did the follwing:
[root@localhost root]# cd /tmp
[root@localhost tmp]# tar zxvf jtager-0.1.0.tar.gz
jtager-0.1.0/
jtager-0.1.0/README
jtager-0.1.0/AUTHORS
jtager-0.1.0/COPYING
jtager-0.1.0/ChangeLog
jtager-0.1.0/INSTALL
jtager-0.1.0/Makefile.am
jtager-0.1.0/Makefile.in
jtager-0.1.0/NEWS
jtager-0.1.0/TODO
jtager-0.1.0/aclocal.m4
jtager-0.1.0/configure
jtager-0.1.0/configure.ac
jtager-0.1.0/CREDITS
jtager-0.1.0/MAINTAINERS
jtager-0.1.0/tools/
jtager-0.1.0/tools/Makefile.am
jtager-0.1.0/tools/Makefile.in
jtager-0.1.0/tools/config.guess
jtager-0.1.0/tools/config.rpath
jtager-0.1.0/tools/config.sub
jtager-0.1.0/tools/depcomp
jtager-0.1.0/tools/install-sh
jtager-0.1.0/tools/missing
jtager-0.1.0/tools/mkinstalldirs
jtager-0.1.0/tools/rebuild
jtager-0.1.0/tools/rebuild-gcc
jtager-0.1.0/tools/readme
jtager-0.1.0/doc/
jtager-0.1.0/doc/Makefile.am
jtager-0.1.0/doc/Makefile.in
jtager-0.1.0/doc/jtager.html
jtager-0.1.0/doc/jtager-cn.html
jtager-0.1.0/doc/jtager-internals.html
jtager-0.1.0/doc/jtager-internals-cn.html
jtager-0.1.0/doc/circuit.txt
jtager-0.1.0/doc/s3c44b0x.bsdl
jtager-0.1.0/doc/sa1100.bsdl
jtager-0.1.0/include/
jtager-0.1.0/include/jtager.h
jtager-0.1.0/include/types.h
jtager-0.1.0/include/jtag.h
jtager-0.1.0/include/arm7tdmi.h
jtager-0.1.0/include/arm9tdmi.h
jtager-0.1.0/include/target.h
jtager-0.1.0/include/flash.h
jtager-0.1.0/include/Makefile.am
jtager-0.1.0/include/Makefile.in
jtager-0.1.0/include/config.h.in
jtager-0.1.0/src/
jtager-0.1.0/src/Makefile.am
jtager-0.1.0/src/Makefile.in
jtager-0.1.0/src/main.c
jtager-0.1.0/src/tools.c
jtager-0.1.0/src/jtag/
jtager-0.1.0/src/jtag/Makefile.am
jtager-0.1.0/src/jtag/Makefile.in
jtager-0.1.0/src/jtag/jtag.c
jtager-0.1.0/src/target/
jtager-0.1.0/src/target/Makefile.am
jtager-0.1.0/src/target/Makefile.in
jtager-0.1.0/src/target/target.c
jtager-0.1.0/src/target/arm7tdmi/
jtager-0.1.0/src/target/arm7tdmi/Makefile.am
jtager-0.1.0/src/target/arm7tdmi/Makefile.in
jtager-0.1.0/src/target/arm7tdmi/arm7tdmi.c
jtager-0.1.0/src/target/arm7tdmi/register.c
jtager-0.1.0/src/target/arm7tdmi/memory.c
jtager-0.1.0/src/target/arm7tdmi/ice.c
jtager-0.1.0/src/target/arm9tdmi/
jtager-0.1.0/src/target/arm9tdmi/Makefile.am
jtager-0.1.0/src/target/arm9tdmi/Makefile.in
jtager-0.1.0/src/target/arm9tdmi/arm9tdmi.c
jtager-0.1.0/src/target/arm9tdmi/register.c
jtager-0.1.0/src/target/arm9tdmi/memory.c
jtager-0.1.0/src/target/arm9tdmi/ice.c
jtager-0.1.0/src/flash/
jtager-0.1.0/src/flash/Makefile.am
jtager-0.1.0/src/flash/Makefile.in
jtager-0.1.0/src/flash/flash.c
jtager-0.1.0/src/flash/sst39vf160.c
jtager-0.1.0/src/flash/sst39vf040.c
jtager-0.1.0/src/flash/sst28sf040.c
jtager-0.1.0/src/flash/am29f040.c
jtager-0.1.0/src/cmd/
jtager-0.1.0/src/cmd/Makefile.am
jtager-0.1.0/src/cmd/Makefile.in
jtager-0.1.0/src/cmd/command.c
jtager-0.1.0/src/cmd/basic.c
jtager-0.1.0/src/cmd/help.c
jtager-0.1.0/src/cmd/idcode.c
jtager-0.1.0/src/cmd/debug.c
jtager-0.1.0/src/cmd/reg.c
jtager-0.1.0/src/cmd/ice.c
jtager-0.1.0/src/cmd/mem.c
jtager-0.1.0/src/cmd/flash.c
[root@localhost tmp]# cd jtager-0.1.0
[root@localhost jtager-0.1.0]#

Then now to try to configure:
[root@localhost jtager-0.1.0]# configure --prefix=/usr/local/jtager
bash: configure: command not found

What did I do wrong?

My friend suggested that I move that file to /usr/local/jtager directly to compile and type
". configure"
This is what I got:
[root@localhost jtager-0.1.0]# cd /usr/local/jtager-0.1.0
[root@localhost jtager-0.1.0]# . configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
rm: remove regular file `conftest.sed'?

I answered "yes" and this is where it goes really fast and 8 - 10 lines of stuff flash by then the terminal closes

Any ideas of what I am doing wrong??

Here is the Config.log readout:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by JTAGER bash 0.1.0, which was
generated by GNU Autoconf 2.57. Invocation command line was

$ bash

## --------- ##
## Platform. ##
## --------- ##

hostname = localhost.localdomain
uname -m = i686
uname -r = 2.4.20-31.9
uname -s = Linux
uname -v = #1 Tue Apr 13 18:04:23 EDT 2004

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/X11R6/bin
PATH: /root/bin


## ----------- ##
## Core tests. ##
## ----------- ##

bash:1332: checking for a BSD-compatible install
bash:1386: result: /usr/bin/install -c
bash:1397: checking whether build environment is sane
bash:1440: result: yes
bash:1473: checking for gawk
bash:1489: found /bin/gawk
bash:1499: result: gawk
bash:1509: checking whether make sets $(MAKE)
bash:1529: result: yes
bash:1676: checking whether to enable maintainer-specific portions of Makefiles
bash:1685: result: no
bash:1708: checking build system type
bash:1717: error: cannot guess build type; you must specify one

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build_alias=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run aclocal-1.6'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run tar'
AUTOCONF='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run autoconf'
AUTOHEADER='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run autoheader'
AUTOMAKE='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run automake-1.6'
AWK='gawk'
CC=''
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
DEFS=''
DEPDIR=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LDFLAGS=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='${SHELL} /usr/local/jtager-0.1.0/tools/missing --run makeinfo'
OBJEXT=''
PACKAGE='jtager'
PACKAGE_BUGREPORT='zhanrk@163.com'
PACKAGE_NAME='JTAGER'
PACKAGE_STRING='JTAGER 0.1.0'
PACKAGE_TARNAME='jtager'
PACKAGE_VERSION='0.1.0'
PATH_SEPARATOR=':'
RANLIB=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='0.1.0'
ac_ct_CC=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__include=''
am__quote=''
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/usr/local/jtager-0.1.0/tools/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE "jtager"
#define PACKAGE_BUGREPORT "zhanrk@163.com"
#define PACKAGE_NAME "JTAGER"
#define PACKAGE_STRING "JTAGER 0.1.0"
#define PACKAGE_TARNAME "jtager"
#define PACKAGE_VERSION "0.1.0"
#define VERSION "0.1.0"

bash: exit 1
---------------------------------------------------------------------------------------

nagolcj
04-30-2004, 10:04 PM
you have to enter ./configure, not just configure

PC_works
04-30-2004, 11:23 PM
This is what I got... it didn't close the terminal window..wow hoo!!! BUT,

[root@localhost jtager-0.1.0]# ./configure --prefix=/usr/local/jtager-0.1.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... configure: error: cannot guess build type; you must specify one
[root@localhost jtager-0.1.0]# make all
make: *** No rule to make target `all'. Stop.
[root@localhost jtager-0.1.0]#

-----------------------------------------------------------------------
I get some sort of error about system build type? any ideas? thanks again for all the help. PC

nagolcj
05-01-2004, 06:40 PM
This is what I did I downloaded a new jtager from : http://umn.dl.sourceforge.net/sourc...er-0.1.0.tar.gz

why? that version will NOT work with the B55 unless you modify it. use fluxman's instead.

My friend suggested that I move that file to /usr/local/jtager directly to compile and type ". configure"
unless your friend is experienced in installing packages in Linux, I suggest you send him to the beer store while you're doing this ;)

Here's the command sequence :

#cd /tmp
#tar zxvf jtager-0.1.0.tar.gz
#cd jtager-0.1.0
#./configure --prefix=/usr/local/jtager
#make all
#make install
#cd /usr/local/jtager/bin
#./jtager

PC_works
05-01-2004, 10:30 PM
nagolcj

I tried the fluxmans one. I must be missing something . I will upload it for you. i change the file name when i typed in the commands to reflect the file name. No go.......aaaaaaaaaaaaaauuuuuughhhhh!

nagolcj could you please let me know if it is me or this file. thanks for all your help as always. PC

PC_works
05-12-2004, 08:45 PM
nagolcj

Took a bit of a break. Trying again. I would like to try Fluxmans file in cygwin (at least it starts jtagger. I used the above file with Cygwin "ioperm -i" installed and active.
The paralell port in jtagger shows 0x3bc and 0x3bd. I'm on 0x378. what do i need to do change this to the right port. (i'm not that techincal)

Win xp
Start->control panel-> system-> hardware tab-> device manager-> resources

after that i'm lost on how to change it in there.

or could i just change it in the jtagger program to 0x378?