When running this example on an LED-connected GPIO, the delay
of 1 second is too large, and the selected values not very good
to notice the difference in brightness.
Use a ramp array of values with a more visual difference when
running on an LED and shorten the wait between changes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
From the user point of view the the main change is the addition of function
ldx_gpio_request_by_controller() which selects the gpio to use using following
arguments:
- controller: The controller name or alias of the GPIO to request.
- line: The line number of the GPIO to request.
- request_mode argument has been removed since that argument only has
sense for sysfs related functions as it controls the way the line is
exported and unexported.
The configuration file entries change to following format:
- USER_LED = mca-gpio,12
- USER_BUTTON = mca-gpio,10
Also improved argument parsing and help
https://jira.digi.com/browse/DEL-6425
Signed-off-by: Hector Bujanda hector.bujanda@digi.com
In previous implementation, if alias wanted to be used, it had to be passed twice.
https://jira.digi.com/browse/DEL-6425
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Use the same prompts that we use in the online documentation:
* For the target: "~#"
* For the host: "~$"
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This commit:
* adds the name of the connector in the readme files
* uses the official platform names
* minor changes for consistency between readme files
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
We need to reduce the optimization level in order to be able to
perform a debugging of the applications, without this there is
an strange behaviour while debugging.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
The first time that the example is run there was an error
related with an invalid value for the duty cycle.
With this fix we set the duty cycle to 0 when we close the example.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>