On Mon, Oct 9, 2017 at 5:41 PM, Stéphane Charette
<[email protected]> wrote:
> On Mon, Oct 9, 2017 at 12:39 PM, Stephane Charette
> <[email protected]> wrote:
>>
>> In the past, I used to identify the type of device by reading the file
>> /proc/device-tree/compatible.  For example, see this:
>>
>> > hexdump -C /proc/device-tree/compatible
>> 00000000  74 69 2c 61 6d 33 33 35  78 2d 62 6f 6e 65 2d 67
>> |ti,am335x-bone-g|
>> 00000010  72 65 65 6e 00 74 69 2c  61 6d 33 33 35 78 2d 62
>> |reen.ti,am335x-b|
>> 00000020  6f 6e 65 2d 62 6c 61 63  6b 00 74 69 2c 61 6d 33
>> |one-black.ti,am3|
>> 00000030  33 35 78 2d 62 6f 6e 65  00 74 69 2c 61 6d 33 33
>> |35x-bone.ti,am33|
>> 00000040  78 78 00                                          |xx.
>> |
>>
>> Last night I upgraded to a new build.  I installed this one:
>>
>>
>> https://rcn-ee.com/rootfs/bb.org/testing/2017-10-08/stretch-iot/BBB-blank-debian-9.2-iot-armhf-2017-10-08-4gb.img.xz
>>
>> Now I see that same model no longer identifies itself as a BBG.  it now
>> thinks it is a BBB:
>>
>> > hexdump -C /proc/device-tree/compatible
>> 00000000  74 69 2c 61 6d 33 33 35  78 2d 62 6f 6e 65 2d 62
>> |ti,am335x-bone-b|
>> 00000010  6c 61 63 6b 00 74 69 2c  61 6d 33 33 35 78 2d 62
>> |lack.ti,am335x-b|
>> 00000020  6f 6e 65 00 74 69 2c 61  6d 33 33 78 78 00
>> |one.ti,am33xx.|
>> 0000002e
>>
>
>
> I should also have mentioned:  I have not upgraded or installed new builds
> since...early 2017?  This is my first time back working with my beaglebones
> in probably 8 months.  So this change in behaviour may actually have been
> quite a while ago.

Ugh, so it's not a bug, it's just the way the final *.dtb is generated
with u-boot overlays:  (we build up from one dtb..)

So if we assume the BeagleBone Green = BeagleBone Black (minus) HDMI
(audio/video)...

BeagleBone Green:

Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green:

uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
loading /boot/dtbs/4.9.53-ti-r67/am335x-boneblack-uboot.dtb ...
55752 bytes read in 170 ms (319.3 KiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1105 bytes read in 871 ms (1000 Bytes/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
695 bytes read in 830 ms (0 Bytes/s)

[    0.000000] OF: fdt:Machine model: TI AM335x BeagleBone Black

BeagleBone Black:

Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBoard.org BeagleBone Black:

uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
loading /boot/dtbs/4.9.53-ti-r67/am335x-boneblack-uboot.dtb ...
55752 bytes read in 69 ms (789.1 KiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /lib/firmware/OSD3358-00A0.dtbo ...
441 bytes read in 1234 ms (0 Bytes/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1105 bytes read in 160 ms (5.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4169 bytes read in 877 ms (3.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
695 bytes read in 175 ms (2.9 KiB/s)

[    0.000000] OF: fdt:Machine model: TI AM335x BeagleBone Black

So you can see how both boards start out as
"am335x-boneblack-uboot.dtb" and we add, eMMC/HDMI/WL1835/ADC..

I guess we could patch in the model/compatble...

BBBW:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBBW-WL1835-00A0.dts#L32-L33

BBGW:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBGW-WL1835-00A0.dts#L41-L42

Is it really worth it thou? ;)

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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYirxiX-dzQ33Dg4_MkP_BWdMeNE1h%3DYR%2BPv375x%3DP2UcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to