Skip to contentSkip to conversation

configuring u-boot for custom board based on beaglebone(am335xx_evm)

U-Boot Pavan 3 participants 6 messages Dec 19, 2012 – Dec 28, 2012

lore
Share & tools
lore

Pavan

author
#0 lore raw

Hi,

i need to configure u-boot-2013.01.rc2 for my custom board, that
is completely based on beaglebone Rev A3,i have mux.h file according to my hardware i am not understanding the codeflow of beaglebone for include the mux.h.

i have some extra hardware on my board,but first i need to understand the codeflow for beaglebone then only i can change the all required files according to my hardware.

Can you please tell me which are the files i need to change? or u-boot is using pin-mux for baglebone?

I checked the file include/configs/am335x_evm.h and also in board/ti/am335x directory the mux.c is there,but i didn't understand the codeflow properly?

Please help me out?

Regards
Pavan

--
View this message in context: http://u-boot.10912.n7.nabble.com/configuring-u-boot-for-custom-board-based-on-beaglebone-am335xx-evm-tp143228.html
Sent from the U-Boot mailing list archive at Nabble.com.

#1 lore raw
Quoted 7 lines · Pavan

Hi,

i need to configure u-boot-2013.01.rc2 for my custom board, that
is completely based on beaglebone Rev A3,i have mux.h file according to my hardware i am not understanding the codeflow of beaglebone for include the mux.h.

Quoted 6 lines

i have some extra hardware on my board,but first i need to understand the codeflow for beaglebone then only i can change the all required files according to my hardware.

Can you please tell me which are the files i need to change? or u-boot is using pin-mux for baglebone?

No

Quoted 2 lines

I checked the file include/configs/am335x_evm.h and also in board/ti/am335x directory the mux.c is there,but i didn't understand the codeflow properly?

As you can see mux.c provides pinmuxes for dedicated hardware parts like UART, I2C etc. In enable_board_pin_mux() u-boot decides what board it is running on and activates relevant hardware parts. main line kernel makes the same. This was different for am3517 though.

Yegor

author
#2 lore raw

Hi Yegor,

Thanks for quick reply,

in u-boot source code to change the beagleboard -xM pin mux we
can change by updating the file board/ti/beagle/beagle.h by changing the MUX_BEAGLE() micro ,how can i access the same thing for beaglebone?

Regards
Pavan

--
View this message in context: http://u-boot.10912.n7.nabble.com/configuring-u-boot-for-custom-board-based-on-beaglebone-am335xx-evm-tp143228p143231.html
Sent from the U-Boot mailing list archive at Nabble.com.

#3 lore raw
Quoted 7 lines · Pavan

Hi Yegor,

Thanks for quick reply,

in u-boot source code to change the beagleboard -xM pin mux we
can change by updating the file board/ti/beagle/beagle.h by changing the MUX_BEAGLE() micro ,how can i access the same thing for beaglebone?

You don't. We intentionally only enable the muxes that are required rather than every single possible mux. You need to do the muxing in the kernel. And any clocking too, assuming it's not one fo the ones already enabled.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121219/95e5ae11/attachment.pgp>
author
#4 lore raw

Hi all,

i am using u-boot-2013.02.rc2 and cross-compiling for target
am335x_evm_uart2_config target its creating MLO and u-boot.img for my target.buts its not booting on uart2.

is there any configuration i need to change in u-boot source code?

Thanks

Regards
Pavan

--
View this message in context: http://u-boot.10912.n7.nabble.com/configuring-u-boot-for-custom-board-based-on-beaglebone-am335xx-evm-tp143228p143311.html
Sent from the U-Boot mailing list archive at Nabble.com.

#5 lore raw
Quoted 7 lines · Pavan

Hi all,

i am using u-boot-2013.02.rc2 and cross-compiling for target
am335x_evm_uart2_config target its creating MLO and u-boot.img for my target.buts its not booting on uart2.

is there any configuration i need to change in u-boot source code?

Nope. And that configuration has been tested on the full EVM and I belive a beaglebone with a UART cape.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121228/251fbed8/attachment.pgp>