driver/at30tse75x: port to ztimer_usec#17137
Conversation
|
If you want to test on hardware, this sensor is available on the samr21-xpro boards provided by IoT-LAB (Saclay site only), see https://www.iot-lab.info/docs/boards/microchip-samr21/ |
b550f14 to
e990bb5
Compare
e990bb5 to
95be6bf
Compare
|
@aabadie: I neither can get the master nor the PR working on the iot-lab.info. I get in both cases |
|
@aabadie: test worked the senor is at 0x4f (riot defaults to 0x48)-> maybe you are able to change the link to the in the iot-lab documentation to the Microchip IO1 Xplained extension doc mentation is wrong maybe microchips own docu is the right choice |
|
You forgot to adapt the module dependencies in Kconfig |
Is RIOT/drivers/io1_xplained/include/io1_xplained_params.h Lines 37 to 39 in c739516 correct then? |
fjmolinas
left a comment
There was a problem hiding this comment.
Tested, seems to work fine:
BOARD=samr21-xpro make -C tests/driver_io1_xplained/ flash term -j
2021-11-05 11:27:50,172 # SD Card CID info:
2021-11-05 11:27:50,173 # MID: 3
2021-11-05 11:27:50,173 # OID: SD
2021-11-05 11:27:50,173 # PNM: DSU04
2021-11-05 11:27:50,174 # PRV: 128
2021-11-05 11:27:50,174 # PSN: 4012115276
2021-11-05 11:27:50,174 # MDT: 252
2021-11-05 11:27:50,175 # CRC: 177
2021-11-05 11:27:50,175 # +----------------------------------------+
2021-11-05 11:27:50,176 #
2021-11-05 11:27:51,155 # Light level: 0
2021-11-05 11:27:51,159 # +-------------------------------------+
2021-11-05 11:27:56,196 # Temperature [°C]: 23.312
2021-11-05 11:27:56,200 # +-------------------------------------+
2021-11-05 11:27:57,208 # SD Card CID info:
2021-11-05 11:27:57,209 # MID: 3
2021-11-05 11:27:57,209 # OID: SD
2021-11-05 11:27:57,210 # PNM: DSU04
2021-11-05 11:27:57,211 # PRV: 128
2021-11-05 11:27:57,213 # PSN: 4012115276
2021-11-05 11:27:57,214 # MDT: 252
2021-11-05 11:27:57,214 # CRC: 177
2021-11-05 11:27:57,218 # +----------------------------------------+
2021-11-05 11:27:57,219 #
2021-11-05 11:27:58,226 # Light level: 0
2021-11-05 11:27:58,230 # +-------------------------------------+
2021-11-05 11:28:03,267 # Temperature [°C]: 23.187
2021-11-05 11:28:03,271 # +-------------------------------------+
2021-11-05 11:28:04,279 # SD Card CID info:
2021-11-05 11:28:04,280 # MID: 3
2021-11-05 11:28:04,281 # OID: SD
2021-11-05 11:28:04,282 # PNM: DSU04
2021-11-05 11:28:04,282 # PRV: 128
2021-11-05 11:28:04,284 # PSN: 4012115276
2021-11-05 11:28:04,285 # MDT: 252
2021-11-05 11:28:04,286 # CRC: 177
2021-11-05 11:28:04,290 # +----------------------------------------+
2021-11-05 11:28:04,290 #
2021-11-05 11:28:05,298 # Light level: 0
2021-11-05 11:28:05,301 # +-------------------------------------+
Yes, I just wasn't using saul which lead me to search .... |
a5fe74b to
314bc00
Compare
|
moddif.txt Seems like this rule isn't in KConfig: Lines 26 to 36 in 314bc00 |
f3792bf to
4ebb099
Compare
|
I am not sure i this is the way i am supposed to solve that (I would think there is some kind of Automatisation to try to get a working configuration for xtimer but it seem like "No") |
@leandrolanzieri is this one of the corner cases where we match configuration to match in the test application or is it something to be fixed in the modeling? |
|
Every kind of trying to auto select the MODULE_XTIMER_ON_ZTIMER failed due to being a loop. (tryed selects with if depend on, if block that include or remove that choiceblock) Making the choice (of x_on_z or xtimer_compat) non optional would make it allway include one (even if no one need a xtimer interface) May be it is just the case that we need more explicit choices with KConfig |
This should be changed in Kconfig modelling. I'm looking into it to provide a fix.
Yes, we need to make it non optional but also depend on xtimer being there. |
4ebb099 to
314bc00
Compare
|
with #17165 in this should work without that last commit |
|
Retested on IoT-LAB and works. ACK |
Contribution description
port at30tse75x-driver to ztimer_usec
Testing procedure
build and run tests/at30tse75x-driver
Issues/PRs references
#17111