News:

Printed Amstrad Addict magazine announced, check it out here!

Main Menu

Recent posts

#1
Isn't this a reasonably well known issue with CMOS Z80s ( I think I've seen speculation that, since the instruction was unintended, it's just a result of how internal signals value when floating differs between NMOS/CMOS)

There's also a slight difference in LD A,R/LD A,I behaviour according to @arnoldemu 

https://www.cpcwiki.eu/forum/amstrad-cpc-hardware/z80-cpu-nmos-or-cmos/
#3
OUT (c),0 working  :-* but like OUT (c),255   :picard: ;D

OUT &BC00,15: OUT &BD00,15: rem CURSOR REGISTER
?INP(&BFFF)
15
CALL &BFFC, &e9dd ,&c9 ,  &71ED,     &BD00, &100
REM             JP(IX)   RET   OUT(c),0    LD BC,&BD00
? INP(&BFFF)
255

Dear Zilog, does 1 CY really save you?  :-\

But SymbOS working  :D
#4
Isn't the DDI-1 wired to supply 5v on the floppy cable?

Could that damage the CPC?
#5
Quote from: Bryce on Today at 18:29https://www.cpcwiki.eu/index.php/File:Floppy_Cable.png

Bryce.
Hi Bryce!
Thank you for the link
I already had it.
so it's wire to wire wiring?
Thanks
#7
Hello everyone,
So here I am going to try to be clear in my explanations.
I have a Schneider DDI-1 (external reader) with its Amsdos interface for my CPC 464. Everything works perfectly.
I would like to make a cable that directly connects my DDI-1 to my CPC 6128 (EDGE port).
Just by replacing the AMSDOS interface.
of course I would like to keep my internal 3" drive in A and the external one in B
I have the 34p cable, the 34p female connector and the EDGE connector.
The problem is that I don't know the exact pinout. I read a little bit of everything.
If anyone has a diagram that would be great.
Thanks for reading me.
Willow3411
#8
OUT (C),0 is used in all optimized AY routines, so yes, that makes sense with the corrupted sound.
#9
avatar_roudoudou
Programming / Re: bits 5 and 3 of F register...
Last post by roudoudou - Today at 15:14

iterating or not with LDI or LDIR, you keep S, Z and C
then you set P when BC will be zeroed
about the non documented behaviour, it's something like this

(((databusValue+A) & 2)<<4) | ((databusValue+A) & FLAG_3_BIT);
#10
most of problems are due to (i guess) OUT (C),0 undocumented opcode which was fixed (or reassigned) in later versions
Powered by SMFPacks Menu Editor Mod