SAM E54 Platform » Chola Turbo

Modbus TCP development is ~80–85% complete.

Ethernet, IP, ARP, and TCP layers are fully working (connect + send success confirms this).

State machine and polling design are correct (init outside loop, poll inside loop).

The remaining 15–20% gap is protocol correctness at Modbus level:

Unit ID / MBAP length / register address validation

RX timeout + error handling

Proper response parsing and retry logic.
The code and logs were shared with Venu sir on Saturday, and we are currently awaiting his feedback.

Working

Due date extended to reflect integration, review and testing

Due date extended to 20/01/2026

Issue reported on 26th thru Teams

we are having a SERIOUS timing issue with Config packet reception/handling
it is taking between 3-5mins to receive a full packet size of 2k (127 signals)
we havenot been able to run a end to end to test to check the E-remos and data.
with limited signals, we are able to run end to end. (we NEED to deliver with all the signals enabled as per client)
Options

1. Hardcode all the signals in the device (Fixed configuration) - Malli to test
   fix modbus tcp issues if any.
2. USB tool to provide all the modbus registers to read
   Greeshma, do we have GUI to add/edit registers to read ? possible ?
3. Need Wireshark logs in the Local Server. Neha talk to Bhanu and get a us a log.
   Need TCP server logs too, to assess the delay
4. Prakash, pls get a timestamp in linux and provide a log.

USB integrated, 2 more issues pending , hard coded config pkt is not getting fully, looks like memory alignment due to compiler, it resets and socket receive from tcp modbus is NOT happening, wireshark shows data response..

Greeshma/Devipriyaa, pls check the extract_tcp_config() function, after 20 entries update, no error but data update doesn't happen.