u-boot 2016.01-rc2 detects BeagleBone Black incorrectly
Hello,
I am running 2016.01-rc on BBB (Embest replica)
printenv shows the following:
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then if test $board_rev = BBG1; then setenv fdtfile am335x-bonegreen.dtb; else setenv fdtfile am335x-boneblack.dtb; fi; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name = A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;
after findfdt has been run,
fdtfile=am335x-bonegreen.dtb
But it is not correct. My $board_rev is the following, I have no idea why does it contain line break.
board_name=A335BNLT
board_rev=t\
ue
Hi Matwey
Quoted 16 lines · Matwey V. Kornilov
Hello,
I am running 2016.01-rc on BBB (Embest replica)
printenv shows the following:
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then if test $board_rev = BBG1; then setenv fdtfile am335x-bonegreen.dtb; else setenv fdtfile am335x-boneblack.dtb; fi; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name =
A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;after findfdt has been run,
Quoted 7 lines
fdtfile=am335x-bonegreen.dtb
But it is not correct. My $board_rev is the following, I have no idea why does it contain line break.
board_name=A335BNLT
board_rev=t\
Yuck, another variation! Can you do me a favor and dump the eeprom:
https://github.com/beagleboard/image-builder/blob/master/readme.md
Download and run:
sudo /bin/bash show-eeprom.sh
It uses hexdump and compatible with bb.org' 3.8/4.1/etc..
The green should only trigger on: 0x1a 0x00 0x00 0x00
Regards,
Signature · 2 lines
Robert Nelson https://rcn-ee.com/
2015-12-17 3:53 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 30 lines
Hi Matwey
Quoted 16 lines · Matwey V. Kornilov
Hello,
I am running 2016.01-rc on BBB (Embest replica)
printenv shows the following:
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then if test $board_rev = BBG1; then setenv fdtfile am335x-bonegreen.dtb; else setenv fdtfile am335x-boneblack.dtb; fi; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name =
A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;after findfdt has been run,
Quoted 7 lines
fdtfile=am335x-bonegreen.dtb
But it is not correct. My $board_rev is the following, I have no idea why does it contain line break.
board_name=A335BNLT
board_rev=t\Yuck, another variation! Can you do me a favor and dump the eeprom:
Quoted 7 lines
https://github.com/beagleboard/image-builder/blob/master/readme.md
Download and run:
sudo
/bin/bashshow-eeprom.sh
# sudo /bin/bash show-eeprom.sh eeprom: [?U3?A335BNLTt ue] eeprom raw: [00000000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 74 0a 75 65 |.U3.A335BNLTt.ue|]
Quoted 12 lines
It uses hexdump and compatible with bb.org' 3.8/4.1/etc..
The green should only trigger on:
0x1a0x000x000x00Regards,
--
Robert Nelson
https://rcn-ee.com/
Signature · 4 lines
With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207 at jabber.ru
Quoted 37 lines · Matwey V. Kornilov
2015-12-17 3:53 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 36 lines
Hi Matwey
Quoted 16 lines · Matwey V. Kornilov
Hello,
I am running 2016.01-rc on BBB (Embest replica)
printenv shows the following:
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then if test $board_rev = BBG1; then setenv fdtfile am335x-bonegreen.dtb; else setenv fdtfile am335x-boneblack.dtb; fi; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name =
A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;after findfdt has been run,
Quoted 7 lines
fdtfile=am335x-bonegreen.dtb
But it is not correct. My $board_rev is the following, I have no idea why does it contain line break.
board_name=A335BNLT
board_rev=t\Yuck, another variation! Can you do me a favor and dump the eeprom:
https://github.com/beagleboard/image-builder/blob/master/readme.md
Download and run:
Quoted 7 lines
Quoted 1 line
sudo
/bin/bashshow-eeprom.sh# sudo /bin/bash show-eeprom.sh eeprom: [?U3?A335BNLTt ue] eeprom raw: [00000000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 74 0a 75 65 |.U3.A335BNLTt.ue|]
ah, it's tripping on the "." = "0a" character..
Do you happen to remember where you purchased it and what it was called.. (for git commit)
This patch should work:
https://gist.github.com/RobertCNelson/21f44591c78daed7c637
Please test,
and i've added it to our table:
https://github.com/RobertCNelson/omap-image-builder/commit/620ebf627d3df8c693845bef07af232aa289ff41
Regards,
Signature · 2 lines
Robert Nelson https://rcn-ee.com/
2015-12-17 21:08 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 47 lines
Quoted 37 lines · Matwey V. Kornilov
2015-12-17 3:53 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 36 lines
Hi Matwey
Quoted 16 lines · Matwey V. Kornilov
Hello,
I am running 2016.01-rc on BBB (Embest replica)
printenv shows the following:
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then if test $board_rev = BBG1; then setenv fdtfile am335x-bonegreen.dtb; else setenv fdtfile am335x-boneblack.dtb; fi; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name =
A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;after findfdt has been run,
Quoted 7 lines
fdtfile=am335x-bonegreen.dtb
But it is not correct. My $board_rev is the following, I have no idea why does it contain line break.
board_name=A335BNLT
board_rev=t\Yuck, another variation! Can you do me a favor and dump the eeprom:
https://github.com/beagleboard/image-builder/blob/master/readme.md
Download and run:
Quoted 7 lines
Quoted 1 line
sudo
/bin/bashshow-eeprom.sh# sudo /bin/bash show-eeprom.sh eeprom: [?U3?A335BNLTt ue] eeprom raw: [00000000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 74 0a 75 65 |.U3.A335BNLTt.ue|]
Quoted 9 lines
ah, it's tripping on the "." = "0a" character..
Do you happen to remember where you purchased it and what it was called.. (for git commit)
This patch should work:
The patch works good.
But could you please explain me? I thought the problem was in 'test' operator. Unlikely
test '\0x74\0x0a\0x75\0x65' = BBG1
should be true.
Quoted 11 lines
Please test,
and i've added it to our table:
https://github.com/RobertCNelson/omap-image-builder/commit/620ebf627d3df8c693845bef07af232aa289ff41
Regards,
--
Robert Nelson
https://rcn-ee.com/
Signature · 4 lines
With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207 at jabber.ru
Quoted 7 lines
Quoted 7 lines
ah, it's tripping on the "." = "0a" character..
Do you happen to remember where you purchased it and what it was called.. (for git commit)
This patch should work:
Quoted 8 lines
The patch works good.
But could you please explain me? I thought the problem was in 'test' operator. Unlikely
test '\0x74\0x0a\0x75\0x65' = BBG1
should be true.
I saw this when i first booted the Green with the production eeprom, "test" doesn't seem to like non printable characters..
Sorry i didn't look into "test" much further..
Instead i just worked around it with the Green..
Regards,
Signature · 2 lines
Robert Nelson https://rcn-ee.com/
2015-12-20 1:29 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
ah, it's tripping on the "." = "0a" character..
Do you happen to remember where you purchased it and what it was called.. (for git commit)
This patch should work:
Quoted 8 lines
Quoted 5 lines
The patch works good.
But could you please explain me? I thought the problem was in 'test' operator. Unlikely
test '\0x74\0x0a\0x75\0x65' = BBG1
should be true.I saw this when i first booted the Green with the production eeprom, "test" doesn't seem to like non printable characters..
Seems, issue is in command parser, not in test itself.
Quoted 10 lines
Sorry i didn't look into "test" much further..
Instead i just worked around it with the Green..
Regards,
--
Robert Nelson
https://rcn-ee.com/
Signature · 4 lines
With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207 at jabber.ru
Quoted 17 lines · Matwey V. Kornilov
2015-12-20 1:29 GMT+03:00 Robert Nelson <[email protected]>:
Quoted 16 lines
Quoted 15 lines
Quoted 9 lines
ah, it's tripping on the "." = "0a" character..
Do you happen to remember where you purchased it and what it was called.. (for git commit)
This patch should work:
The patch works good.
But could you please explain me? I thought the problem was in 'test' operator. Unlikely
test '\0x74\0x0a\0x75\0x65' = BBG1
should be true.
Quoted 4 lines
Quoted 2 lines
I saw this when i first booted the Green with the production eeprom, "test" doesn't seem to like non printable characters..
Seems, issue is in command parser, not in test itself.
Yeah. You may be able to instead use 'cmp.w' and mw to try and keep all of this inside just the script side of things and outside of C. That also however may end up being even uglier.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151220/88c583c0/attachment.sig>