Who's Online |
69 user(s) are online ( 33 user(s) are browsing Forums)
Members: 0
Guests: 69
more...
|
|
|
|
|
Re: Introducing Gabrielle - Xena's companion
|
|
Just popping in 
|
@jaokim Here the output from my X5000
X5000> md.w e0008000 8
e0008000: 2210 2210 2210 2210 2210 2210 2210 2210 “.”.”.”.”.”.”.”.
X5000> mw.w e0000000 1
X5000> md.w e0008000 8
e0008000: beef beef beef beef beef beef beef beef …………….
X5000> mw.w e0000000 2
X5000> md.w e0008000 8
e0008000: 2210 2210 2210 2210 2210 2210 2210 2210 “.”.”.”.”.”.”.”.
X5000> mw.w e0000000 4
X5000> md.w e0008000 8
e0008000: 0001 0001 0001 0001 0001 0001 0001 0001 …………….
X5000>
|
|
|
|
|
|
Re: Listen on scoket and for other signals (like CTRL-C)
|
Posted on: 2025/10/8 7:10
#2
|
Just popping in 
|
@OldFart
Personal taste. Even having got a CTRL-C, and something is present at the socket, you could let connect the client and immediately tell him something like "service will go away". Depends on the protocol / service you are about to to implement.
But the pasted code way copied/modified from a setup where the other signals were from other messages ports. So not necessary from a signal indication that the program should exit.
Max
|
|
|
|
|
|
Re: Listen on scoket and for other signals (like CTRL-C)
|
Posted on: 2025/10/7 5:59
#3
|
Just popping in 
|
@MigthyMax I figured it out by myself. If somebody wants to know how to do it. You can actually use ISocket->WaitSelect for implemneting a simple server like this (simplified, no error checking etc):
ISocket->bind( socket,(struct sockaddr *)&addr,sizeof(addr) );
ISocket->listen( socket,1 )
for( int loop = TRUE;loop; ) {
fd_set listenFds;
FD_ZERO( &listenFds );
FD_SET( socket,&listenFds );
printf("Listening.....\n");
ULONG signals = SIGBREAKF_CTRL_C;
int readyDescriptors = ISocket->WaitSelect( socket +1,&listenFds,NULL,NULL,NULL,&signals );
if( readyDescriptors == -1 ) {
printf( "Network Error.\n" );
loop = FALSE;
}
else {
if( ( signals & SIGBREAKF_CTRL_C ) == SIGBREAKF_CTRL_C ) {
printf( "Detected CTRL-C.\n" );
loop = FALSE;
}
if( FD_ISSET( socket,&listenFds ) ) {
int client = ISocket->accept( socket,NULL,NULL );
if( client != -1 ) {
printf("Client connected.\n");
ISocket->CloseSocket( client );
}
}
}
}
|
|
|
|
|
|
Listen on scoket and for other signals (like CTRL-C)
|
Posted on: 2025/10/6 14:39
#4
|
Just popping in 
|
Hi,
does anyone know how to listen on a server socket (ISocket-listen) and on the same time listen for other signals like CTRL-C.
I'm looking for something like ISocket->WaitSelect but for a server implementation.
regards
max
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/7/13 14:34
#5
|
Just popping in 
|
@All Here a public none expiring download link. Under Artifacts at the end of the page you can download a build performed by github.
|
|
|
|
|
|
Re: Amiga40 Germany
|
Posted on: 2025/7/9 18:11
#6
|
Just popping in 
|
@flash
I agree with walkero, too
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/7/6 13:57
#7
|
Just popping in 
|
@skynet
Sorry, currently I have to provide a link. A thought I succeeded with setting up a build job on github, but that was juts hopeful thinking of me.
I will come back in upcoming days with a new link for donwloading, If I forget it again, just repost here.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/7/6 11:20
#8
|
Just popping in 
|
@skynet I wrote some information about how to use etc at https://github.com/migthymax/pl2303.deviceI hope it is understandable, if not ask here any question and I will try to answer.
|
|
|
|
|
|
Re: Snork: New Tracing Tool for AmigaOS 4
|
Posted on: 2025/6/27 9:55
#9
|
Just popping in 
|
@msteed Quote: Of course, if the string pointer is invalid the function you're calling will probably cause a DSI itself as soon as you call it. Still, there's some value to Snork not causing the DSI, even if there's going to be one an instant later anyway. Or (another suggestion) Snork doesn't pass the invalid pointer but passes on a valid string like "DEADSTRING\0". Than at least no DSI , still the string could mess up other stuff. But still some additional steps before a potential crash.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/25 16:52
#10
|
Just popping in 
|
@SinanSam460
I see that your exec.library version is 54.69 ? Are on any beta stuff?
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/25 16:42
#11
|
Just popping in 
|
@sinisrus
Don't know the model but the serial chip is a FTDI (vendor ID 0x2341 and product ID 0x0043)
The arv toolchain can probably be cross compiled with clib4 maybe even easy.
@SinanSam460
Thanks
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/25 13:12
#12
|
Just popping in 
|
@all I uploaded the source on github. And now the the driver and source can be downloaded from github. @sinisrus Well my arduinos aren't pl2303 based, so this driver won't help reaching that goal.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/25 9:43
#13
|
Just popping in 
|
@SinanSam460
Nice to hear that it works. Can you give me again an update crash log? Maybe I can figure out the crash.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/23 9:07
#14
|
Just popping in 
|
@SinanSam460 I found time to investigate your logs. You have a variant of the pl2303 chip which is named HDX (resp. HDX clone). My isn't of that kind, but yours need special handling, which I now implemented. I don't now why unplugging your USB gadget triggers a crash, but I'm proved the unplug handling too, hoping that it avoids the crash at your setup. For all here is the latest version, if your are to late DM me.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/16 7:02
#15
|
Just popping in 
|
@tekmage
I don't think so, because the driver doesn't check for matching product and vendor id. So just editing the pl2303.fdclass file to have the product/vendor id of your usb gadget, the driver will tried the best to talk with it.
So having ENV variables will just add a an additional layer of complexity
BTW. I plan to release the source, because
* Everyone can take a loo and improve the code * There is no example for an USB driver, which again register another device in the system * An most of the work is based on open source, so it should be open source
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/15 16:23
#16
|
Just popping in 
|
@graff Even a solution for end of June, would be in Amiga time measurement an immeasurable of warp 20 
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/15 9:02
#17
|
Just popping in 
|
@graff
Hi Thomas Graff, I'm assume you are the author of the USB stack?
If so you might answer me the following question:
The driver is heavily bases/inspired on the linux driver, which supports a variety of usb device (product/vendor) combinations.
As long I understand it I need for each product/vendor combination a fdclass file? Is there a way to group them within a sub drawer or can a fdclass file contain multiples entries?
Max
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/15 8:49
#18
|
Just popping in 
|
@tekmage For that device you need an adopted pl2303.fdclass (It's a text file) Just change the VENDOR and PRODUCT entries os that the file content looks like this:
FUNCTIONDRIVER
NAME "Serial PL2303 Driver"
VENDOR 0x0557
PRODUCT 0x2008
TYPE FUNCTION
PRI 6
DRIVER "pl2303.usbfd"
With that file the driver should pick up your device and the than everything works as expected/hoped a device will be register in os with the name "pl2303.device".
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/12 14:50
#19
|
Just popping in 
|
@tekmage
For me it was the same, I think Term was hiding on its own Screen in background. So just toggle through the screens.
You can change the behavior of Term in the setting to let it open its window on a public screen, like the workbench.
|
|
|
|
|
|
Re: USB Driver for PL2303 serial adpater
|
Posted on: 2025/5/1 8:43
#20
|
Just popping in 
|
@jabirulo
I didn’t knew of that. Is there a documentation somewhere?
|
|
|
|
|
|