Welcome, Guest. Please login or register.


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - gflorez

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 185
46
Hardver / Re: Hajdani konfigom...
« on: 2020.March.18. 15:16:59 »
Thanks Scipucsu and Zozo, I will try the bilingual way, but some times the answer is slower.

47
Hardver / Re: Hajdani konfigom...
« on: 2020.March.18. 15:08:03 »
Yo sí, pero yo pienso que estoy solo con éso. O, pienso de estar solo con éso. :D

Better:  "Yo sí, pero yo pienso que estoy solo con en eso(not éso)."

In Spanish it is odd to put the subject several times, often even there is not subject because there are other particles conjugated, even non verbs, that implicitly point to it. Example: "Voy a comer", "¡Tiene guasa!" or "Mal vamos...".

48
Hardver / Re: Hajdani konfigom...
« on: 2020.March.18. 13:37:09 »
Machine translation butchered it. Again. Why do you keep insisting on that?

Sorry for insisting on that.

When I use Google Translate I also ask the reverse translation, to see if the sentence looks close to what I want to mean.

Please forgive me if I bothered you, but only living in Hungary for several years I could write your difficult language like you. I think the important thing is that we can communicate.

The threads in Hungarian interest me as much as the others, and I will continue to comment on them if I think I can contribute something.

¿Quieres que te lo explique en Castellano?

49
Programming / Re:Converting old Ocean games
« on: 2020.March.18. 10:01:37 »
The machine even has Arabic characters on the keyboard as well as the English characters, which made it an interesting variant to see for sale.

Anyway, I'm afraid that I won't even be able to see the output from the computer (and verify the EXOS version) until I make an RGB-to-BNC cable, because I don't have a PAL TV.

Yes, the emulator is the best tool to develop, with all its options to debug, find strings, trace, disassembly, etc.

You can know more about the Egyptian Enterprise units here.

If you name the maker and model of your monitor we can aid you to make the video cable. If it has BNC connectors it is a professional one, sometimes they need Sync on Green or other strange ways to input the Sync signal.

50
Programming / Re: ScoreTrack, Vilmos Kopácsy MIDI attempt
« on: 2020.March.17. 12:14:08 »
Questions, aren't they the fuel that drives us humans?

----

I don't know from where to start, because I must return to some facts that I explained on the first commentary of this thread.

I think that the Midi interface that has arrived to our hands after so long time was made for the cartridge port for one very good reason. It was always an underused expansion port, out of being the place to put the necessary Basic Rom cartridge.

Probably the main reason for the unknown Jefrey(the name of the Rom writer and probably real developer) was to offer an interface that could be connected to all Enterprises, independently of the other expansions connected at the right side of the computer. The same objective than guided Szörg to put the SD reader there.  

But it is a very limited port to put devices, because the signals that arrive to it are oriented only to manage memory. This problem has been excellently solved in the case of the SD reader, using a memory zone as the interchange gate to the SD content.

On the Midi interface they did some similar, the two necessary ports where paginated on memory positions BFF8 and BFF9, on segment 7 put on page 03. The Rom is 32KB wide, and is placed on the 06 and 07 segments, allowing the cartridge to still hold copies of the language Rom on 04 and Basic Rom on 05 segments.

I have found that almost all Midi interfaces of that era made for MSX, BBC, CPC, PCW, Spectrum, used the same UART chip, the MC68B50. This chip doesn't have internally a lot of baud-rates to select, only 3 but related to the external oscillator used(1:1, 1:16, and 1:64). The 3 variants of the chip are the 1, 1.5 and 2Mhz versions, and the several Midi interface makers always selected the MC68B50 because its 2MH oscillator frequency, on the third selection, gives exactly the Midi baud-rate: 2.000.000/64=31250. Then only remains to select the serial protocol, 8bit and 1 stop bit and the chip has been configured.

It has 4 x 8 bit registers, Control(write), Status(read), Transmit Data(write) and Receive Data(read), and usually the interface makers joint all on only 2 ports, Control/Status and Data. Control is only used for initialisation, and is where we define the baud-rate and serial protocol.

 

Bits 5, 6 and 7 are used for interrupts, not applicable on the Cartridge Bus. They will go as Zeros.

Then you can see that  the initialisation is well defined, first we reset the chip writing 03h(00000011b) on the Control register, and then we write 16h(00010110d, 22d), this is, select 1:64 frequency and 8bit word with 1 stop bit.

Now, let's see what happens on the ScoreTrack Rom( I know the position because it was where IstvanV modified the Rom to work on the emulator):

Code: [Select]
*C146  32 F8 BF     LD    (BFF8), A     ; A arrives here with 00000111, perfect to reset the chip
  C149  3E 16        LD    A, 16h        ; 00010110 sets 1:64 frequency, 8 bit, 1 stop bit
  C14B  32 F8 BF     LD    (BFF8), A

Not needing any control except erasing the emulator Midi buffers, IstvanV modified it as this:

Code: [Select]
*C146  00     NOP
  C147  00     NOP
  C148  00     NOP
  C149  00     NOP
  C14A  00     NOP
  C14B  AF           XOR   A
  C14C  D3 F6        OUT   (F6), A       ; a Zero clears out buffer

To transmit data, the chip has the Status register, that has to be watched by the processor to know when there is data to receive or when it can send.  The Receive register is the bit 0, and the Send register is bit 1. The rest of bits are not important here.

On the ScoreTrack Rom there is only Midi OUT because the program is unfinished:

Code: [Select]
*DCB6  3A F8 BF     LD    A, (BFF8)
  DCB9  CB 4F        BIT   1, A         ; bit 1 marks if the data has been send
  DCBB  28 F9        JR    Z, DCB6
  DCBD  F1           POP   AF
  DCBE  32 F9 BF     LD    (BFF9), A    ;write the Midi OUT buffer

IstvanV modified it as this:

Code: [Select]
*DCB6  00           NOP
  DCB7  DB F6        IN    A, (F6)
  DCB9  CB 77        BIT   6, A          ; Send bit
  DCBB  20 FA        JR    NZ, DCB7
  DCBD  F1           POP   AF
  DCBE  D3 F7        OUT   (F7), A       ;Midi OUT
  DCC0  00           NOP


And then, here come my questions:

Why has made IstvanV so drastic changes to the code? Where they necessary? Some of you can contact him?

Because, we have to decide NOW if we must follow his changes, and remain compatible with the EP emulator and the Midi utilities, or on the contrary, emulate correctly the MC68B50, that will allow further development of the ScoreTrack program, share the chip emulation on the other computers that are supported by the  SF3, and probably we will have the opportunity to see easier sequencer conversions from other platforms that use the same chip, like CPC, even MSX.

Edit: if not evident, I want to mark the things that have been changed and apply or not apply to a good MC68B50 emulation:

-He has substituted the memory paginated ports for real unused ports. Good.
-Instead of the sequence 03h,16h written on the Control register for the chip initialisation he has opted to only write a Zero. Bad.
-On the Status byte, the Receive and Transmit bits have been changed from 0 and 1 bits to the 7 and 6 bits. Bad.
-The values of the bits inside the status byte has been negated, as you can see on the conditional jump. Bad.

51
Hardver / Re: Hajdani konfigom...
« on: 2020.March.16. 20:41:32 »
De 3D darabokat készít és tesztel, összefonódásokat készít, illeszkedik, tehát továbbra is aktív fejlesztő (alfa), nem pusztán javító hibák (béta).

Nagyszerű munka!

52
Hardware / Re: SymbiFace3 is near your Enterprise...
« on: 2020.March.16. 10:42:52 »
GREAT!

53
Programming / Re:Converting old Ocean games
« on: 2020.March.15. 10:13:05 »
Great news!

But a 64KB Enterprise is not the best model to start with. First it has EXOS 2.0, slightly incompatible with the definitive 2.1 version all stock 128KB models have. All modified EXOS Roms by Zozo are based on it.

Second, some hardware problems where fixed on the later 64KB models, but definitively on the 128KB model.
 
But almost all these issues can be fixed if you are handy and do not fear to open the EP.

54
Hardware / Re: SymbiFace3 is near your Enterprise...
« on: 2020.March.13. 22:23:51 »
One idea I have is to use a flat ribbon cable male to female like this to connect the SF3 to the future SF3 slot adapter, making a Z with the 2 pcbs and the ribbon cable the SF3 can be lowered at max. to the Bus expander surface, but this only can be made on the first slot because this approach can be very thick.


But then the SF3 would need to be fixed in some way to the future SF3 slot adapter.

55
Hardware / Re: SymbiFace3 is near your Enterprise...
« on: 2020.March.13. 20:58:56 »
Zozo asks me:  you also will make a "SF3 adapter board with a 245" for a bus card slots?


Yes, it is my intention, to make better use of the Bus Expander, but the designs I have done, due my poor experience with Eagle, are modifications of the MSX slot adapter, actually very tall.

It is not so important on a MSX cartridge, but the SF3 has already a respectable length....

See what happens when I put the SF3(not connected...) above a M-SLOT adapter on the Bus Expander:

24498-0

Ok, subtract 1 cm. because the Sf3 is not connected, but 21 cm. tall is very ugly to see at the side of our slim computer....

May be using a 4 layer design I could shorten it some cm.

I accept ideas......

56
Hardware / Re: SymbiFace3 is near your Enterprise...
« on: 2020.March.13. 20:07:36 »
In order to make work the SF3 with the new adapter, a simple lead has to be sold:

24492-0

24494-1


To fix some memory issues that happened interfacing the SF3, a 74LS245 chip was needed to protect the Data Bus. Actually this chip is in every Enterprise expansion, so it was the logical move.

But Hans found that there was no free pin to implement it on the CPC connector, so he redefined the TP3 point to be /Busdir, a returning signal that activates when memory(RAM/ROM) or ports are accessed(decoded) inside the SF3.

The lead will connect TP3 to pin 1 on the CPC connector.

This is not the perfect solution, because pin 1 on the CPC connector is the Sound output, and being the SF3 made for the 4 SymbOS computers, this would cause noise when connected to a real CPC.

There is planned a revision of the SF3 with the 74LS245 chip included, is for that the Enterprise adapter has a detachable pcb scrap to make a dummy chip for the 245 socket.

24496-2

57
Hardware / Re: EPNET
« on: 2020.March.10. 15:57:27 »
Don't think that Jörn(Prodatron) is concentrated on SF3 development..... Hans(TMTLogic) is always waiting him to appear and finish the necessary SymbOS drivers.

I think that better we aid ourselves, or this development can last decades.... 

58
Hardware / Re: EPNET
« on: 2020.March.09. 15:21:13 »
I think this is the best place to put this.

http://www.symbos.de/appinfo.htm?00027

It can be that these drivers and sources can be tailored to make EPNet  and Simbiface3 NET drivers for SymbOS.

EPNet ones can be easier, because the chip used on the EP card is an evolution of the Wiznet W5100, already used on two of the MSX net cards.

59
Programming / Re: Questions about QUIGS programming.
« on: 2020.March.06. 18:44:53 »
It has not been easy....

Code: [Select]
// Quigs 1.01 Application for Symbos
// Name:
// Coder:
// Date / Version:

// Declare variables
Var Enter:Sheet   // a curious type of variable to store  graphics

// End declares

Function Main:Void()
// Main loop

EndF

Function Image1.Event:Void()

//Lets load the Sheet according to No. of colours
If Screen.Colour = 2 Then
//Its a 2 colour image so xxx.qs1
Enter.Load(App.Path+"Sheet1.qs1")   // these two sets of graphics are created automatically
Else
//Its a 4 colour image so xxx.qs2
Enter.Load(App.Path+"Sheet1.qs2")   // and have to go with the application.
EndIf

Ctrl.Image.Tile.Set Image1, Enter,0   // this command loads the file on the Image1 control
Ctrl.Refresh Image1       // this command rewrites the event.


EndF

Function Form1.Close.Event:Void()
Enter.Free   //releases memory at exit
EndF
Function Form1.Open.Event:Void()
Image1.Event       // this is necessary to launch the Image1 event just at opening the program.


Also, if you want to show a text, the space has to be bigger than the No. of characters:


60
Programming / Questions about QUIGS programming.
« on: 2020.March.05. 21:15:10 »
Tutus, can you put here your .qpf program? Maybe I can fix it.

 

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 185