accessing 0x3000 region of hardware in 730
#1
Member
Thread Starter
Join Date: Jun 2001
Location: Eh?
Posts: 391
Likes: 0
Received 0 Likes
on
0 Posts
Car: 1988 Monte Carlo SS
Engine: 5.7L TPI
Transmission: T5
Axle/Gears: 3.73
accessing 0x3000 region of hardware in 730
I'm loosing my mind here....
Using aldl data read commands, I can read locations 0x3130 and 0x3131 and see the value incrementing while an engine is running. But if I patch in some code in the 160Hz loop (or in segment 2) to copy these values to my nvsram module, I always read back the value 0x30 and 0x31 respectively (using the same aldl data read commands).
Is there some bit somewhere that needs to be set or cleared to make this region of memory accessable outside of the ALDL tx routine??
Thx...
Using aldl data read commands, I can read locations 0x3130 and 0x3131 and see the value incrementing while an engine is running. But if I patch in some code in the 160Hz loop (or in segment 2) to copy these values to my nvsram module, I always read back the value 0x30 and 0x31 respectively (using the same aldl data read commands).
Is there some bit somewhere that needs to be set or cleared to make this region of memory accessable outside of the ALDL tx routine??
Thx...
Code:
ARRRRRRRG: psha ldaa 0x3130 staa 0x2C01 ldaa 0x3131 staa 0x2C02 pula jmp (address withheld)
Last edited by MonteCarSlow; 07-22-2006 at 04:08 PM.
#2
Junior Member
iTrader: (2)
Join Date: Jun 2001
Location: Sayre, PA
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by MonteCarSlow
I'm loosing my mind here....
Using aldl data read commands, I can read locations 0x3130 and 0x3131 and see the value incrementing while an engine is running. But if I patch in some code in the 160Hz loop (or in segment 2) to copy these values to my nvsram module, I always read back the value 0x30 and 0x31 respectively (using the same aldl data read commands).
Is there some bit somewhere that needs to be set or cleared to make this region of memory accessable outside of the ALDL tx routine??
Thx...
Using aldl data read commands, I can read locations 0x3130 and 0x3131 and see the value incrementing while an engine is running. But if I patch in some code in the 160Hz loop (or in segment 2) to copy these values to my nvsram module, I always read back the value 0x30 and 0x31 respectively (using the same aldl data read commands).
Is there some bit somewhere that needs to be set or cleared to make this region of memory accessable outside of the ALDL tx routine??
Thx...
Code:
ARRRRRRRG: psha ldaa 0x3130 staa 0x2C01 ldaa 0x3131 staa 0x2C02 pula jmp (address withheld)
If you really read address 0x3130 outside of the ALDL transmit routine, who knows what you are reading... The timer chip may respond, I don't know.
Scot
#3
Member
Thread Starter
Join Date: Jun 2001
Location: Eh?
Posts: 391
Likes: 0
Received 0 Likes
on
0 Posts
Car: 1988 Monte Carlo SS
Engine: 5.7L TPI
Transmission: T5
Axle/Gears: 3.73
Bwaaahhahahaa.....
Thanks Scot.
Everything makes so much more sense now. Me, being more of a h/w guy, assumed these were hardware counters...
Thanks Scot.
Everything makes so much more sense now. Me, being more of a h/w guy, assumed these were hardware counters...
#4
The "3" preceeding the address means that the ALDL value that follows is double byte word.
When a double byte word is set up for transmit in the ALDL tables, a $3xxx or $4xxx must be appended to the address to flag the software to load both bytes of the word simultaneously in order to ensure consistency.
If the word is in the $0-$3FF address range, a "3" is appended. If the word is in the 2K RAM chip ($1800-$1FFF range), a "4" is appended.
Todd
When a double byte word is set up for transmit in the ALDL tables, a $3xxx or $4xxx must be appended to the address to flag the software to load both bytes of the word simultaneously in order to ensure consistency.
If the word is in the $0-$3FF address range, a "3" is appended. If the word is in the 2K RAM chip ($1800-$1FFF range), a "4" is appended.
Todd
#5
How did you figure that out?
I've been tripping over that for a few years. The PW in 8D is transmitted that way.
RBob dropped a hint a few months back by I didn't have time for a tangent.
I've been tripping over that for a few years. The PW in 8D is transmitted that way.
RBob dropped a hint a few months back by I didn't have time for a tangent.
#6
Supreme Member
iTrader: (2)
Join Date: Jan 2002
Location: Moorestown, NJ
Posts: 9,962
Likes: 0
Received 3 Likes
on
3 Posts
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
Originally Posted by MonteCarSlow
Bwaaahhahahaa.....
Thanks Scot.
Everything makes so much more sense now. Me, being more of a h/w guy, assumed these were hardware counters...
Thanks Scot.
Everything makes so much more sense now. Me, being more of a h/w guy, assumed these were hardware counters...
Last edited by dimented24x7; 07-26-2006 at 02:24 AM.
Thread
Thread Starter
Forum
Replies
Last Post
88SS6SPEED
Engine/Drivetrain/Suspension Parts for Sale
7
11-11-2015 07:05 AM
sjorgens
Suspension and Chassis
7
10-01-2015 07:54 PM