!Connector problems on Pi 3

Hello,

I am trying to use !Connector to do a null modem connection from Pi 3 to PC

First problem: Where to get the BlockDrivers? In the link provided by ROOL the ZIP files are no longer there.

https://www.riscosopen.org/news/articles/2016/04/06/get-connected-with-rool

Second problem: I got !SerialDev from Hearsay 2.24 and get the message “Cannot find block driver InternalPC loading Internal32 instead” Is Internal32 o.k.?

http://www.davidpilling.net/hearsay.html

Third problem: !Connector then starts and I can open a 115200 baud communication. Text from PC is received in !Connector but no sent text appears on the PC. It is not a connection problem: I tried with Raspbian and it is working.

Thanks
Lothar

The BlockDriver zip on archive.org seems to work. No idea about your other questions.

xat have reorganised the site¹ if you go back to the root and navigate down the new structure, you get to April 2017 Blockdrivers

Good news: !Connector is now working. The third problem with “no sent text appears on the PC” was my fault: In !Connector “hardware handshake” is the default and I had not set it to “no flow control”

And bad news: Has anyone tested the BlockDrivers examples on any Pi?

Examples.Example gives “Syntax error” in FNd

After fixing this obvious it gives “SWI &2B returned a bad error pointer”

Examples.loopback3 gives “SWI not known”

The third problem with “no sent text appears on the PC” was my fault: In !Connector “hardware handshake” is the default and I had not set it to “no flow control”

and that folks is an example of why it makes a difference when a serial port (like on the Beagle, Pi and iMX6) has only some pins connected rather than all pins connected (like on the Titanium from Elesar) – it’s OK provided you know and can configure the software to not require hardware responses.

Examples.loopback3 gives “SWI not known”

I’ve lost track of the number of times I’ve seen messages like that when the simple inclusion of
ON ERROR PRINT REPORT$+" at "+STR$(ERL) : END
right at the start gives a better, more helpful, set of error messages.

If you feedback the info to XAT then perhaps they can provide a working example for use on a Pi.

If you feedback the info to XAT then perhaps they can provide a working example for use on a Pi.

I pointed out that mistake in the examples to Paul at XAT on 18-Dec-2015. If you replace

DEFFNd(A%,B%,C%,D%)
   CALL driver TO A%
=A%

DEFFNd(A%,B%,C%,D%)
=USR driver

Try to use !PPPWart and !PPPWahl from the download area www.gag.de. I use it any years before. Maybe it works.

> Examples.Example gives “Syntax error” in FNd
> =USR driver

Now with the Example driver “sp_dualpc” init gives “undefined instruction”. If I change to the new driver “internal32” init gives some error number.

> Examples.loopback3 gives “SWI not known”

The unknown SWI is “SPSerial_Control” most likely from “sp_dualpc” but as said this does not load on a Pi 3

> feedback the info to XAT

I will try that also. In parallel I shall take a look at the !Connector source: how they are calling the block drivers. And continue work on the direct UART hardware programming:

https://www.riscosopen.org/forum/forums/2/topics/9265

> If I change to the new driver “internal32” init gives some error number

Fixed: “internal32” requires registering with the “BlkDrv” module before init:

J%=FNd(DRIVER_INITIALISE,-1,0,0) J%=FNd(DRIVER_CLOSEDOWN,com%,0,0) J%=FNd(DRIVER_INITIALISE,com%,0,0)