Name of the SERIAL App?

Check

What about !SerialDev (block drivers) You need the latest !SerialDev from xat. If you don’t see SerialUSBn when running hearsay either SerialUSB 0.13 is not loaded or !SerialDev has not been seen.

I think it might be important to mention that I am using US keyboard layout.

This isn’t a problem in getting Hearsay working. Only the device, SerialUSB0.13, !SerialDev and!Hearsay are required.

If you have !SerialTerminal showing a window to the usb device then Hearsay will ignore it as it is already in use. In that case running hearsay will show ‘Serialn’.

What about !SerialDev (block drivers) You need the latest !SerialDev from xat.

I have SerialUSB 0.13 and HearSay from your website. !SerialDev was an empty file included with the HearSay I deleted. There is no !SerialDev with this release of HearSay.

when running hearsay either SerialUSB 0.13 is not loaded or !SerialDev has not been seen.

I double-click on SerialUSB prior to running HearSay but it does not see any USB device.
There is no !SerialDev in the HearSay folder with the newest release.

f you have !SerialTerminal showing a window to the usb device then Hearsay will ignore it as it is already in use. In that case running hearsay will show ‘Serialn’.

Testing with HearSay failed, only then did I run !SerialTerminal, with HearSay on the screen, to see if the device was taken by HearSay. It wasn’t.

Once I run HearSay, I cannot open it again until after a reboot.

!SerialDev is available at xat here. Just download the blockdrivers

I re-downloaded HearSay from the store. Moved !SerialDev from the archive into a directory containing the newest HearSay. This !SerialDev is not empty, It contains Internal32 and Telnet. Each of the folders contain a file named Driver.
Neither the new !HearSay or the restored !SerialDev have a file type set.
I double click USBSerial, Run HearSay. No USB device found, “Serial1”.

:-)

Hearsay from the store doesn’t work.

Hearsay and SerialUSB from here

!SerialDev from here

!SerialDev will contain SerialUSB 0.13 in the future but he hasn’t released it yet so in the meantime just double click on SerialUSB 0.13 so that it works with your device for now.

It’s UP, It’s Running. This is really wonderful. I’m able to access the REPL on the Microbit AND the Pyboard. I’ll be testing some others as Well.

Now I need to figure HOWTO get .py files from RiscOS Python or StrongED to the Pyboard and we’re all in business.

Much appreciation for your hard work and perseverance.

A Serial Icon on the IconBar would be handy – for a file to be dropped on from StrongEd.

It might even be possible to add an icon to StrongED’s toolbar (in Python mode probably) to start the file transfer. Something along the line of:

SaveText Run(<command to start transfer>)

A Serial Icon on the IconBar would be handy – for a file to be dropped on from StrongEd.
SaveText Run()

Indeed this would be handy. StrongED could offer setting the !SerialUSB device as the cwd. Isn’t EVERYTHING a file on RiscOS?
I’ve been trying to get cut and paste to work with the RAW repl but so far no luck.

Because the Microbit shows up as a drive, it’s a cinch to get programs on it. The “other” boards do not mount as a flashdrive, as they should, so writing to other than the repl is still an obstacle.

A good work-around for the Pyboard is to save the .py file to an SD card as main.py. When inserted into the Pyboard and powered on, the program runs. This works for any 8266, ESP32 and STM32 variant that has a SD card slot either on-board or SPI interface.

This is really good news for microcontroller fans. RiscOS can now be used in support of the modern IoT hobby/market. It is not, however, for the faint of heart at this point in time.

I’ll be investigating the feasability of micropython emulation by creating classes for use with the RiscOS Python implementation.

Microbit does not include a byte code compiler on-chip, porting the uflash utility from linux may be possible. Until then, Microbit will need to be compiled online or with MU.

I’ve done some testing with different microcontroller boards. As expected, none will mount as a flashdrive.

I have two boards that are quite easy to connect to my router with WiFi and create a socket and buffer file but, I don’t yet know how to create a socket for filecore. “I can send files to it but they can’t get through it!”

The ESP32 WROOM and the WEMOS D1 mini pro will make nice additions to the pool of hardware RiscOS supports.