Dear all,
I have the latest version of the beaglebone u-boot source which I took from the official git repository.But I need the particular version of the u-boot source that was used to build the binary that came along with the micro-SD in the board. My boot message shows the following
U-Boot 2011.09-00053-gb423c52 (Aug 10 2012 - 11:26:55).
The reason why I need it is summarised below.
We purchased a TI am3359 IDK. We successfully ported u-boot to it. But the ethernet interface is not working. Boot log shows that PHY reset timed out. When we used the microSD card that came up with beaglebone board and booted it in the IDK board(I know we are not supposed to do this,but just gave a try). We found that the ethernet interface worked. So we want to do a comparison of the bootloader source. We cloned the official u-boot source as suggested by the Beagleboard support pages and built it for beaglebone and tested if ethernet works. But then also we found that it doesn’t work. Only when i used the SDcard that came up with beaglebone, ethernet interface work and that is the reason we need the exact version of the u-boot source. Meanwhile we are debugging parallel, we want to try this approach as well.
Kindly excuse me if this question is stupid or is not the right place to ask for.
Regards,
Hari Prasath
one thing you can do is to configure the MII or RGMII interface (pinmux + setup) in the mux.c file and board.c for the latest u-boot from TI (ti ezsdk)
Dear all,
I have the latest version of the beaglebone u-boot source which I took from the official git repository.But I need the particular version of the u-boot source that was used to build the binary that came along with the micro-SD in the board. My boot message shows the following
U-Boot 2011.09-00053-gb423c52 (Aug 10 2012 - 11:26:55).
That means “v2011.09” with git hash “b423c52…”. I don’t know where that exactly came from, as it’s not in the TI vendor tree I deal with.
The reason why I need it is summarised below.
We purchased a TI am3359 IDK. We successfully ported u-boot to it. But the ethernet interface is not working. Boot log shows that PHY reset timed out. When we used the microSD card that came up with beaglebone board and booted it in the IDK board(I know we are not supposed to do this,but just gave a try). We found that the ethernet interface worked. So we want to do a comparison of the bootloader source. We cloned the official u-boot source as suggested by the Beagleboard support pages and built it for beaglebone and tested if ethernet works. But then also we found that it doesn’t work. Only when i used the SDcard that came up with beaglebone, ethernet interface work and that is the reason we need the exact version of the u-boot source. Meanwhile we are debugging parallel, we want to try this approach as well.
If you look at the sources in mainline you’ll see that we do run-time checking of which board we are running on and setup ethernet and other peripherals as needed. I would suggest going back to TI and asking them for the source used in the binary you have, and from there look at the board/ti/am335x/evm.c (or board.c) file and seeing how they setup ethernet on the IDK board. A patch vs mainline to fix ethernet on IDK would be most welcome and reviewed.
I cloned the following link and try to rebuild the u-boot & kernel, hoping that I would get the source of the u-boot so that I could compare with TI version of u-boot.
git clone git://github.com/Angstrom-distribution/setup-scripts.git
But it looks like after the build process, the sources are removed. How do I configure to leave the source code after the build process is complete ?
I also tied what was suggested in the link below, but then also the source code was not present.
http://wind.cs.purdue.edu/doc/crosscompile.html
I need to see the u-boot source code.
Update. I build u-boot using angstrom and I got the u-boot source. I flashed the u-boot image and MLO and tested it in the IDK and found ethernet is working.
But I dont think comparing this u-boot source with the u-boot source from TI’s PSP release would help.
Also when I booted the new u-boot image, I was getting error saying couldn’t read from NAND flash at address 0x280000. I am unable to modify the console u-boot environment variable. By default the console u-boot environment variable is set to ttyO3. I am surprised why this happens because Beaglebone uses ttyO0 as console. In the u-boot that came with the Beaglebone board, console was set to ttyO0.
Because of this I am not able to modify the network related u-boot params also and save it. I couldn’t see any console message.
We traced out the reason for the Ethernet interface working in the TI AM3359 IDK board when using a beaglebone u-boot. It was because the BB u-boot source had support for the PHY controller TLK110 that is present in the IDK board. TI PSP U-boot doesn’t have this support(may be because TI doesn’t officially support Linux on the IDK).
We did the required code changes in the TI’s u-boot and tested it. Ethernet interface did work this time.
Thank you all for your support and time.