golden tee golf

[ed12]

this was requested from me
by rfr341
i think anyone that has a golden tee golf might be interested ?
if not so be it if so carry
this is work in motion

ed

[ed12]

ok this part get's me every time
ppl saying i bought this from so and so or off of fleabay
welp here u go
there is 2 of them
egale2.09 and egale
if u can burn your own eprom's ? do yourself a favour and double chk the hexcsums
it must match
side note here
both rom's are the same >egale 2.09< final itsgamming build's
and are public
there is nothing hidden here expect the rip off dealer's

ed

[ed12]

thk-u @ for re-pointing me onto a file i did forget to up-load.

name PONYPROG
file ussage
enable a person to lift 2 pin's on any 93-xx chip or other eeprom
and onboard real time read/re-program the same said chip
it is done through a real serial port,i have never tried it on a usb to serial so i do not know 

the way is simple
ground/sco/sc1

the file has it's own setup file in it
just .exe. it and go
as ALWAY'S SCAN FOR TROUBLE

i will get the hook-up's and add them as a edit when i get a chance

ed

[dssrocks]

Hi Ed, See the attached picture on a board that was working. It gets to this point and then restarts over and over. One thing, not sure if it is normal or not but when first powered up after detecting IDE hard drive it says 2 as you can see in the picture. Then it changes to 1 when it starts is restart loop. THe hard drive, boot rom and power supply work on another GT 2005 green board so I can eliminate these things as problems.

[ed12]

ok what i need to know first is the bootrom ? 2.09? or older ?

as that is what it look's like looping..
as i tried to explain, it for some reason is not writting and or getting it's .bak file

ed

[dssrocks]

It is an older boot rom but it works on another board. I do not have 2.09.

[ed12]

well the reason was multi folded for 2.09
not olny to open the board up to larger harddrive size's
but is also dose away with the chk-sum failure u are getting,because 2.09 inqoure's it..
can u program a eprom ?
if not find some one who can and use my 2.09 on a 27c080 eprom
and it may fix the problem

ed

[ed12]

i just need to know before i finish this piece up if i am missing anything in this ? expect for the tech of it?

>>
add on for golden tee

this part deals with the "spi" interface and what it is for.

first what dose "spi" stand for
serial program interface

usage >board interface <
to read/write code into the serial inteface loop of the >dut< >device under test<

location on the :green golden tee board:
j54
there is olny the j54 lable on the board and if u are lucky
a listing like gnd/tdo/tdi/tms/tclk/vcc
these are very handy,as will be explained,this long and get's deep so if u want to know read more
if not colse out this add on


what these pin's stand for

gnd = ground
tdo = to data out >device under test output<
tdi = to data input >device under test input<
tms = to device !memory sync! handy if u want to see what the memory is doing
tck = timming system clock
vcc = vcc

tdo can also be refered to as timed data out >board out< >dut< >device under test<
tdi can also be refered to as timed data in  >board input< >dut< >device under test<
tms can also be refered to as timed memory sync

that is the basic of the "port:-:j54:"
<<

ed

[ed12]

ok here is some more i found today digging
slute to mame and sub forums (r.belmont)
in here if u care to read far enough in
u will find the lib. inculdes u need to run emu on the chip sets

enjoy

ed

[ed12]

just a scant up-date
nec-vr-4310 main cpu (64 bit) true
nec- vrc-4373 main board controler  (64 bit) true

units ARE (jtag-able)

vr4310 (ports)
52 = jtms
57 = jtck
63 = jtdi
65 = jtdo

the manuals for these chip's are hard to get
but once i am done i will up-link there locations (http's)..

j-tag/t-tag raw c+ code
thk-u clause

this piece must be added and under stood
before entering into jtag mode

Testing
The controller may be configured at power-on reset to force all signals into a high impedance
state to facilitate board-level, in-circuit testing. To do this, drive the
MuxAd[7] signal high during reset.

that is what u do with the vrc 4373



ed

[ed12]

ok vr4310
if u open it
u will see the j-ports
the neat thing i do not understand is
they do not have a tie in to pin 65
olny a solder land
and please before u say it must be under it
look at the .img i am going to up-load

ed

[ed12]

here is what the board looks like with the vr4310 out
the black ticks u can see are felt pen on the jtag ports
it clearly shows pin65 not used ?

ed

[ed12]

well after more digging

B.3.7 JTAG
The VR4300 conforms to IEEE149.1-1990. Consequently, the JTDO signal
becomes active in the shift IR and shift DR modes.
Because the VR4400 conforms to the previous version of the IEEE149.1, the
JTDO signal is not driven.

so even though they state they use it
this apex refers to the point they do not.?


ed

[ed12]

well this is interesting
a google chk for jtaging this beast turned this up
it is from the n64 fourms

>
I think that this project is spectacular. So much so that I just had to register to post this comment.

I know what's wrong - why it doesn't work.

As is the case with many embedded CPUs, a small operating system is required to get the chip to do anything useful. In the case of the Nintendo 64, the operating system checks to see if a cartridge is connected and, if one is, starts loading the game by coping the program's data into RAM and jumping to the code for execution.

I'm almost 100% confident that N64s ship with stock NEC VR4300-100s (with a Nintendo branded logo on), as you have suspected, but you're going to have to rip the firmware out of the old chip and flash it to the new one.

If you look at the datasheet you've provided, you can see that the chip has a JTAG bus (JTDI, JTDO, JTCK, etc.) This is exceedingly convenient and will make this process easy. If you've had experience ripping firmware from CPUs before, you are at a major advantage. If not, no sweat. It's not that difficult, you just need the right tools. If you're interested in carrying this further, get yourself some JTAGing software, a JTAG programmer, connect the pins on the programmer to the respective pins on the CPU, and see if you get anything out of the chip. If not, there may be some enable line hiding somewhere that you may have to tie to 5v. You're going to have to use an unmodified N64 for this, as there's no way you're going to get the chip you removed powered up properly (or at least you shouldn't waste your time trying to get it to.) Make sure that when you're JTAGing you don't have any expansion pack inserted in the N64.
<
what it is saying is there is as i thought frimware inbeded in the chip..hence ser# chk and -f frimware

ed

[ed12]

ok just off topic but pretains to the egale s/w
red board
gt-golf (complete)
buck hunter/bh2/bhse
once u have sorted out the "u53" number u are to have by the serial  number of the board
in my case
00059348-b  (-b makes it a buck hunter) rev 2
the u53 u need in this case is bbh2-can-u
no other u53 firmware revision will work..
once u have done the same board level tests i explained in the green boards (red and green are basicly the same)
u will need to put e1- rs232/e2-card-1 back in,along with the proper u53 and egale boot rom 2.09.and u26 'red-1'and hard drive/video-card.
the board should fire up.
now with out u-50 (time keeper/high stats etc the board should load up to the .img i will post
with it in the board should load and go to game mode

ed

[ed12]

now with u50 back in u will get this .img
and u will beable to make a note :game-load-dose-not-stall: as in my last .img i u-loaded

ed

[ed12]

now another side note i will add about u53
this is important....
if u are using a :test-u53:
and u get !dial-ing-out-to-tele-net!
u are going to end up with -f firmware #c040602
this is cross plate-fourm (reg-green-board),
your fix is proper u53 and cross your fingers
and or a new fresh flash to the vr4310 cpu (yes it has some on-board-flash)..

i have seen u53 fix olny 1 of the dialing out problems to date,but it did end up with the ^^ serial key and -f firmware

ed

[ed12]

ok with all this in hand we can now deduce a few facts
u53 is software depented
ie: u53-bb2-can-u=big buck hunter 2
ie: u53-bb-can-u=big buck hunter
the same applys to usa just sub in usa instead of can
the same info will follow down thread to golden tee golf
ie can44-u
ie:gt-golf-can-u
etc
etc
now to find big buck .img ?
found

ed

[ed12]

here is a few more timbits
green board (buck-hunter)
make note of !u510!
*on buck hunter it will say e2 gun1*
on golden tee it will just say e2r1
if u get a green board for repair?
*look at this chip first*
as u CAN NOT USE IT FOR GOLDEN TEE GOLF AND REVERSE
also note !u26! green board will list as sb04 or sb05
04 is golf
05 is buck hunter

ed

[ed12]

well after a week of going through various hard drives and various images for golden tee complete.
i just about have it hex wise nailed down..
what i upload will be !diskeditor! screen shots..
and edits pointing to landing zones of interest for us.
if u are working on this also and wondering where i am going i suggest
u get a copy of it.
now the reason this is important, it is a work around for
a= -F software
b= boot cycleing >yes it is the hard drive<
please note test !b! was done on a complete green and red board set with all chips in.
c=board will boot to game load then report !wrong s/w for hardware!
or boot back to the game load page
ie chking harddrive 0-1-2
these are caused by the hard drive,and as the .chd's WILL NOT fix this problem,i needed to look at the
offender >hard drive<
and the olny offer i recieved for a work around from it-gamming was to copy a fied complete hard drive
which i already had.and in the process of editing now

ed

[lilshawn]

man, you crazy!

 

[ed12]

well time for some more up-dates
the great news for red/green board owners
is u can now but the u53 right out of its-gamming (take a bow ed)..
it is exchange,29.99 usd..
also if u follow along on there web site ? u will find they offer the complete hardrive and u15 boot rom (150.00) usd
that price is out to lunch..but what do i know.

now on to some tech for them of u playing along
this is a little piece of a up-comming pdf i am writting
but should help u along if know what to do ?

u510
take a significant role in designing
and the implementation for the role of what the board will be.
ie: golden tee/silver strike/buck hunter.

chip > u510 <
one could go as far as to say this is the board "personailty" chip
as i talked about before e2/gun1.
if the chip reads gun1 IT IS NOT A GOLDEN TEE GOLF BOARD,and will not work as such,unless u follow along here and are perpared..


now we go deeper
the chip U510
even though it is a xc9572xl,and is a cpld  programmable logic device,
it dose have on board "flash",this is very handy,as it leads out to it's own port,>j54< on green boards (any gen),for (RED BOARDS) this dose not apply.

next u61
contains the !!!on-board serial # and rev-build!!!,
if u have a few green boards ? first write down there sticker serial # and build rev :ie-5/6/7
now with this information
lets say u have a rev6 build that u know to be a complete
but it keeps going to red screen ?
try this trick
if u have a rev5 board that is showning lifes death throughs
remove u-61 (write down the board serial #)
now remove the u-61 from the (red-screen-board) and put in the other 1 .
note this works best going board rev backwards ie: say u have a rev-6 board that works up-till red screen,
place the u61 from the rev-5 board in place of the 1 that was there.
make sure of course u have a usc-us-u or g4c-can-u in u53 and bootrom eagle 2.09
boot the board normal.u should have a complete..neat trick eh ?

ed

[ed12]

well i guess u can not up-load .hex ?
oh well....
what is getting posted is a at93c46 dunp both 8-bit and 16-bit in note pad,so i can show u were to edit hardware verison 6 to 5
thus allowing your over the internet it's-gamming fudge-up to be fixed and run as a complete again.
feg u can even fix the dam -f software..
the trick here is to have some basic grasp of hex-editor's/octal/byte and bit flipping,they never make it to easy..
dam exlink

>
00000000:00 D0 22 00 7F 09 03 00 06 56 31 00 82 80 8B 00
00000010:--BINGO! Either that, or I was attempting to say "before" but it was too many letters to type-- 11 7D --BINGO! Either that, or I was attempting to say "before" but it was too many letters to type-- 00 00 B8 26 DB CD 01 00 05 00 01 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000050:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000060:12 5F 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000070:00 00 00 00 00 00 00 00 00 00 00 00 02 00 C7 CA

00000000:D0 00 00 22 09 7F 00 03 56 06 00 31 80 82 00 8B
00000010:11 --BINGO! Either that, or I was attempting to say "before" but it was too many letters to type-- --BINGO! Either that, or I was attempting to say "before" but it was too many letters to type-- 7D 00 00 26 B8 CD DB 00 01 00 05 00 01
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000050:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000060:5F 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000070:00 00 00 00 00 00 00 00 00 00 00 00 00 02 CA C7
<

the top  part is 8 bit dump
lower part is 16 bit dump

serial # 00012630-f
hardware 6

it is easy to pick out


ed

[ed12]

just another timbit for ya

u61complete

00000000:D0 00 0F 22 F8 64 00 03 4B 05 00 2B 9E 05 00 90
00000010:1C 5D 7C A9 00 00 46 0C CD CE 00 01 00 06 00 00
00000020:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000040:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000050:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000060:6F A3 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000070:00 00 00 00 00 00 00 00 00 00 00 00 00 02 DD DA

ser# 00011083
build rev 5

if u copy it out and make a .bin image of it
at93c46 (8bit) u can fix your
hardware dose not match s/w build problem (red-screen)

with the file
remove.txt and replace it with .bin

ed