TimJTi commented on issue #17004: URL: https://github.com/apache/nuttx/issues/17004#issuecomment-3275678448
I didn't know of the app to calibrate this...the default for the board I based my custom board on had a seemingly sensible value but it would appear to be wrong having tried the app! It should be 61505 not 65775 it seems: but it depends on whether you compile with full optimization, so that's a further subtle factor here! By setting the default to -1 rather than 5000 for boards seems a good idea to me, but a -1 setting that throws an error might be confusing to NuttX newcomers? They now have to get an app built-in right away, just to calibrate this before they even get started? Perhaps a new default "magic" value could be caught during compile, re-mapped to (say) 5000 but with a compiler #warning to commend a calibration be done by the user some time soone? This wouldn't have caught my naïve assumption that is was OK for my derived board of course but I take that on the chin! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
