Guillaume Sottas

Sorry for the delayed answer. Do you know which version of the **A2L** format specification you use? Because depending on it, either ```SYMBOL_LINK``` is a new keyword introduced after the...

could you tell me in which sub-node is the ```MOD_COMMON``` ? I tried to reproduce the problem in the test ```test_module_mod_common_node``` but it seems to work as expected, thus, I...

Thanks for the feedback. The parser fails because currently, only 'standard' ```IF_DATA``` nodes are supported. In this case, the node ```IF_DATA XCPplus``` will not be processed as expected (```IF_DATA XCP```)....

@hartkopp thank you for your detailed response. I will give a try to the *SO* link you shared. Concerning the `isotp_release()` code: In the past I've used the [J1939](https://elixir.bootlin.com/linux/v5.10.8/source/net/can/j1939) stack,...

Hello all, any news on this topic?

according to **ISO-15765-3**, *the P2_can_client* is defined as: *Timeout for the client to wait after the successful transmission of a request message (indicated via N_USData.con) for the start of incoming...

Hello @MatinF, - Concerning the `interval_1`: I think the transport layer handles the request and the response in two different transactions, and is not responsible of the `interval_1` timeout management....

Hello @pylessard, Concerning the hard-coded delay, I'm not sure to understand. The transport layer also specifies the **STMin** parameter (minimum separation time between two consecutive frames), which is communicated to...

Yes, I've added this feature (issue #36). When we call ```open_tunnel()```, the function internally calls ```open()``` and ```open()``` calls the JLink API ```JLINKARM_SelectIP(address=str, port=int)```. Internally, both ```address``` and ```port``` parameters...

Thank you for your feedback. You understood it correctly, here is the piece of assembly code (ARM none ABI): ```asm ... bl rst_get_reset_reason /* this function returns 6 */ ldr...