09-09-2021, 11:45 PM
Thanks for the response. No luck so far.
- I have connected 3 different serial console gadgets; 2 with the FT232RL chip and another with the CH340 chip:
Voltage set to 3.3V, Serial port set to 115200 baud, 8N1
GND -> PI-2 GPIO pin 6 (GND on baseboard schematic)
RXD -> PI-2 GPIO pin 8 (UART_TXD on baseboard schematic)
TXD -> PI-2 GPIO pin 10 (UART_RXD on baseboard schematic)
If I hit keys on my terminal, the txd light on the serial gadget lights up. I have never ever seen the rxd led light up so it doesn't seem like there is a console here.
- The board schematic says that GPIO pins 8/10 are connected to UART6, which corresponds to pins 35/75 on the SOEDGE connector.
On the other hand SOEDGE pins 33/34 are CONSOLE_RX/CONSOLE_TX (in the pin assignment spreadsheet) and UART2_RX/TX in the schematic.
I do see UART2 on pins 6/8 of the PI-5 bus connector but plugging the serial gadget in here doesn't give any signal either.
On the Pine64 boards, the console is UART0 but I don't see UART0 pins on the SOEDGE baseboard schematic.
Is the SOEDGE console supposed to work or was it never tested? Does the kernel build need to be reconfigured to put the console on a different UART?
- When I boot up with a network cable, I do not see a new MAC address with an ssh listener.
What vendor prefix should I expect to see on the MAC address?
Also without a console, I'm reduced to using nmap scans to try to find the SOEDGE on my LAN.
It's frustrating that Pine64 have not provided the most basic documentation on how to determine if the SOEDGE boards are working or defective.
- I have connected 3 different serial console gadgets; 2 with the FT232RL chip and another with the CH340 chip:
Voltage set to 3.3V, Serial port set to 115200 baud, 8N1
GND -> PI-2 GPIO pin 6 (GND on baseboard schematic)
RXD -> PI-2 GPIO pin 8 (UART_TXD on baseboard schematic)
TXD -> PI-2 GPIO pin 10 (UART_RXD on baseboard schematic)
If I hit keys on my terminal, the txd light on the serial gadget lights up. I have never ever seen the rxd led light up so it doesn't seem like there is a console here.
- The board schematic says that GPIO pins 8/10 are connected to UART6, which corresponds to pins 35/75 on the SOEDGE connector.
On the other hand SOEDGE pins 33/34 are CONSOLE_RX/CONSOLE_TX (in the pin assignment spreadsheet) and UART2_RX/TX in the schematic.
I do see UART2 on pins 6/8 of the PI-5 bus connector but plugging the serial gadget in here doesn't give any signal either.
On the Pine64 boards, the console is UART0 but I don't see UART0 pins on the SOEDGE baseboard schematic.
Is the SOEDGE console supposed to work or was it never tested? Does the kernel build need to be reconfigured to put the console on a different UART?
- When I boot up with a network cable, I do not see a new MAC address with an ssh listener.
What vendor prefix should I expect to see on the MAC address?
Also without a console, I'm reduced to using nmap scans to try to find the SOEDGE on my LAN.
It's frustrating that Pine64 have not provided the most basic documentation on how to determine if the SOEDGE boards are working or defective.