Search results

I had a project recently where I had to interconnect a daughter board with a PCB... The only reliable solution I could get involved machine pin headers on the daughterboard and replacing the sockets on the main PCB with machined round sockets l.

I haven't had time to look at this properly... but I looked at it improperly... Put a 6502 back in the CPU socket; PETTESTER in H7 and... I wonder if that is a clue?

I've taken all the above onboard; just need to find some time to experiment... will probably be the weekend. Thanks all. PS Please don't mention the discolouration in the top left... it's a huge embarrassment! That was in my early days of hot air for chip removal.

Wow! I've read that document so many times and never noticed that! My brain must interpret it as 05! http://www.zimmers.net/anonftp/pub/cbm/schematics/computers/pet/2001/2001_main_logic_assembly.pdf

Revisited... Physical pressure doesn't seem to help. Damp finger is in my diagnostics kit. Yeap moved finger around. Seems most effective near pin 27. When I have time I will whip the PCB out and look for issues. This poor motherboard is used for every gadget I have made so there has been...

The different naming conventions are confusing... but yeap... the very original Basic1 complete with lots of bugs. (Obviously the PETTESTER runs don't verify the contents of H7 since that's where it sits)

So my beloved PET has started to act strange... which is rather annoying as I'm trying to test some bits and pieces before sending them out to people... It won't reliably start unless I put my finger on pin 27 of the CPU... If I leave my finger there it performs perfectly. Could this be a...

B Sockets - Not recognised rom-1-c000.901439-01.bin 0xe85f 0x0 0xe85f rom-1-c800.901439-05.bin 0xe4fe 0x0 0xe4fe rom-1-d800.901439-06.bin 0x1e49 0x0 0x1e49 rom-1-d000.901439-02.bin 0x31fc 0x0 0x31fc rom-1-e000.901439-03.bin 0xca92 0x0 0xca92 rom-1-f000.901439-04.bin 0xf21c 0x0 0xf21c...

FWIW... and mostly for @daver2 's benefit... copies of my bodged versions and source...

Hi. I did do a bit of poetic licence and sent you the version that goes in H7. It should say put in H7 on the label ;) Can you remove the Tynemouth board, just put it in H7 and have a 6502 in the CPU socket. And send a photo of what you have set up. It really shouldn't look like what you...

http://www.zimmers.net/anonftp/pub/cbm/schematics/computers/pet/8032/8032029-01.gif Indeed... a simple reset circuit. Strange goings on can be many things... RAM, ROM, .... etc... Probably the best approach would be to burn @daver2 's PETTESTER and give your PET a workout.

On my way to the post box. :)

Well I should have warmed up the soldering iron so I could put @rglenn 's ROM in the post but I couldn't resist a small hack of the PETTESTER source... ROM Top line is original sums... next line should be a sum of only the first 2K... in the E case they match since only 2K of E is summed first...

@daver2 Is V5 ready? 2K Checksums would be nice here!

OK... lo 2K hi 2K 4K basic-2-c000.901465-01.bin 0xa347 0x94f1 0x3838 basic-2-d000.901465-02.bin 0xa7f1 0xa879 0x506a basic-4-b000.901465-19.bin 0x9f95 0xacc9 0x4c5e basic-4-b000.901465-23.bin 0xa005 0xa163 0x4168 basic-4-c000.901465-20.bin 0x9e94 0xbacc 0x5960...

rom-1-c000.901439-01.bin 0xe85f rom-1-c800.901439-05.bin 0xe4fe rom-1-d000.901439-02.bin 0x31fc rom-1-d800.901439-06.bin 0x1e49 rom-1-e000.901439-03.bin 0xca92 rom-1-f000.901439-04.bin 0xf21c rom-1-f800.901439-07.bin 0x1a88 rom-2-c000.901439-09.bin 0xe7cb rom-3-c000.901439-13.bin 0xa347...

You could... but there are probably cheaper alternatives if you aren't too worried about aesthetics. You can get a ROM adapter for a more commonly available ROM and find a friend in your region who would program for you. Maybe I should try and change my design to be black with the bits on the...

12 is rom-1-f000.901439-04.bin aka 6540-016... something you would expect to find in H4 and service F000-F7FF.. one looks good* We are looking for an A6 *ah... that was probably substituted! doh

I wrote a quick program... rom-1-c000.901439-01.bin 0x4b rom-1-c800.901439-05.bin 0xe6 rom-1-d000.901439-02.bin 0x32 rom-1-d800.901439-06.bin 0x6b rom-1-e000.901439-03.bin 0x60 rom-1-f000.901439-04.bin 0x12 rom-1-f800.901439-07.bin 0xa6 rom-2-c000.901439-09.bin 0xb6 rom-3-c000.901439-13.bin...

Using VOSSI for the 2K ROM test is a good idea. The checksum isn't very robust... I think it is a bit weird... but it should match if they do perfectly match. Might match even if they don't. 2K checksums in PETTESTER might be nice ;) checksum_11 = $4b ; rom checksums...