Wanted Diagrom V1.3 Manual User ?...

[dwprod38]

Hello,

I'm looking for detailed document of DiagRom V1.3 for better understanding hexadecimal data displayed on Putty software as shown below.

Included full description of corresponding codes addresses like as "INTENA", "INTREQ", "DMACON", "OVL", "UDS/LVS" and table of allocated memory which indicate us the concerned component associated with different addresses functions... I've found nothing on "Diagrom.com" website and impossible to have email contact with John "Chucky" Hertell.

Thanks,
Stef

 

[arnljot]

Have you checked to see the tools github repo to see if an issue addresses your concern?

John is very busy, but some users help eachother on the issue tracker and points users to solutions if they can.

I would venture to guess that most hexadecimal data are addresses, either to memory or memory allocated to registers. NTENA / INTREQ / DMACON are standard Amiga custom‑chip registers at $DFF09A, $DFF09C, and $DFF096 respectively; DiagROM just reads/writes them and prints the values over serial so you can see interrupt and DMA enable/request bits.
OVL is the overlay control bit in the Gary/custom logic that switches the address space at $00000000 between Kickstart ROM and RAM; DiagROM’s “Testing if OVL is working: OK” message comes from the code that repeatedly writes/reads low memory while toggling this bit.

UDS/LDS are the 68k upper‑ and lower‑data‑strobe lines; the “Parallel Code $FE – Test UDS/LDS line” part is a short routine that writes a word to a chosen address and checks if both halves of the bus respond correctly.

Then the list below shows what was written and which bits came back wrong.

I'm just venturing a guess here, I am no Amiga hardware expert, software expert or ROM expert.

You could also gleam some from the DiagROM.s source file, where the text is defined, and then where it's later used.

I believe DiagROM is a tool mostly meant for those who have the ROMKernel guides ingraved in their brains, and who know the amiga PCB inside and out... I'm not one of those, but I ask Perplexity.ai, look at the code and I try to figure out. And also I ask here like you.

Hope you figure this one out my friend!

 

[Bruce72]

Looking at the output of the RAM scan, it is identifying that bits 0-7, and 9-16 are all being held high. and this should be the first fault to fix.

What machine are you building/repairing?