I am just starting to test my unibone with the various .cmd scripts. It had had old software, and Jeorg sent me info to update it, which seems to have worked.
But I have noticed an oddity. Several of the command scripts in ~/10.03_app_demo/5_applications/cpu have instructions or actually scripted commands to start the CPU running via "p c 1". However, the software I have doesn't accept that, instead cpu20 is looking for "p r 1".
Is that just me? Is my software messed up?
Also while XXDP boots and runs in my setup, rt11 gets started trying to run, but then gets hung up in some sort of loop. mini-unix comes up with the "@" prompt, and upon entering the expected "rkmx<LF>" (where <LF> is a linefeed newline character) it prints out (very slowly) the AT&T banner stuff, but never issues the "login:" prompt.
(Note: I have the Unibone in slot 1 of a 9 slot backplane, real terminator in slot 1, real memory in slot 8, Uniprobe in slot 9, with complete grant chain intact. Memory size is 128kw, and the unibone "sz" command detects memory from 000000 to 757776 - 0x3DFFE (which allows for an 8K I/O page) so, more than an 11/20 could address, but the 11/20 *should* take any address with the highest bits on, and extend it to 764000 on up - and once started up with "p r 1" hello.cmd works OK. The "tm" and "tr" commands work fine with the memory.
(I'm also going to try it with emulated memory to see what that does...)