On Tue, Jul 28, 2015 at 5:59 AM,  <[email protected]> wrote:
> Hello Robert,
> I was going through this forum to resolve my current problem with custom
> board copied from Beaglebone Black for our company's specific need.
> We are using AM3352 TI cpu and Alliance AS4C256M16D3 MEMORY chip set which
> has tCK 2.5 min 3.3 max.
>
> Hence, I board memory leveling though CCS 6.1.0  for DDR2, The following I
> noticed
> 1/ Jtag initialise and connect cortex A4 memory test seems to succeed
> 2/ When I try to set break point hard at s_init() CCS does NOT get set
> breakpoint
> 3/ Using Assembly code stepping system reach to following stage
>
> U-Boot SPL am335x (july 27 2015 16:46:16)
> Incorrect Magic Number (0xffffffff) in EEPROM
> Could not get Board Id.
> Unknown board, cannot configure pinmux. ####ERROR ###### Please RESET the
> board ####
>
> AND system hung permanently.
>
> After setting message and enumerated my structure am335x_baseboard_id
> in the function read_eeprom() the program fall out from lack of magic number
> while reading MLO file
> AS I noticed there were no values in the am335x_baseboard_id header
> structure.
>
> The question IS this check can be by passed?  Including all EEPROM info
> board name serial SKU etc
>
> I ran diff on the provided link for the board.c which exists on git repo
> am335x/board.c I did not found any difference.
>
> If you please shed some light on this problem I am stuck on this almost a
> week.
> Much appreciated for your  help.
> Thank you,

Yes you can bypass this.  However you can't use any of the current
patches as-is..

Since you are using ddr2, this has to take the "beaglebone" route,
(not beaglebone black (ddr3))..

Do you have an eMMC to worry about?

Regards,

-- 
Robert Nelson
https://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.

Reply via email to