Stuart

Not consistently true - I'd say "tie-tanium". So it's consistent with urinal, should I ever happen to use both words in the same sentence. And Titanic. There's a titanic tie-tanium yoo-rai-nal in the cupboard under the stairs.

Have you checked the CF card itself? ISTR it hangs on boot if it can't access a (working) card.

Of the 7 received, 4 worked, 3 duds.

What gives these away as fakes?

I've got 10 off HY6264ALP-10 8Kx8 RAMs looking for a new home. Any use to anyone looking to expand a RAMDisk or something? Completely untested! No guarantees! No returns! Yours for the cost of postage from me in the UK to wherever you are.

You could if you like merge the synth with the backing track also played by a TMS9900 ...

Our Father who art in Heaven, Please let my QI TI work, Without undue RF interference, ...

For my Internet Browser, I took the simple approach of just checking in what direction the mouse is moving, and ignoring how fast the mouse was moving. The screen resolution for the TI is so low that trying to implement any form of mouse 'acceleration' didn't really seem worth the effort. I move the cursor two pixels at a time which is fine for the browser but no use of course for any drawing-type programmes. I've copied below the mouse code in case it is of any use. *No key pressed and no joystick movement. Check if any movement from TIPI mouse. CHKMSE BL @RDTPMSE Read data from TIPI mouse. Data returned in buffer MSEBUFF. CLR R4 Flag to indicate if there was mouse movement. CLR R1 MOVB @MSEBUFF,R1 Get horizontal movement. This is: * >00 = no horizontal movement * >FF (slow) - >81 (fast) = movement left * >01 (slow) - >7F (fast) = movement right JEQ CHKMSE2 No horizontal movement. Check vertical. SETO R4 Set flag to indicate mouse movement. (Instruction doesn't affect any status bits) JGT CHKMSE4 Jump if movement to the right. DECT R2 Movement is to the left. Decrement X position. JMP CHKMSE2 CHKMSE4 INCT R2 Increment X position. CHKMSE2 MOVB @MSEBUFF+1,R1 Get vertical movement. This is: * >00 = no vertical movement * >FF (slow) - >81 (fast) = movement up * >01 (slow) - >7F (fast) = movement down JEQ CHKMSE3 No vertical movement. Check button. SETO R4 Set flag to indicate mouse movement. (Instruction doesn't affect any status bits) JGT CHKMSE5 Jump if movement down. DECT R3 Movement is up. Decrement Y position. JMP CHKMSE3 CHKMSE5 INCT R3 Increment Y position. CHKMSE3 MOVB @MSEBUFF+2,R1 Get button press. This is: * >x8 = no button press * >x9 = left button press * >xA = right button press (not used by the browser) ANDI R1,>0F00 Isolate required nibble. CI R1,>0900 Left button press? JEQ JOYFIRE Yes. Jump to routine that handles keyboard <ENTER> key (via joystick routine as jump out of range). MOV R4,R4 Flag set to indicate mouse movement? JEQ MSST001 No, jump to continue. B @MSSP10 Yes, process new sprite position. **************************************************************** *Subroutine - read data from TIPI mouse. *Call: BL @RDTPMSE **************************************************************** RDTPMSE MOV R11,@SAVR11 Save return address. LI R1,1 Number of bytes in message to send. MOV R1,@GPLWSR0 Save in GPL workspace R0. LI R1,B20 Address of message to send. MOV R1,@GPLWSR1 Save in GPL workspace R1. MOV @MSEBUFA,@TIPIBUF Set TIPI buffer address. BL @TIPICOM Send TIPI command message and get result, which is three bytes - * horizontal movement, vertical movement, and button press. MOV @SAVR11,R11 Restore return address. B *R11 Return.

Exactly what I done three posts above ...

This thread: https://atariage.com/forums/topic/288694-wanted-replacement-pal-chip-corcomp-fdc-1985-rev-a-u12/page/2/#comments I worked out a first iteration of the PAL equations based on the info from Helocast, but it needs someone who can program and re-read the PAL data to check and refine them.

Nothing new ... but have been having an e-mail chat with a chap helping to restore a Royal Observer Corp Group HQ Bunker in Scotland (that's the northern bit of the UK!). This is one of a number of HQ Bunkers that would receive information from smaller 3-man underground bunkers about the spread of nuclear fallout in the UK in the event of someone dropping one or more nuclear bombs on us. Operational up to the early 90's. They've got a number of bits of kit that use the TMS9900 and 9995 that they're restoring, and they were after one of my TMS9900 PCBs to use as a simple way to test their processors and clock chips. https://www.facebook.com/28Group/ if you're interested. It's a Facebook page but if you haven't got an Facebook account just click the "Not Now" link towards the bottom right of the login banner displayed and you can scroll through to your heart's content and try to spot our favourite processors.

It is being sold by Jaime, who designed the NanoPEB.

http://www.stuartconner.me.uk/ti/ti.htm#connecting_serial_mouse

Indeed, which means that you'd have to sit at your terminal typing away at a steady speed, never slowing down or deviating, never stopping ... I suspect what dhe vaguely remembers is that you could pop a 9903 in a 9902 socket (it is one pin shorter so has to go at one end of the socket), but the synchronous protocol and serial connections are different to the RS-232 interface provided by the 9902. You *can* design the board to support both but it needs a 25-pin serial connector and you need a terminal that supports the same synchronous connection.

It's the LMF instruction - Load Memory Map File - opcode 0320 - from the 990/10 and 990/12 processors. They have 21 instruction formats - ouch!

Did you look at [http://www.stuartconner.me.uk/ti/ti.htm#tipi_network_socket_interface], scroll down to: **************************************************** *Find CRU address of TIPI device. **************************************************** That code will find the CRU address of the TIPI. (Code is largely based on code I found elsewhere)

Hi Fabrice, They're all yours. PM me your mailing address and I'll get them in the post to you during the week. If I then let you know the postage cost, can you PayPal me the money? Stuart

I've been given the following: -- Approx 5 HM628128ALP-7 128KB static RAMs -- Approx 10 HM62256BLP-7 32KB static RAMs -- Approx 10 HY6264LP-10 8KB static RAMs Any use to anyone? They're free except for the cost of postage and packing from me in the UK. To post to the US will cost about UK£10. They're quite possibly from China. I haven't tested any of them. No guarantees or refunds! Stuart

Have you looked at something like https://electronics.stackexchange.com/questions/286052/divide-clock-frequency-by-3-with-50-duty-cycle-by-using-a-karnaugh-map ? Pretty simple if you're not worried about the duty cycle.

If you pull one of the 9901 programmable inputs either high or low then use the TB instruction to read the state of that input, then you'll know whether CRUIN will be high or low? So if you pull CRUIN high through a resistor and use it to measure a low input, it should be fairly obvious when it goes hi-Z?

I use a USB-to-barrel connector power cable, and power the board from a USB socket on the computer I use for the serial terminal. I was given a 99110, but have only ever seen 99105s for sale on eBay. So at least one 99110 exists.

If you're able, try replacing U10 and U11 on the card - both 74LS373. They provide the interface between the PIO connector and the rest of the card.

DATA >0340 will do it.

If your power supply is OK (the voltage on each output pin should be marked on the PCB right next to the connector) then you might be better off by first replacing the two static RAM chips - those are the two larger chips marked "MCM6810P". You can get those off eBay. The VRAM RAM chips (the block of eight marked MCM4116... and TMS4116...) can and frequently do go bad, but they usually result in a corrupted display rather stopping the machine booting altogether. Get some decent quality cutters so you can cut the IC pins individually with the IC still on the board then you can remove the IC body, then you can unsolder and remove each pin individually. This will reduce the risk of damaging the PCB. Fit a turned-pin socket to the PCB to plug the new IC into.

The PEB cable 'foot' that plugs into the console? (With some questionable soldering quality bottom right ...)