Name of the SERIAL App?

It looks like you may have a potential reason Philip might not be using the updated “test” version

SerialUSB doc file version 0.02.

SerialUSB-0.12 (01 Feb 2021)

Seems I pushed that send button too soon.

Another quirky HTTPS

Interesting, the Online Certificate Status Protocol check fails due to a timeout.
Revocation information OCSP OCSP: http://r3.o.lencr.org
Revocation status Validation error OCSP ERROR: Exception: connect timed out [http://r3.o.lencr.org]

Let’s Encrypt are usually pretty reliable, but that server? I’m used to seeing http://ocsp.int-x3.letsencrypt.org as the OCSP responder

Qualys SSL check <— Few bits to turn off

Seems I pushed that send button too soon.

Been there, done that, T-shirt in rag collection…

Looks like the iconbar HTTPS is a bit broken

Yes. It works with http:

SerialUSB-0.12 (01 Feb 2021)

You must be using the new one as SerialTerminal shows a SerialUSB device. The new module has a ‘d’ at the end of the help string like this

*help serialusb
==> Help on keyword SerialUSB
Module is: SerialUSB       0.12 (01 Feb 2021) d

Don’t seem to have the ability to send commands to the board though

I’m having problems sending via usb serial on windows.

Updated my Microbit V1.3b to Interface version 0249. Ran !SerialTerminal.

Escape codes removed
SerialUSB2#noblock;nohandshake;baud=115200;data=8;stop=1;noparity:
Transmit and Receive
Key echo off
Line ending LF
CDC Device, ARM, BBC micro:bit CMSIS-DAP

Using ‘MU’ as the access program was the only way to see the REPL on the Microbit. Then it is receive only. I may be mistaken, its been some time ago. My current Linux distro chokes when I try to run MU. I’ll be working that so I have some comparison data for the RISCOS experience.

Dug out a second Microbit V1.3B, updated the firmware, successfully accessed the REPL using screen /dev/ttyACM0 115200 on my Linux box.

Ran !SerialTerminal -echo and received the same output as the first Microbit.

I did learn (again) that the Microbit does not accept .py files. They must be .hex. Whereas the Pyboard will compile to bytecode from a .py file.

Module is: SerialUSB 0.12 (01 Feb 2021) d

Confirmed!

I’m having problems sending via usb serial on windows.

Putty?

Ok I got it working I created the python program below in the microbit app – I’m using the windows app which downloads the hex file directly to the microbit. If I then plug the microbit into riscos and run serialterminal, typing text and pressing return works – note the text you type isn’t echoed while typing.

ln = ""
serial.redirect_to_usb()
# serial.setBaudRate(BaudRate.BaudRate115200)
serial.write_line("Hello there")
while True:
    pause(100)
    serial.write_line("Enter text and press return")
    ln = serial.read_line()
    serial.write_line(ln)

The drag and drop of .hex files onto the Microbit using the filer seems to work well. Hopes are the the Pyboard will be seen by the filer and .py files can be created and transfered using RISCOS.

At present, I don’t have an offline compiler for the microbit so I am unable to try the program above. I can consistently connect to either the Pyboard or Microbit and the LED flashes with each keypress. I don’t get the >>> REPL prompt and the keyboard commands have no effect.

I’ll get another Pi computer up and running so I have an offline Microbit compiler.

Great work so far!

Here’s the hexfile to try.

Here’s the hexfile to try.

Works like a charm.

Is it time to move this version of !SerialTerminal to the default version?

Nature’s fury (snow storm) took out my internet connection yesterday so I don’t yet have MU running on a PI as I had planned. I’ll get back to that this afternoon/evening.
These are exciting times!

Ok.

I’ve updated SerialUSB to version 0.13 and the new SerialTerminal will just work there is no need to click on the module to load it. If you want to use the latest !SerialDev with the version of hearsay I posted earlier you will need to replace the SerialUSB module in !SerialDev (serialusb 0.12) with version 0.13 from the SerialUSB distribution. Hearsay will give you a linux terminal like display if you need it.

Regarding your other device it is virtually identical to microbit in USB terms except that the microbit has an extra HID interface. So I would expect it to work in exactly the same way. If the mass storage interface isn’t working I think you only hope is to see if you can upgrade the firmware on the device.

updated SerialUSB to version 0.13

I wrote a program to send accelerometer data streams using Print, in the Microbit code, to a serial terminal. Working beautifully.

Transmitting Control commands back to the board have no effect. Ctrl C, Ctrl D, Ctrl A . Single keypress ie: CRLF is OK. Glanced the object code file, didn’t see a lookup table. ASCII subset?

I’ve got my “Microbit Lab” up and running, I’ll write some code to see what I can break!

The Pyboard has upgraded firmware, the abscence of the HID interface is common among ALL of my microcontroller boards save for the Microbit. I still wonder about the Pi Pico. SOLD OUT (for now).

use the latest !SerialDev with the version of hearsay I posted earlier you will need to replace the SerialUSB module in !SerialDev

Still pretty new to shuffling things on RiscOS. I put HearSay in a folder by itself (unzipped). Copied SerialUSB into the modules folder where SerialDev resides.
HearSay complains. Huh?

> I’ve updated SerialUSB to version 0.13

Any chance of adding support for Arduino? This may be difficult to accomplish:

“Why was the Atmega16U2 used on the Arduino UNO as a USB to Serial converter”

https://arduino.stackexchange.com/questions/49168/why-was-the-atmega16u2-used-on-the-arduino-uno-as-a-usb-to-serial-converter

Transmitting Control commands back to the board have no effect. Ctrl C, Ctrl D, Ctrl A

If you are referring to Colin’s SerialTerminal here, It filters the keyboard input. You can tweak and compile the supplied source with the free GCC should you not have the DDE.
Hearsay or Connector is probably what you want if you get escape chars from the device.
SetialUSB module like all modules becomes system wide (globally used) It would have to be loaded to replace any existing SerialUSB module instance.
Maybe
*help module SerialUSB
would show any change.
There are also more direct USB queries I think.
!SerialDev in this case is related to Hearsay app resources, confusingly the name is used in Boot resources also.

You only need to put the module SerialUSB into !Hearsay you do this by holding down the shift key then clicking !Hearsay then opening modules folder replace with new module.

> I’ve updated SerialUSB to version 0.13
Any chance of adding support for Arduino? This may be difficult to accomplish:

SerialUSB already supports arduino – at least it works with my arduino duo

I’ve put the modified version of Hearsay which works with SerialUSB on my web site (Hearsay.zip) for those who are interested.

!SerialDev should be updated to support SerialUSB 0.13 soon.

> SerialUSB already supports arduino – at least it works with my arduino duo

Could you please confirm: Does it work with the default USB/serial port for Serial.print() – which uses ATMEL 16U2 as USB/serial converter, or only with the 2nd USB/serial port with CDC – which all other Arduino like Uno – do not have?

I do not mean talking to the bootloader and uploading programs – just for reading the output of Serial.print()

“The Arduino Due has two USB ports available. The Native USB port (which supports CDC serial communication using the SerialUSB object) is connected directly to the SAM3X MCU. The other USB port is the Programming port. It is connected to an ATMEL 16U2 which acts as a USB-to-Serial converter. This Programming port is the default for uploading sketches and communicating with the Arduino”

at least it works with my arduino duo

That’s my mistake I have an arduino uno.

It uses Atmel Mega 16u2 and appears as a CDC device.

If I program it with the program below on a PC. You can plug it into riscos and run !SerialTerminal which comes with SerialUSB and you can type and the characters are echoed – is that what you mean?.

If there is something more that doesn’t work on your arduino if you send me the descriptors for the device I’ll have a look to see if I can do anything.

To get the descriptors download !USBDescriptors run the program and send the descriptors for your Arduino Due to the email address on the ftpc page

void setup()
{
  Serial.begin(115200);
  while (!Serial) {}
  Serial.write("\r\nSerialTest: Type something and it should echo\r\n>");

}

void loop() 
{
  if (Serial.available()) Serial.write(Serial.read());
}

Hearsay or Connector is probably what you want if you get escape chars from the device.

I have the new HearSay, initial testing has been unsuccessful to Recieve data stream from USB device. Have to correlate the choices to this hardware setup. ANSI? VT100? Will continue to test.
Transmitting control characters to the board is essential to using the REPL.

I look forward to having other microcontroller boards, without the HID interface, working as the Microbit does. When the Pyboard, and its cousins, can be seen in the Filer, RiscOS will have become an official alternative development platform for the Internet Of Things (IoT). I’ll do some testing with TL1302 spec.

If you got hearsay from my website you don’t need to do anything to it to get it to work. ANSI/ VT100 etc don’t matter

1) Ensure your program is 115200 baud

2) !SerialDev is seen – Ideally SerialDev should be updated to use SerialUSB0.13 but failing that Ensure you have run SerialUSB 0.13 running

3) Plug in device – if it is not already plugged in

4) Run Hearsay.

If a SerialUSB device is detected Hearsay will appear with ‘SerialUSBn’ under it. If no SerialUSB device is detected Hearsay will appear with ‘Serialn’

If you have more than 1 SerialUSB devices plugged in just keep running Hearsay until it is using the device you want then quit the versions you have run that you don’t want.

Note pressing return sends ‘\r’ and not ‘\n’ so if your program is expecting ‘\n’ you need to press <ctrl> J

Ensure you have run SerialUSB 0.13 running
3) Plug in device – if it is not already plugged in
4) Run Hearsay.

Check

If a SerialUSB device is detected Hearsay will appear with ‘SerialUSBn’ under it. If no SerialUSB device is detected Hearsay will appear with ‘Serialn’

HearSay reports “Serial1”.

If you have more than 1 SerialUSB devices plugged in just keep running Hearsay until it is using the device you want then quit the versions you have run that you don’t want.

Keyboard and mouse are USB but the Microbit is the only USB device that Serial Terminal sees.
If I try to run another instance of HearSay, I get an error, type=3.

While HearSay is still on the screen, I run !SerialTerminal. It works fine.

Note pressing return sends ‘\r’ and not ‘\n’ so if your program is expecting ‘\n’ you need to press J

IN !SerialTerminal:
After pressing ^B “Linebuffer on”.
^Y pastes clipboard content twice.
Enter jumps down 3 lines. ^J jumps down 3 lines. ^M jumps down 3 lines.
No other Control key combo does anything or flickers LED.

IN HearSay, No keypress or combo keypress has any effect.

I think it might be important to mention that I am using US keyboard layout.
Identified these Control Characters in !SerialTerminal.
“^|” (Cntl Pipe) presents a help menu: "Help on C=Command, F=Function, V=Variable, K=Key, M=Mode, D=Docs, Z=Zap
“^]” (Cntl Right Bracket) Inserts Line Numbers.

Experimenting with ALT Numpad characters.