NLNetfound
/
dsendcomm
2
2
Fork 0
Código Incidencias 82 Pull Requests 0 Lanzamientos 5 Wiki Actividad
Etiquetas Hitos
Nueva incidencia

#74 Traces to JP2 and JP3 are wrong

Cerrada
abierta hace 4 años por Michael Schloh von Bennewitz · 1 comentarios
Michael Schloh von Bennewitz comentado hace 4 años

Traces to JP2 and JP3 are wrong

Problem environment

UART connections connect half duplex signals over crossed traces, meaning a host transmits over a TX trace connected to the RX trace of a device.

Steps to reproduce

  1. Observe the schematic design
  2. Search the JP2/JP3 connectors
  3. Observe UART_TX and GPIO14/TXD

Expected result

  • UART_RX connects with GPIO14/TXD.
  • UART_TX connects with GPIO15/RXD.

Actual result

  • UART_RX connects with GPIO15/RXD.
  • UART_TX connects with GPIO14/TXD.

Workaround

The jumper layout specifies a male header, allowing to cross the connection appropriately using breadboard female wires.

Severity level

This is high priority because we expect most users to use the serial connection extensively.

# Traces to JP2 and JP3 are wrong ## Problem environment UART connections connect half duplex signals over crossed traces, meaning a host transmits over a TX trace connected to the RX trace of a device. ## Steps to reproduce 1. Observe the schematic design 1. Search the JP2/JP3 connectors 1. Observe UART_TX and GPIO14/TXD ## Expected result * UART_RX connects with **GPIO14/TXD**. * **UART_TX** connects with GPIO15/RXD. ## Actual result * UART_RX connects with GPIO15/RXD. * **UART_TX** connects with **GPIO14/TXD**. ## Workaround The jumper layout specifies a male header, allowing to cross the connection appropriately using breadboard female wires. ## Severity level This is **high priority** because we expect most users to use the serial connection extensively.
Michael Schloh von Bennewitz ha añadido la etiqueta
bug
hace 4 años
Michael Schloh von Bennewitz ha añadido esto al hito Target platform regression testing hace 4 años ' issues.change_milestone_at=`modificó el hito de %!s(MISSING) a %!s(MISSING) %!s(MISSING)
Michael Schloh von Bennewitz comentado hace 4 años
Propietario

Resolved in 8e36a89.

Resolved in 8e36a89.
Inicie sesión para unirse a esta conversación.
Ninguna Rama/Etiqueta especificada
Ramas Etiquetas
Etiquetas
Limpiar etiquetas
bug
Something is not working derivative
Regarding a derived product duplicate
This issue or pull request already exists enhancement
New feature help wanted
Need some help invalid
Something is wrong question
More information is needed wontfix
This won't be fixed
Sin etiquetas
bug
derivative
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Limpiar Milestone
Sin Milestone
Target platform regression testing
Asignados
Limpiar asignados
No asignados
1 participantes
Fecha de vencimiento

Sin fecha de vencimiento.

Dependencias

Esta incidencia actualmente no tiene ninguna dependencia.

Escribir Vista previa
Cargando…
Cancelar
Guardar
Aún no existe contenido.
Eliminar la rama con el nombre '%!s(MISSING)'

Eliminar una rama es permanente. NO PUEDE deshacerse. ¿Continuar?

No
Sí