firmware: verify that the commands inside transaction are the same

[pat1]

In the pull request
#418
when inside a transaction we ignore the commands after the first
A transaction start with a command that request data and terminate when the data are returned or for timeout.

We can make a more robust system checking if the commands received inside a transaction are the same (repetition) or if different return an error (with a wrong CRC?) or no data.