Awesome!
Looks a lot better, I just ran it through my decompiler and posted the
first pass here:
https://github.com/BiggRanger/Tandy_PDD/blob/master/PDD2.ASM
There are still some invalid opcodes floating around, I need to dig
deeper and see what is going on there. I also see several lookup
128 more bytes ;)
On Tue, Jan 23, 2024 at 3:28 PM Stephen Adolph wrote:
> It was a first pass attempt. I captured it as 128 blocks of 32 bytes.
> Was it
>
> On Tuesday, January 23, 2024, Darren Clark wrote:
>
>> Hello Steve,
>>
>> Looks awesome so far! I've started to manually decompile
I had that thing about request format 0x47 backwards. Tpdd1 ignores 0x47,
tpdd2 responds to it, which makes more sense, since it's just like several
other commands on tpdd2. Doesn't matter to anyone but just for the record
to correct saying it backwards before.
bkw
On Wed, Jan 10, 2024, 11:49
It was a first pass attempt. I captured it as 128 blocks of 32 bytes. Was
it
On Tuesday, January 23, 2024, Darren Clark wrote:
> Hello Steve,
>
> Looks awesome so far! I've started to manually decompile it and some
> things are not making sense.
>
> The first 3 bytes 0x8e, 0x87, 0xFF do
It was a first pass attempt. I captured it as 128 blocks of 32 bytes.
I'll check that I didn't cut off the file by accident.
On Tuesday, January 23, 2024, Darren Clark wrote:
> Hello Steve,
>
> Looks awesome so far! I've started to manually decompile it and some
> things are not making
Interesting, going down the rabbit hole Futamura is referenced in
this patent https://uspto.report/patent/grant/6202001 for an embroidery
data creating device for Brother. If I remember correctly the TPDD was
originally sourced or is the same as a drive used in a Brother
embroiderymachine.
Hello Steve,
I RDP's into my home system and ran the binary through my
decompiler. It looks like there might be an issue with how the ROM was
pulled. It's missing a byte every 32 bytes, so I'm getting a lot of
invalid opcodes. That could also explain the missing 128 bytes at the
end
Hello Steve,
Looks awesome so far! I've started to manually decompile it and
some things are not making sense.
The first 3 bytes 0x8e, 0x87, 0xFF do make sense this puts the stack
pointer at address 0x87FF, the top of the external RAM. This is good.
Normally there is some other
Thanks Bert,
Already got the belts replaced, but good to be ready for working on my two
TPDD2 in the ffuture.
GregS <><
Sent from my iPad
> On Jan 8, 2024, at 10:23 AM, bir...@soigeneris.com wrote:
>
>
> The TPDD2 service manual in all of its glory...
>
>
these look like 6301 opcodes. Maybe this worked.
take a look please when you can. thanks. Steve
On Tue, Jan 9, 2024 at 6:55 PM Darren Clark wrote:
> TPDD2 firmware dumping - breaking this into a new thread.
>
> It would be interesting to see if we can use the command 'Request Block'
> from
Oh yeah and we know who wrote it:
M.FUTAMURA
On Mon, Jan 22, 2024 at 11:21 PM Stephen Adolph
wrote:
> these look like 6301 opcodes. Maybe this worked.
> take a look please when you can. thanks. Steve
>
>
> On Tue, Jan 9, 2024 at 6:55 PM Darren Clark wrote:
>
>> TPDD2 firmware dumping -
11 matches
Mail list logo
