SAD Version 5 (alpha)

All hardware related, disassembly / programming and code discussions belong here.
tvrfan
Posts: 88
Joined: 2023 Oct 22, 22:13
Location: New Zealand
Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.

EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler

Re: SAD Version 5 (alpha)

Unread post by tvrfan »

Always open to new ideas, and I hope you understand if I ask "why?" it's not because I object, but more info on why you ask may lead to a different and better idea between us all, or may merge into something else. More info is always better !

1. Overlapping fields (word and byte) - do you have an example where this is used ? As far as I know values are not used interchangeably as word and byte (and long) anywhere except when used for scaling purposes (e.g. x/128 or x * 128). Some values are used multiple times and scaled differently, but stay as one base 'size' . If it's for symbol names, I changed the validation after discussions with jsa so that names CAN overlap, and only a true duplicate is rejected. In the latest V5, but args broken.

2. Looped scan - Um, sorry don't know what you are after. Currently a 'scan 01234' should start at 01234 and then do the whole 'tree' of code below it - everything called or jumped to. An example and more info please (even if it's made up) ? Thanks.
If it's linked to the idea that a code loop is emulated to get all the DATA it refers too, this is on my agenda already, but I haven't got that far. Yes, there are lots of 'lists' of things that would then pop up.
jsa
Posts: 274
Joined: 2021 Feb 16, 15:46
Location: Australia
Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV

Binary Editor
ForDiag

Re: SAD Version 5 (alpha)

Unread post by jsa »

The address / inline scalar issue...
http://www.efidynotuning.com/forum/view ... 678#p14506
BOOSTEDEVERYTHING
Posts: 235
Joined: 2023 Sep 06, 13:11
Location: Charlotte NC , USA
Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100

Re: SAD Version 5 (alpha)

Unread post by BOOSTEDEVERYTHING »

I am not sure exactly how to describe the looped scan function, but if you take a look at my directive file you will see how many scan commands I had to use to make it through just 2 banks. Right now it seems that as soon as it finds a stopping point, it stops scanning. I will see if I can make a dir with just the scan codes to give you a clearer view. It would be awesome if it would scan a range of code if you put a start and end address for it to scan, where it wouldn't stop until it got to the end of the range. I guess that may be the easiest way to explain it, I guess. Maybe JSA could elaborate on it a bit...

Also, You will see examples of the byte and word values that I am talking about in my dir file. Again, I am very new, and I am following examples in the dir files I am given, Maybe there is a better way of doing it, or maybe I am misunderstanding the dir files?? Thanks for being so open to new ideas, especially from someone so new to this.
Attachments
Stock_EKO2.zip
(339.46 KiB) Downloaded 8 times
jsa
Posts: 274
Joined: 2021 Feb 16, 15:46
Location: Australia
Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV

Binary Editor
ForDiag

Re: SAD Version 5 (alpha)

Unread post by jsa »

At the moment the scan command takes a start address and scans until it hits a return.

Scan over a range would take a start address and an end address.

If a scan reaches a return before the end address, scan would start at the next address after the return and scan again. Repeat until the start to end address range is scanned entirely.

Yes, some bins require an excessive number of scan commands, that could be alleviated with scan range.
Post Reply