Re: Galileo Gen 1 GPIO

Tomasz Bursztyka

Hi Gottfried,

Using this Cypress chip is a mandatory support as a low level pinmuxing
if you want to configure and use the hardware pins, the ones exposed as
arduino compatible.
Your use case of inserting an arduino shield is exactly one of those
which will fail.

If you take a look here:
You'll see the grey boxes "MUX": this is about this chip.

The mapping:

It is the same story for Gen 2, but the chip is different. Take a look
at boards/galileo/pinmux*
(and drivers/gpio/gpio_pcal9535a.c).

About USB, Zephyr as a low level usb API. I know it works for Quark SE
SoC, but not Quark x1000 (Galileo's).
It could be the same controller, I don't know if anyone has tried.



Thanks for your answer.Like Fabio I also want to use Galieo v1 board
but not really certain about your answer and what
type of restrictions you are talking about.Myself I will not use
Cypress so maybe your answer would be different.
But it would be nice to know what GPIO restrictions are there on
Galileo v1
Playing around with busybox on Galileo was cool but would love to
connect 2 devices to it ( one usb-host ,one arduino shield ).I am
well aware that you work for zephyr and not Galileo



On Mon, Sep 19, 2016 at 7:37 AM, Tomasz Bursztyka
<mailto:tomasz.bursztyka(a)>> wrote:

Hi Fábio,

Unfortunately, we do not support Galileo v1 pinmuxing, thus: the
whole board is basically unusable at this stage.
You won't be able to get very far unless you provide the cypress
chip driver.

Can you use another board? We support quite a few (see boards
directory in zephyr's tree)



Dear Sirs,
I am using Galileo Gen 1 (Cypress I/O expander) and I can
not change the GPIO levels.
What GPIO driver should I set in menuconfig tool
(DesignWare, PCAL9535, MMIO, Intel SCH)?
What driver name and pin numbers should I use in functions
API (gpio_pin_configure, gpio_pin_write, ....)?
Thank you very much.

Join to automatically receive all group messages.