Hearsay

Error block: 80000001 Internal error: abort on instruction fetch at &00000000
R0 = 00000011
R1 = ffffffff
R2 = 00000000
R3 = 00000000
R4 = 000404f0
R5 = 000007d0
R6 = 00000034
R7 = 00040a44
R8 = 00000000
R9 = 00045228
R10 = 0005c238
R11 = 0005cec8
R12 = 0005ce6c
R13 = 0005ce70
R14 = 0000efc0
R15 = 00000004
CPSR = 60000110
R13_usr = 0005ce70
R14_usr = 0000efc0
R13_svc = fa208000
R14_svc = 0003af38
SPSR_svc = 60000110
R13_irq = fa102000
R14_irq = 60000113
SPSR_irq = 60000113
R13_abt = fa301fa8
R14_abt = 00000004
SPSR_abt = 60000110
R13_und = fa402000
R14_und = fc174eac
SPSR_und = 20000110
OSMem16: 2 = fa100000, 00002000, 00002000
OSMem16: 3 = fa200000, 00008000, 00008000
OSMem16: 4 = fa300000, 00002000, 00002000
OSMem16: 5 = fa400000, 00002000, 00002000
Memory: fa100000 - fa102000
Memory: fa200000 - fa208000
Memory: fa300000 - fa302000
Memory: fa400000 - fa402000
Memory: ffff0108 - ffff010c
OSRSI6: 69 = ffff0108

R15 = 00000004 is system workspace
R14_usr = 0000efc0 = +6fc0 in application memory = driver_load +b4

USR stack:
0005ce70 : 69726553 :
0005ce74 : 65446c61 :
0005ce78 : 6f4d3a76 :
0005ce7c : 656c7564 :
0005ce80 : 6e492e73 :
0005ce84 : 6e726574 :
0005ce88 : 43506c61 :
0005ce8c : 6972442e :
0005ce90 : 00726576 :
0005ce94 : 0000cd14 :
0005ce98 : 00063284 :
0005ce9c : 0000000c :
0005cea0 : 0005cec8 :
0005cea4 : 0005ceb0 :
0005cea8 : 000455e8 :
0005ceac : 00045724 : - R0
0005ceb0 : 00040794 : | R4
0005ceb4 : 00040ab8 : | R5
0005ceb8 : 000455e8 : | R7
0005cebc : 0005cef0 : | R11
0005cec0 : 0005cecc : | R12
0005cec4 : 0002a334 : | R14: 0002a334
         :          : | = +22334 in application memory
         :          : | = claim_serial_port +4c
0005cec8 : 0000ef18 : | APCS function: 0000ef10
         :          : | = +6f10 in application memory
         :          : | = driver_load +4
0005cecc : 00040ab8 : | R4
0005ced0 : 0003feb8 : | R5
0005ced4 : 000455e8 : | R6
0005ced8 : 0000000f : | R7
0005cedc : 00000000 : | R8
0005cee0 : 00045228 : | R9
0005cee4 : 0005cf7c : | R11
0005cee8 : 0005cef4 : | R12                                                                                 - R4
0005ceec : 0000b964 : | R14: 0000b964                                                                       | R5
         :          : | = +3964 in application memory                                                       | 
         :          : | = main +8b4                                                                         | 
0005cef0 : 0002a2f4 : | APCS function: 0002a2ec                                                             | R6
         :          : | = +222ec in application memory                                                      | 
         :          : | = claim_serial_port +4                                                              | 
0005cef4 : fc177a38 : |                                          - Return to fc177a38?                      | R7
         :          : |                                          | = SharedCLibrary +3c8c                   |

I have no aborts with hearsay with @setserialdev(“SerialUSB”) with the new !serialdev

I get a Hearsay throwback window with:

Errors in file: ADFS::Hit75.$.Comms.SerialDev

    Line  Type           Description
    290  Serious error  Wrong number of arguments

I had setserialdev(“SerialUSB”,0) before this.
Playing around with this for a bit seems to have stopped the freeze up though.
Maybe I should ignore the error seeing as you haven’t been using the ,0

a quick sanity check

Argh! You can’t say that in 2020!

Social Justice Warriors might feign offence on behalf of those who are gaga nuts bonkers batshit*t crazy as a soup sandwich.

With respect to Connector… how big is the driver, and how much space does Connector allocate?

Ronald. My apologies it should be setserialdev("SerialUSB",0) in hearsay. The error was because the ,0 was missing.

Rick it dynamically allocates the memory. It’s failing with the InternalPC driver. I’ve checked a pandaboard now that works ok too. So it’s just the pi4 and iyonix that fail armx6 and pandaboard work. iyonix is an old rom pi4 newish. Hearsay no problem on all machines. There are no choices saved for connector on any machine so it’s just using the default driver. Fails with ROOL’s version of Connector and the one I compiled.

The problem appears to be in the Desk Library which is unfortunate as it is binary only.

it should be setserialdev(“SerialUSB”,0) in hearsay

yes thats what you said originally in the thread. No joy with Hearsay/SerialUSB or Connector/SerialUSB here, but I connected the same device (pizero) through Internal32,0 on my Iyonix and both Hearsay and Connector worked quite easily,
so from my point of view it is just the SerialUSB stuff that is the problem, not sure why you are concerned with Connector, thats all.

It crashes for me without serialusb on the machine.

If you fetch SerialUSB double click on the SerialUSB module, double click on !terminal does it work/crash?

I should know better – is the SerialUSB thing a problem with getting the new version loaded. Maybe the new !SerialDev needs double clicking, before running Hearsay etc.

DeskLib – seems sources are available – https://www.riscos.info/index.php/DeskLib#Source

Ronald. I’ve tried a piB+ and that works fine. As David pointed out the problem may be you not loading the new !serialdev. Looking at the run file if BlockDriver is already running double clicking on !serialdev will not load the new version.

David. According to the ROOL sources ReadMe

In accordance with the terms of the Desk licence, RISC OS Open is
distributing an unmodified version of the public Desk library, even though
the head RISC OS licence holder has traditionally used a customised version
of the library. For compatibility with this customised version, the files
installed in the Export directory retain the directory structure of the
customised version. This conversion is scripted so as to simplify ongoing
maintenance, and is performed during the export-hdrs and export-libs build
phases.

Desk is currently moderated by Philip Ludlam <philip@philipnet.com> and the
latest version of Desk can be obtained from
http://www.philipnet.com/project/desk.

The problem appears to be in the Desk Library which is unfortunate as it is binary only. […] DeskLib – seems sources are available

DeskLib isn’t Desk, unfortunately. The two parted ways back in the early 1990s, IIRC.

If you want to try building with a more recently compiled DDE oriented DeskLib, look at http://heyrick.ddns.net/desklib/

If it’s actually using Desk, and not DeskLib, you’re probably out of luck unless you can rebuild from source, as few people made the transition…

If you fetch SerialUSB double click on the SerialUSB module, double click on !terminal does it work

Iyonix, yes though I had to run your terminal a second time /after/ Raspbian had booted. Could be just a Raspbian thing.
No crashes
I did notice myself early on that !SerialDev doesnt reload when clicking, this behaviour could be changed without breaking anything, and it /is/ what you would expect.

Thanks Rick but it’s using Desk.

I’m back in the game. Despite DDT stopping when it met a Desk function the problem was that Connector defaults to using the InternalPC serialdev which is 26bit. So I’ve defaulted to Internal32 – that crashed but I found the offending 26bit instruction. Not many serialdevs work on the Pi4 but Internal32 and SerialUSB do for me. For some reason the Dummy SerialDev also fails.

Anyway back to the beginning would anyone like to try ConnectorTest. Hopefully it works now. If you are already using SerialDev double clicking on the attached version will now load the updated driver. The SerialUSB module is in !SerialDev and is loaded by the SerialDev driver.

I’ve changed the default settings to be more useful so if you need 115200 8N1 it should work straight away. If you have saved Connector settings those will be used but if a driver other than InternalPC or SerialUSB is loaded it may well crash.

but if a driver other than InternalPC or SerialUSB is loaded it may well crash.

This is a solved problem. Connector needs to be updated to reject drivers that aren’t 32 bit compliant on 32 bit systems.
[probably Hearsay too…]

anyone like to try ConnectorTest.

Iyonix -works well, you probably know about the slight behaviour difference of the choices save button not closing the window. OK is of course doing the job though. It seems to have also made the sun shine for the first time in weeks, so will have to put back trying it on the pi zero til later.
Edit: PiZero was good with !connector and !Hearsay worked well too.
It looks like to save speed settings in Hearsay the AutoRun.!Config can be editted manually.
Going back to the Iyonix I had problems with Hearsay, even as far as making Connector error on loading the driver.
A new copy of Hearsay cleared up the problem, The corrupted copy I was using also accounts for my previous reported problems while others had Hearsay working OK.
So all good now, except for the minor settings saving quirks.

Ronald – I’m sure there is something to click on in Hearsay to save the configuration (AutoRun.!Config). I don’t have a copy here so I can’t say more. We used to worry about configuration files and status files. Configuration was something global like your modem type. Status was things for the system you were calling. There would be many different systems one would call.

I’m sure there is something to click on in Hearsay to save the configuration

Unfortunately Hearsay has two ways of saving its configuration. One obvious, one less so.

• Terminal type, modem driver, printer…
  • Iconbar menu → Choices.
  • Edit as you see fit.
  • Click on “Save”.

• Terminal setup, serial speed, word format, screen size, echo…basically everything else.
  • Set it all up as you desire in Hearsay’s menus.
  • Menu → Script → Save as default

Anyone like to try Connector-1_09_01

I’ve added special character set mappings and it now converts unicode back to the character set connector uses – at least for the characters I found.

So line drawing works when connected to raspian or armbian (one uses unicode the other special characters). tmux works, though of limited use on a small screen, raspi-config and armbian config both work.

Menu → Script → Save as default

Sorry, my fault, I didn’t look at that one.
Both Hearsay and Connector wont do anything with SerialUSB settings/initalising unless the actual USB device is plugged in. Connector will respond with ‘error intilialising driver’ at startup, Hearsay (more silently) has unstuck speed settings, that wont respond to changes.

raspi-config and armbian config both work.

My raspian is showing en-GB-utf8 in the LANG and vt102, however I get multiple characters instead of lines.
Hearsay replaces both vert and horiz lines with a single lower case b, so is a bit tidier.
Both would be useable.

It is possible to start Hearsay with an argument from !Launcher, and by changing the system variable of Hearsay$Library in the !Run file to suit the argument. eg ‘!Hearsay USB0’
and

Set Hearsay$Library <Hearsay$Dir>.Library

If “%0” = “USB0” Then Set Hearsay$Library <Hearsay$Dir>.LibUSB0

Just use the ANSI setting in Connector. I have found that Alsamixer uses a different method of switching special graphics which doesn’t work in 1.19.01 which I’ve now fixed.

There is a new version of !SerialDev on the xat website. Your findings with no USB device is normal Connector doesn’t dynamically detect devices and will do nothing if there is no serialusb devices and it is configured for SerialUSB. Neither does it allow you to select between SerialUSB devices.

My intention is not to alter the interface to connector but just get it usable so I can use it as a serial terminal from RISC OS so I can use git/nano from the RISC OS desktop.

What are you connecting too? A modem! Are there any phone BBS left – Arcade ?

What is the last version of ArcBBS – is it downloadable?

Does using a USBSerial lead help isolate your computer from the phone line?

I’m just connecting to Linux on an orangepipc or pi on my desktop from my armx6 using a null modem cable. Connector has never worked for me so I decided to do something about it and with the help of Paul at Xat I have serialdevs working with SerialUSB and connector not crashing when I try to use it.

The dialup interface just gets in the way. Luckily it can mostly be configured away except if you want to change what the function keys send in which case you need to use the telephone book.

Just use the ANSI setting in Connector.

That’s better, do you get 3-4 characters cropped down the right side?

What is the last version of ArcBBS – is it downloadable?