Thank you Eric for your response.
There are a couple of ways to get around the EEPROM ID check.
1. Bypass the checks in u-boot:
Here is a link to the section of code that you will need to modify:I’m not sure if this is exactly the same code as what you are running, but we have seen in the past that the puts() for the “Bad EEPROM …” statement would not actually print anything to the UART console and it would look like everything would just hang when the EEPROM was not programmed. If you look at the board/ti/am335x/mux.c file of your u-boot build, then you can see the actual code you are running and can modify it so that you use the “board_is_bone()” configuration for the pinmux (or define your own)2. Use Robert Nelson’s patch to create u-boot that will boot and allow you to program the EEPROM: In u-boot apply the patch:
Using the “blank” image, create a file in the first partition:/boot/.eeprom.txtUse the variable: board_eeprom_headerFor a built-in device:12345board_eeprom_header=bbb_blankboard_eeprom_header=bbbl_blankboard_eeprom_header=bbbw_blankboard_eeprom_header=os00_blankboard_eeprom_header=beaglelogic_blankFor a non built-in, use “eeprom_program”12345678910111213141516eeprom_program=i2c dev 0; \i2c md 0x50 0x00.2 20; \i2c mw 0x50 0x00.2 aa; \i2c mw 0x50 0x01.2 55; \i2c mw 0x50 0x02.2 33; \i2c mw 0x50 0x03.2 ee; \i2c mw 0x50 0x04.2 41; \i2c mw 0x50 0x05.2 33; \i2c mw 0x50 0x06.2 33; \i2c mw 0x50 0x07.2 35; \i2c mw 0x50 0x08.2 42; \i2c mw 0x50 0x09.2 4e; \i2c mw 0x50 0x0a.2 4c; \i2c mw 0x50 0x0b.2 54; \i2c md 0x50 0x00.2 20; \reset ;You can also just run the “run eeprom*” commands from U-Boot console. (This works in “blank” and “normal” images.)One other thing that I wanted to mention: I know you are aware of the Linux device tree, but u-boot also uses a device tree that you might need to modify. You should find the u-boot device tress in ./arch/arm/dts It is useful to look through the 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch patch from Robert Nelson (see https://eewiki.net/display/linuxonarm/BeagleBone+Black) since this patch modifies device trees and can point you to important directories in u-boot.
I have a serial connection to UART0. My device has RS232 that connects to UART0 so i used that to connect. I connected at 9600 – 8-N-1 and software flow control. I wasn’t sure what the default Baud rate was going to be in this case. I launched Putty and prints an “@” first and then the letter “B” every few seconds. Does that mean anything to anyone? I tried to type in the terminal but it doesn’t respond to anything.
I went through the procedure to bypass the EEPROM. The procedure assumed a lot but i got through most of it. I installed an Ubunto VM and then figured out i needed to search for Terminal to run those commands that were listed. Then found out i had to install wget and git. I got up to step 5 and ran into a problem. I attached what was displayed in the terminal. Maybe i was supposed to change to a different directory or something. I’m a Windows guy so the direction needs to be fairly clear. Using ubuntu in a VM was painful to navigate but i have to do this.
Attachments:
I’m afraid it made no difference. I also created a new VM using Virtualbox because my first VM was in VMWARE VSphere and i could not gain access to the SD card. The VM that I created in Virtualbox gave me SD Card access but i had the same “no such file or directory” error when running the command. I can use pwd by itself and it will print the current working directory.
When i run this –
export CC=?pwd?/gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
and then run this to check it –
${CC}gcc –versionI get the error
I even typed in the full path instead of using ‘pwd’
I looked in the bin directory and there is no directory with the name “arm-linux-gnueabihf-”
I’m not sure what the purpose of the export is but it looks like its creating a variable called “CC” that is used in the calls to compile
