forked from opencode.energia.arti.ee/vt1200
arti
d8d54bb990
The XIE path now runs end to end: XieCreateImage -> XieCreatePhoto ->
XiePutTile -> XieExport(photomap -> depth-1 pixmap) -> XCopyArea(pixmap ->
window), and the client's tile appears on screen at the client's own window
position, pixel-exact.
TWO FAULTS BEHIND THE LONG DEAD END
1. Device model (harness/mame/vt1200.cpp, opt-in VT1200_ACCEL=1). The
accelerator's output port 0x5600200 returns the pixel stream the firmware
pushed into the FIFO -- the firmware then stores it into the drawable itself
(file 0x125528: MOVE *B6,*B1 ; ADDK 0x10,B1). The FIFO read pointer was
never reset between transfers, so consecutive exports read stale words and
the same fill produced 759 then 516 set pixels. Reset m_fifo_in/out on the
data-register write; the export is now deterministic.
2. Measurement, not the device.
- dwt/screenshot.py without --real reads 1024x1024 at a 128-byte row stride,
but the VR319 default programs 1280x1024 at a 2048-bit (256-byte) pitch.
That is the "shifted" picture; --real is the correct read.
- The earlier "0 differing bytes over 128 KiB" VRAM comparison stepped peek
by 1024 *bit* addresses, so it scanned rows 0..63 only -- never the window
at rows 200..263. Over the real raster the white/black diff is 576 bytes
spanning exactly those rows.
- New instrument: decclient does a server-side XGetImage readback of the
pixmap and window and counts set pixels. That separated "the server never
drew it" from "the framebuffer view is wrong".
EVIDENCE (reproduced twice, the second time from a fresh machine)
no export vs 0xFF : 4096 / 4096 pixels differ
no export vs 0x00 : 0 / 4096 (the window background is black)
0xFF vs 0x00 : 4096 / 4096
0xAA vs 0x0F : 2048 / 4096 (the two stripe phases)
Tile byte 0xAA reproduces as 1-pixel vertical stripes, 0x0F as 4-pixel, with
no shear -- so the placement is right and the pixels are the client's.
Contents: xie/ holds DEC XIE 2.3 headers, 84 man pages and complete
client+server source; a libXie.a and decclient built from DEC's own code; the
XIE probes; and evidence/ with every measurement, including explicit
retractions of the earlier wrong readings (VRAM_IDENTICAL_FOR_BOTH_FILLS and
friends). xie/evidence/XIE_IMAGE_DISPLAYED.md is the report; frames are in
xie/evidence/png/.
The accelerator model stays opt-in: it answers the status poll and relays the
pixel stream, but performs no compositing, so it is a stand-in and the verified
default configuration is unchanged (a no-env run still parks in the level-0
diagnostics menu at PC=3FDCE400).
42 lines
1.8 KiB
Plaintext
42 lines
1.8 KiB
Plaintext
ARM CHECK TRACED -- and the printed operands CONTRADICT the static reading.
|
|
|
|
Addresses computed in code this time (my hand-computed ones were wrong by
|
|
0x8000, which is why the previous attempt showed no trace at all).
|
|
|
|
w9=0x100 (byte8=1): arm1 = SILENT(ok)
|
|
ACBA a11=00000002 b8=00 b12=00
|
|
ACBE a7=FFFFFFE9
|
|
ACC4 a7=00000000
|
|
ACCA a7=00000000
|
|
ACD0 a7=FFFFFFFE
|
|
OKPATH_6AD34 <- success path
|
|
|
|
w9=0x300 (byte8=3): arm1 = ERROR 8
|
|
ACBA a11=00000002 b8=00 b12=00
|
|
ACBE a7=FFFFFFE9
|
|
ACD4_BADMATCH <- rejected
|
|
|
|
THE PROBLEM: at 0x6ACBA the static reading says
|
|
6ACBA MOVE *A13(0x20),A11,1 ; A11 should be an OBJECT pointer
|
|
6ACBE MOVE *A11(0x40),A7,0 ; then A7 = object->byte8
|
|
but A11 prints as 00000002, i.e. not an object pointer, and `b@(a11+0x40)` reads
|
|
0 -- so the static reading of this block is WRONG.
|
|
|
|
Also, A7 at ACBE prints the SAME value (FFFFFFE9) for both byte8=1 and byte8=3,
|
|
yet the subsequent branch takes different paths. So the value I am printing is
|
|
not the one that decides the branch, and I have not identified the real operand.
|
|
|
|
Therefore: the reason arm fails on a byte8=3 resource is NOT established by this
|
|
trace. I am recording the negative rather than inventing an explanation.
|
|
|
|
WHAT IS STILL TRUE FROM LAST TURN (measured and reproducible):
|
|
* with object->byte36 pointing at a byte equal to 3, PUT_TILE returns success
|
|
(A8=0) -- the import mechanism works;
|
|
* but arm still fails on that same byte8=3 resource, so EXPORT fails, RP never
|
|
fires, and src_base remains unreadable;
|
|
* the goal (a client-chosen image via XIE) is NOT met, and the successful
|
|
import depended on debug pokes, not on client-reachable state.
|
|
|
|
NEXT would need either a correct reading of the arm check (all registers at
|
|
0x6ACBE, not just A7/A11) or the DEC 2.3 definition of what arm validates.
|