Looking for SymbOS Quigs documentation

Page 7/8
1 | 2 | 3 | 4 | 5 | 6 | | 8

By edoz

Prophet (2392)

edoz's picture

03-09-2021, 21:51

AxelStone wrote:

Guys 2 questions about Network:
1.- Can I use local lookup daemon to test Network un case I add It ti my software?
2.- With the most recent firmware the Zemmix Neo and all FPGA clones support a WiFi module. It should be great to add this driver to SymbOS.

1. Yes. The local daemon is handling network traffic in SymboS as localhost. I used it a lot to make for example battleship and the snake game, by starting 2 applications at the same time (one as server and other as client) So i had the possibility to test network applications without having a real network in SymbOS. But for my Email client this was more difficult as i needed a email server for this as well. So most of the testing was using real hardware, wireshark and a lot of patience. However, we have some commandline tools for symshell that connect to a socket and can listen to the traffic as well. (So you can see what is going over the line). If you want to receive the quigs source of my email client i'm willing to send it to you but i want to keep that source private as the project is not finished.

2. I don't know the hardware and me and prodatron don't own it as well. (Trebmint doesn't have any hardware at all.. he is more or less a emulator freak) Does the hardware has an TCP stack? As symbOS does not have a software TCP stack onboard as it is using the hardware for this. SymbOS supports, Denyonet and GR8NET on MSX. And it does support M4 (Wifi) on the CPC. The sources are open for the network- daemon. So maybe someone with the hardware is willing to make it? Best i think is to use the M4 Wifi daemon as example, as this is based already on Wifi based hardware.
Here is the source, but you need someone with the hardware and knowledge of assembly as well (and have time for it)
Sources of network drivers SymbOS

By gflorez

Resident (41)

gflorez's picture

04-09-2021, 10:28

M4, even when it also works with a Chinese wifi module like the one supported now by MSX FPGAs, is based on CPC Rom libraries, not directly usable on MSX computers(or Enterprise).

It is easy to forget this fact... I often do it....

By ducasp

Champion (461)

ducasp's picture

05-09-2021, 01:00

gflorez wrote:

M4, even when it also works with a Chinese wifi module like the one supported now by MSX FPGAs, is based on CPC Rom libraries, not directly usable on MSX computers(or Enterprise).

It is easy to forget this fact... I often do it....

I don't think he is saying that you use it on a msx, but someone interested in making the ocm esp8266 interface and firmware I've created working on SymbOS could use the M4 daemon source code as a foundation to make the daemon for the esp8266 unapi firmware / uart interface OCM now has with use of an adapter. Seems like fair advice to me.

By gflorez

Resident (41)

gflorez's picture

05-09-2021, 01:49

Yes.... but no... Contrary to the MSX daemons, the M4 daemon makes use of the CPC libraries on Rom.

The M4 daemon approach is against the SymbOS Philosophy, but it was probably the only way for Jörn to make the M4 usable.

So, if you compare the different daemons code, you will see that the MSX ones access directly the hardware, but on the M4 daemon the Rom is allocated on memory and called, then the hardware is accessed indirectly by the CPC libraries.

Probably there is in some place a description of the hardware and ports used, then the wifi module could be managed directly.

By edoz

Prophet (2392)

edoz's picture

05-09-2021, 08:23

From my understanding it was not possible on the M4 to access the WiFi hardware directly from a hardware point of view as it was behind the rim. But in the end it doesn’t matter. The sources can be used as an example. As you can program directly to the chip as well. But then you need someone that knows how. Applications in SymbOS are talking to the daemon and this does the translation to hardware.

By ducasp

Champion (461)

ducasp's picture

07-09-2021, 17:21

gflorez wrote:

Yes.... but no... Contrary to the MSX daemons, the M4 daemon makes use of the CPC libraries on Rom.

The M4 daemon approach is against the SymbOS Philosophy, but it was probably the only way for Jörn to make the M4 usable.

So, if you compare the different daemons code, you will see that the MSX ones access directly the hardware, but on the M4 daemon the Rom is allocated on memory and called, then the hardware is accessed indirectly by the CPC libraries.

Probably there is in some place a description of the hardware and ports used, then the wifi module could be managed directly.

That would still be perfectly doable, well, the ESP8266 on OCM indeed has an UNAPI BIOS and that could be called as long as SymbOS allows for EXTBIO hooks/calls...That driver is not interrupt driven, so it should be fair as long as SymbOS allows it, that would make it even better as it would be a generic ROM-UNAPI Daemon for any device that follows TCP-IP UNAPI Tongue

Anyway, no matter what, someone needs to dig into the daemons, into the ESP8266 customized firmware documentation (I've made it available on my github), the sample UNAPI Drivers if any question remains (as the customized firmware implements UNAPI calls over serial communication) and adapt that to a SymbOS daemon. If the one for GR8NET, Denyonet or M4 is preferrable that would be up to the developer of that Daemon... No specific Wi-Fi stuff would be needed, as the UNAPI BIOS, even if it stays dormant and un-used after SymbOS boots, gives you the way to join a wireless network and configure the power (and audio noise on case of SM-X) saving features of it as well as the automatic clock setting. Wink

By ducasp

Champion (461)

ducasp's picture

08-09-2021, 00:30

I've glanced at the daemons code and in my opinion, except for Dns, porting the SM-X Wi-Fi interface could be something easy to achieve, the high level calls for tcp are similar to UNAPI in terms of parameters and responses, and it would make much more sense to start clean using the base of denyonet. M4 allows a Wi-Fi ssid configuration and connection strength response as well, UNAPI doesn't provide either one and the bios that is accessible through hitting a function key during boot allows setting this up, there is a provision to get the connection strength somehow in the firmware but not sure if it is worth the trouble (and anyway, it would be possible to add later both functionalities).

If I were to do it, my approach would be to use denyonet project as a base, no need for w5100 or slot functions, just wrap the functions daemon want to see (those are in the end of the denyonet specific daemon code). Should be quite simple in theory, would be fast, wouldn't give you the ssid set up through SymbOS or the signal strength indicator, but those could be part of a second version. The SM-X / OCM ESP8266 interface is really simple through IO and shouldn't be that difficult to be wrapped around to work as SymbOS expects

By AxelStone

Prophet (3055)

AxelStone's picture

18-09-2021, 21:31

Hello guys, one question, what is a Canvas control? I can't find examples of use.

Thanks.

By AxelStone

Prophet (3055)

AxelStone's picture

21-09-2021, 21:18

@Trebmint I think that there is a bug with ImageBox.Top.Get function or I don't understand how it works, I attach an image:

Position Y means where I clicked the Mouse, and Sprite Y means the ImageBox.Top.Get value. Acording to the info, the sprite is in the same Y position that pointer but as you can see it's bellow. With ImageBox.Left.Get it works fine.

Thanks!

By AxelStone

Prophet (3055)

AxelStone's picture

24-09-2021, 11:26

@Trebmint is there any way I can contact you directly? (let's say email). I'm using Quigs IDE and perhaps I can help you with testing it, I've found some issues that probably are bugs. I'm available to provide this kind of testing, since I'm doing a project with it.

Let me know!

Page 7/8
1 | 2 | 3 | 4 | 5 | 6 | | 8