quicr / hactar

Hardware design for test device

QuicR

THiS REPO IS NOT UNDER ACTIVE DEVELOPMENT

hactar's Issues

Track down improper copy and move semantics being invoked with Vector and Packet

Current Behaviour: Packets in the UI are being copied between vectors instead of moved.

Expected Behaviour: All packets should be moved between vectors

Hactar Hack Plan - First Chat Message

Let's pick a task and assign name so to avoid duplication

• Conditionally compile picoquic code - Suhas
• Make Net Code build with libquicr latest (again) - Suhas
• Bring in numero_uri as esp component - Suhas
• Integrate numero_uri in QSession to add template for qchat names - Suhas
• Add net-only quicr subscribe api via qsession - Suhas
• Build a libquicr test client to parse qchat messages
• Test net-only subscribe with mac client publish - Suhas
• Implement encode and decode for QChat message - Brett
• In Chat View, encode and send Watch message - Brett
• In Network View, decode and handle Watch message
• In QSession, handle watch message and map it to publishIntent and subscribe to room
• In Chat View, encode and send Ascii message
• In Network View, decode and handle Ascii message
• In QSession, handle incoming quicr message, map it to Qchat message and hand it over to UI Layer
• In Chat view, handle responses to Watch and Ascii messages

Management code that can upload to UI and Net at reasonable speeds

Current behaviour:

• Management code can run at the highest baudrate of 30000 for reliable upload to the net chip and the UI chip.
• Uses virtual wire that copies the exact register values from one register to another that corresponds with the UART pins

Expected behaviour:

• Management code can run at least a baudrate of 115200 and is reliable.
• Uses UART DMA for receive and transmission.