Thanks for the help Robert
I have done all the changes, whatever you have mentioned in the Patch file,
but still the board is not booting up. I think only the *s_init() function
(file:board/ti/am335x/board.c)* is keep on executing repeatedly, as i can
see only this log i.e.* "**Unknown board: assuming BeagleBone Black."* (*file:
**board/ti/am335x/mux.c.) *in every 1 minute(approx.)
FYI:
As the u-boot source files what you are using and what i am using are not
completely same so i did all the changes manually (instead of applying the
patch directly).
e.g. --- /home/original/am335x_evm.h 2014-11-03 09:49:54.061434173 +0530
+++ include/configs/am335x_evm.h 2014-11-03 10:11:11.869458684 +0530
@@ -142,6 +142,8 @@
"run ramargs; " \
"bootm ${loadaddr}\0" \
"findfdt="\
+ "setenv fdtfile am335x-boneblack.dtb; "\
+ "setenv fdtbase am335x-boneblack; "\
"if test $board_name = A335BONE; then " \
"setenv fdtfile am335x-bone.dtb; fi; " \
"if test $board_name = A33515BB; then " \
so could you please help me out for solving this issue..
On Friday, October 31, 2014 7:36:21 PM UTC+5:30, RobertCNelson wrote:
>
> On Thu, Oct 30, 2014 at 10:50 PM, <[email protected] <javascript:>>
> wrote:
> > Hi Andrew,
> >
> > Now we are using one customized board based on Beaglebone Black Design.
> In
> > case of BBB TI is writing some board type configuration in the EEPROM,
> so
> > during the Initial booting process it reads those information and
> configures
> > the board accordingly.
> >
> > As we are using one fresh board we don't have anything written into
> the
> > EEPROM, because of which it is failing at the U-boot every time with
> some
> > errors like:
> >
> > U-Boot SPL 2013.01.01-00129-g6d40c2a-dirty (Oct 30 2014 - 09:58:22)
> > Incorrect magic number (0xffffffff) in EEPROM
> >
> > I have tried to skip the read_eeprom () in the u-boot which reads the
> > EEPROM header for board type, also done the Pin muxing in
> > board/ti/am335x/mux.c but didn't get any better result out of this.
> >
> > As per my knowledge if we will write the same Configuration into the
> EEPROM
> > as BBB then the board will boot properly. but we want to avoid that
> > procedure. so could you please tell me is there any other method to
> solve
> > this issue.
> >
> > Looking for a quick response from your end ..
>
> See this patch for reference (yes it's v2014.10)
>
> It is what CircuitCo uses to boot blank eeprom boards.
>
>
> https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.10/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch
>
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
