<@U016EM8L91B> <@U016HSAA3RQ> Is caravel GPIO Inpu...
# chipignite
d
@Tim Edwards @jeffdi Is caravel GPIO Input Pull up feature is validated ? I am using caravel GPIO sample code link: https://raw.githubusercontent.com/efabless/caravel_board/main/firmware/chipignite/gpio_test/gpio_test.c and tried with GPIO_MODE_USER_STD_INPUT_PULLUP & GPIO_MODE_MGMT_STD_INPUT_PULLUP does not pull pad to high. Is there is any known issue ?
t
Which GPIO? This is being done on hardware? If so, which shuttle run? I need more information.
d
This CI0622Q Shuttle. I see Input/Output and Bi-Directional GPIO functionality are working. But GPIO_MODE_USER_STD_INPUT_PULLUP & GPIO_MODE_MGMT_STD_INPUT_PULLUP configuration does not pull the pad. I nearly tried most of the GPIO pads (0 to 37). Is Efabless team validated the GPIO pull up functionality?
t
The 2206Q design is correct and yes, the pull-up status has been tested and validated. The value of GPIO_MODE_USER/MGMT_STD_PULLUP, however, is incorrect in the caravel_board repository version of
defs.h
. The caravel repository has the correct value, which is
0x0801
for management pull-up and
0x0800
for user pull-up.
I have made a pull request to the caravel_board repository to fix the problem.
m
I think I just hit this too