Is it possible to steer the fischertechnik C64 robot interface via a modern USB port? - interface

I still have the fischertechnik computing interface 30566.
Is it possible to steer this interface via a modern USB port (instead of the C64 userport)?
I know there are adapters for turning USB into 5V TTL. Or do I need to have RS-232 in between?
And then?

Related

How to send data from STM32 USB port to Raspberry PI USB port?

I want to send data through USB between STM32 and Raspberry Pi. I don't want to use USB to Serial convertor, but instead have a actual USB Connection (maybe CDC class). I have to send data at high rate (Full speed). Please guide on how to achieve this?
A USB-serial connector is simply a microcontroller implementing a USB CDC/ACM virtual COM port and bridging to a UART which you would connect to a microcontroller's UART interface.
In your case you can simply implement the CDC/ACM directly on the STM32 using either of its USB device controller peripherals (USB support varies depending on the specific device https://www.st.com/resource/en/application_note/dm00296349-usb-hardware-and-pcb-guidelines-using-stm32-mcus-stmicroelectronics.pdf).
How you actually implement that will depend on what specific part, and what library or framework ecosystem you are using (e.g. SPL, CubeMX, Mbed). There are reference implementations, examples, drivers and libraries for all of these.
Your milage may vary, but I have measured ST's own USB library and example CDC/ACM virtual COM for STM32F1xx on a 72MHz MCU achieving 700kbits/s. Note that the performance is independent of the baud rate you might set on the host when you open the he VCP. Setting the baud rate simply sends a control packet to the device that can be used to set the baud rate of a UART in bridging applications. In your case such control packets can be ignored. There are similar packets for modem control signals such as DTR, RTS, CTS and RI, which you might choose to us for flow control or other signalling.

Do I need a level converter for Raspberry Pi and STM32 to communicate via GPIO(UART) port?

I want to connect an STM32F407 Discovery board with a Raspberry Pi 4 Model B.
And I want to use UART as communication so I plan to use PD5&6 on STM32 and Pin8&10 on RPi. But after looking up online it says that the voltage of a STM32 port is 5V and RPi is 3.3V, so it seems that I need a level converter between them?
And there are also some articles says that not all the STM32 port are 5V, some are 3.3V. But I cannot find any of that information in the datasheet. Can anyone tell me where can I find these information?
Thank you very much ~ ~
The STM32 uses 3.3V as well. But it's 5V tolerant.
Just go ahead and connect them. There is no voltage difference.
You should have a look at the reference manual for that discovery board. It is here: STM32F407 Reference Manual.
There should be no issue connecting UARTs between those boards. Just remember to connect the TX from one to the RX of the other and vice versa. You can also use the CTS/RTS for flow control, but that isn't necessary as long as you are using baud rates of 115200 or slower.
Something else that I would recommended is to power the Raspberry Pi from the Discovery board. There should be pins for suitable power on the discovery. This is important because it gets both boards using the same power and ground so that the UART logic levels are consistent between the two. This may not be necessary, but I have had issues trying to connect two Nucleo boards SPI busses together if I didn't power one board from the other.

Why Adaptive Autosar ECU use only Ethernet Switch for connection and why not Ethernet Port directly

I have recently come across Adaptive AutoSAR, I see all the Domain Controller/ECUs on the Adaptive side uses Ethernet Switch port to connect to other ECUs or Gateways. I know Switch has many features, but Could you please explain
1. Can we use inbuilt Ethernet Ports for doing the same functionality. or
2. What can the Switch provide which Ethernet Port doesn't.
Unlike CAN and other communication interfaces, SOC could not direct connect by Ethernet port interfaces. A second-layer switch should be used to be divided the network into different collision domains.

rs232 to ethernet converter connection issue with Atmel board

we are doing a project for receiving data from a device using a RS232 to ethernet converter (gridconnect net 232+) onto to a Atmel board. When we connect the converter to the PC, we are getting the output but not when connected to the microcontroller board. We need to know if there has to be some network confirguration to be done on the converter in order to receive it on the microcontroller.
Thanks !
I haven't worked with that board or device, but with any RS-232 communication channel you should check that all RS-232 parameters are set up correctly on both sides. Databits, stopbits, parity settings, etc. Even one setting being off will completely stop RS-232 communications.
Once that is done, I'd hook up a terminal emulator of your choice to simulate the microcontroller side and make sure that you're getting the right traffic from the Ethernet side. You might get lucky at that point and everything might start working. ;)

ESP8266 as a internet interface (access point)

I made some experiments with this amazing module. Now I'm trying to level up my project so I connected it to my Raspberry Pi via UART.
I'm able to send AT commands to make simple connections like I do on my Arduino. How can Linux "see" it like a real WLAN0 interface?
I'd like to use the ESP8266 as an access point to surf the web (maybe bridging the ethernet cable interface).
Is it possible?
No, you can't (easily) make the ESP8266 a true WiFi device for Linux. Although projects like this one here have figured out how to put the device into an ESP8089 mode to use it as a true WLAN interface, it requires modifying the module itself.
You can, however, use the device's AT API to connect to the internet through a UART and send any arbitrary data, or develop your own firmware to pass data back and forth to a server with the ESP8266 - None of these though would allow a seamless TCP connection like an actual WiFi card would, however.