gumstix-users

Hello,
I am trying to get access to as many UARTs on the gumstix as possible
and use mmc cards (via the netmmc board) as well. I have been going
through the list and comparing the PXA255 data sheets with the gumstix
60 and 90 pin connector diagrams and I'm at a loss.
Please correct me if I 'm wrong here, but there are 4 UARTs on the
PXA255, right (FFUART, BTUART, Standard UART and HWUART)? All of which
are brought out on the 60 pin connector.
According to the PXA255 data sheet, the FFUART's Tx and Rx lines are
used by the MMC controller on GPIO 34, 39. Bowever, they are not brought
out on the 90pin which is how they would interface to the netmmc board.
Does this mean that all four of those UARTs are usable (pending
disabling BT etc)? Does the netmmc not use a cs line or is it done
internally on that board, not using the PXA255's control lines?
Thanks for help,
Ernest

On my connex 400, nfs mounts work out of the box. I only add ppp module
and asynch modem support options in the kernel and the new image isn't
able to nfs mount anything. I read a little about what nfs needs and it
appears portmap is necessary for nfs to work but when I check the
portmap option in the menuconfig I get a build error
"undefined reference to get_myaddress"
is there a dependency package I need to include also ?

On my connex 400, nfs mount works out of the box. I only add ppp module
and asynch modem support options in the kernel and the new image isn't
able to nfs mount anything. I read a little about what nfs needs and it
appears portmap is necessary for nfs to work but when I check the
portmap option in the menuconfig I get a build error
"undefined reference to get_myaddress"
is there a dependency package I need to include also ?
Thanks Ben

On May 24, 2006, at 6:25 AM, Ernest Earon wrote:
> I am trying to get access to as many UARTs on the gumstix as possible
> and use mmc cards (via the netmmc board) as well. I have been going
> through the list and comparing the PXA255 data sheets with the gumstix
> 60 and 90 pin connector diagrams and I'm at a loss.
>
> Please correct me if I 'm wrong here, but there are 4 UARTs on the
> PXA255, right (FFUART, BTUART, Standard UART and HWUART)? All of which
> are brought out on the 60 pin connector.
Correct. To be precise, the 60-pin connector brings out GPIO lines
which can be configured as alt functions to connect the PXA's UARTs
to those GPIO lines, enabling 4 UARTs to come out on the 60-pin total.
> According to the PXA255 data sheet, the FFUART's Tx and Rx lines are
> used by the MMC controller on GPIO 34, 39. Bowever, they are not
> brought
> out on the 90pin which is how they would interface to the netmmc
> board.
MMCCS0 and MMCCS1 are also available on other GPIO lines (8&9) which
don't conflict with the FFUART, and those lines (8&9) are the ones we
use for the MMC circuits on the gumstix and daughtercards (basix,
netMMC and netDUOMMC). Actually, we only use GPIO8 right now
(MMCCS0). 34&39 are used for the FFUART which is by default the
console on all gumstix.
> Does this mean that all four of those UARTs are usable (pending
> disabling BT etc)? Does the netmmc not use a cs line or is it done
> internally on that board, not using the PXA255's control lines?
ethernet boards use GPIO49 (which is HWRXD on the 60-pin) as nPWE, so
you'll be limited to only 3 UARTS if you're also using ethernet.
CF boards (including the upcoming wifistix) use lots of those nPWE/
nPOE/nPIO[WR]/etc lines which are overloaded with HWUART function, so
you're limited to 3 UARTs if you use CF too.
Note that when limited to 3 UARTs, you can choose between:
FFUART+STUART+BTUART or
FFUART+STUART+HWUART
since the BTUART lines (GPIO42-45) are configurable to be connected
inside the PXA to the HWUART instead.
C