On Tue, Jul 28, 2015 at 5:59 AM, imrank...@gmail.com 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
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
I remember Robert shared u-boot sources where this eeprom check was omitted.
28 Июл 2015 г. 15:36 пользователь imrank...@gmail.com написал:
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.
I haven't dug in yet but when trying to execute git pull from within
/opt/script/tools/eMMC I get the following error message:
root@mydevice:/opt/scripts/tools/eMMC# git pull
error: server certificate verification failed. CAfile: /etc/ssl/certs/ca-
certificates.crt CRLfile: none while accessing
Date and time are definitely correctly and just checked again. I am still
getting the same error if running git pull from /opt/scripts/tools/eMMC but
if I run from /opt/scripts it works.
Should I be running git pull from eMMC directory or from scripts directory?
~C
On Saturday, June 13,
I will create another BBB from scratch and check, but after running git
pull from /opt/scripts I can now run it from /opt/scripts/tools/eMMC??
Maybe it's just been too long of a week.
On Saturday, June 13, 2015 at 4:16:32 PM UTC-5, Colin Bester wrote:
Date and time are definitely
Much appreciated, thanks!
On Thursday, June 11, 2015 at 3:34:45 PM UTC-5, RobertCNelson wrote:
On Thu, Jun 11, 2015 at 3:24 PM, Colin Bester bester...@gmail.com
javascript: wrote:
Thanks Robert, I assume when using rsync method that you boot the BBB's
eMMC
that you want to clone and
On Thu, Jun 11, 2015 at 3:24 PM, Colin Bester bester.co...@gmail.com wrote:
Thanks Robert, I assume when using rsync method that you boot the BBB's eMMC
that you want to clone and then run the
beaglebone-black-make-microSD-flasher-from-eMMC.sh script as opposed to
executing script after
On Thu, Jun 11, 2015 at 3:04 PM, Colin Bester bester.co...@gmail.com wrote:
After backing up eMMC contents to SD card and then restoring via method
similar to mentioned in
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents, booting from a
SD card and using dd to write to eMMC I have
Thanks Robert, I assume when using rsync method that you boot the BBB's
eMMC that you want to clone and then run the
beaglebone-black-make-microSD-flasher-from-eMMC.sh script as opposed to
executing script after booting up from a SD card - is this correct?
If so, what about any changes to
Gerald, do you know a faster way to write on the eeprom than that :
U-Boot# i2c mw 0x50 00.2 0xaa 0x1
U-Boot# i2c mw 0x50 01.2 0x55 0x1
U-Boot# i2c mw 0x50 02.2 0x33 0x1
the last argument is the length to write, but how can I pass a string ? or
an array of bytes ?
Le vendredi 6 septembre 2013
You can write a piece of code or a script to do it .
GerladGerald
On Tue, May 12, 2015 at 2:19 AM, Mickae1 mickamus...@gmail.com wrote:
Gerald, do you know a faster way to write on the eeprom than that :
U-Boot# i2c mw 0x50 00.2 0xaa 0x1
U-Boot# i2c mw 0x50 01.2 0x55 0x1
U-Boot# i2c mw
Hello,
I'm trying to make image of my beaglebone using : sudo dd if=/dev/mmcblk0
bs=1M | ssh machinekit@192.168.7.2 'dd of=/home/rimvis/Desktop/bbb.img
bs=1M',
but everytime i get error : dd: opening `/home/rimvis/Desktop/bbb.img': No
such file or directory. Obviously that directory exists.
Hello,
I'm trying to clone my beaglebone using : sudo dd if=/dev/mmcblk0 bs=1M |
ssh machinekit@192.168.7.2 'dd of=/home/rimvis/Desktop/bbb.img bs=1M'
but everytime i get error ; dd: opening `/home/rimvis/Desktop/bbb.img': No
such file or directory. Any ideas how to solve it ?
--
For more
Hi everybody,
I've tried the same version that Victor MV used but I'm still at the same
point:
U-Boot SPL 2011.09-00053-gb423c52 (Aug 10 2012 - 11:26:55)
Texas Instruments Revision detection unimplemented
Incorrect magic number in EEPROM
Hi Gerald,
I want to clone earlier version BeagleBone (whilte), just get rid of P8, P9
to make smaller size. I download u-boot,img and kernel from
http://elinux.org/Beagleboard:BeagleBone#Image_Files. So basically my board
will be same as BeagleBone (whilte). Do I still need to write some
You can get the EEPROM from a normal BeagleBone and i believe it's even
written at the SRM.
Regards,
El lunes, 25 de noviembre de 2013 19:03:31 UTC+1, shiwe...@gmail.com
escribió:
From Beaglebone schematic, the EEPROM is to store MAC Address and
Variables, can you provides codes on what
Hi Victor MV,
I'm also cloning the same board (beaglebone white).
I've read the entire discussion but I'm not sure what steps you've been
through for write the EEPROM.
Did you modified the u-boot or just used an older version?
What are the right i2c commands for writing the EEPROM?
Thank you
18 matches
Mail list logo
