boards/msba2/lobaro-lorabox: change TERMFLAGS to PYTERMFLAGS#12095
boards/msba2/lobaro-lorabox: change TERMFLAGS to PYTERMFLAGS#12095maribu merged 3 commits intoRIOT-OS:masterfrom
Conversation
PORT is already given in pyterm TERMFLAGS.
Add a variable for `pyterm` specific flags that are not handled by other terminals. This will prevent issues with boards that have options only supported by `pyterm` and setting `pyterm` options from the environment.
The boards are using `pyterm` specific options that do not work on any other `RIOT_TERMINAL`. It is a shame this is required but at least do not pass arbitrary arguments to the other RIOT_TERMINAL. So use the new PYTERMFLAGS for this.
|
I can confirm that the terminal still works on the MSB-A2. The flags for |
|
I have no lobaro-lorabox to test. If someone would do this, I'd ACK |
|
I think the lobaro-lorabox is a bit more challenging. It seems like it needs the rts cleared to actually work. It does compile and connected but the bloombytes test doesn't actually execute... This is for both socat and picocom, it does work with pyterm. |
|
If this is the case then maybe we just throw an error or say |
|
I confirmed that you must toggle the rts to get the board running at all. Just plugging in will not allow it to execute (though battery power is fine). |
|
We could maybe change the flash script to leave the RTS cleared after so it would work if just flashed (meaning if could work for running all the tests). |
|
If special requirements for the terminal interface are more commen than exclusively these two boards, how about adding special variables like |
|
This PR does not address any compatibility with the other terminals, it just prevents sending arguments that do not match the program.
This would also not work after unplugging the board I guess. |
|
Yup, if it is out of scope then that is fine. Consider the lobaro-lorabox tested and expected to fail and another PR can take care of updating that. Probably by one of the people that have it! |
maribu
left a comment
There was a problem hiding this comment.
OK, now with testing done for both boards: ACK
|
Thank you for the review. |
Contribution description
The boards are using
pytermspecific options that do not work on anyother
RIOT_TERMINAL. It is a shame this is required but at least donot pass arbitrary arguments to the other RIOT_TERMINAL.
So use the new PYTERMFLAGS for this.
This addresses setting the TERMFLAGS in an incompatible way to the other
RIOT_TERMINALin #12089 #12090However,
termwould still not work withsocatorpicocom.Testing procedure
Testing still works on
msba2. For exampletests/bloom_bytestests/shellusingsocatIt does not fail on invalid arguments
Where in master,
socatwas called with incompatible argumentslobaro-loraboxThe
termcommand is still the same forlobaro-loraboxas inmasterI do not have a board to do the real test
Which gives this execution
Issues/PRs references