[Anthony]

Neeraj,

Please disregard the last post. Some device tree updating fixed my wifi problem so that is resolved. I tried following the guide above to disable RTC but still having issues booting the BLANK image. I’ll continue to troubleshoot that but if you have any other tips, please let me know.

Thanks for all your help
Anthony

[Anthony]

Neeraj,

Thanks! I’ll try the guide out today and report back!

I have a separate issue to inquire about now. I have the WL1835 integrated and wired per the guide with the BB blue as a reference. I used the BB blue device tree as a baseline and everything seems to work fine. However, when I scan wifi and issue “services” command in connmanctl, it returns an empty list. The “technologies” command shows the wifi is powered. I’ve tried different antennas with no luck. Any troubleshooting tips for this?

Thanks
Anthony

[Anthony]

Neeraj,

To run the BLANK image, I would like to update the SLP to disable the RTC but can’t seem to find the instructions to do this. Can you please provide these instructions?

Thanks,
Anthony

[Anthony]

Neeraj,

You are correct. I do not have an RTC oscillator for OSC1.

Anthony

[Anthony]

Neeraj,

Update – I tried using the BLANK image you provided above (without patches) with the am335x-pocketbeagle.dtb tree but had no luck. I wasn’t able to see to ethernet gadget with this configuration.

When I used the latest beaglebone image, with the patches and the am335x-pocketbeagle.dtb tree, I was able to get the board to boot and ssh over usb. I will try to update this tree with my board updates and see how it turns out.

Thanks for all your help!

Anthony

[Anthony]

Hi Neeraj,

If it is possible to progressively update the device tree, I would assume using the pocketbeagle device tree should at least get me communicating over the USB client (USB0) and board booted from SD (MMC0) since I used the same pins from the Pocketbeagle for these 2 components. I know I won’t have WIFI or the USB host but by using the default Pocketbeagle device tree, should I at least be able to boot the board and see the network device on my computer?

Thanks,
Anthony

[Anthony]

Hi Neeraj,

Thanks for the detailed response. I was able to resolve the error in the log shortly after posting.

When you mention copying a BBB model name and compatibility string in my custom device tree, do you mean arbitrarily adding these strings or does it matter which model I enter? My board is essentially a pocketbeagle with wifi and a usb host.

model = “TI AM335x BeagleBone Black”;
compatible = “ti,am335x-bone-black”, “ti,am335x-bone”, “ti,am33xx”;

I’ll try the BLANK image you posted. Is it safe to assume I’ll still need a working device tree for by board for it to fully boot or is this just easier than applying those patches to bypass the EEPROM check?

Thanks for all your help
Anthony

[Anthony]

Hi Eric,

Unfortunately, the boards have been built and we did not breakout those UART pins. Is it at least safe to assume that we need to get a working device tree up before one can see the usb network device?

If so, I will keep working that. I was able to find a beaglebone board to run dtb-rebuilder on my device tree but running into this error.

Error: src/arm/am33xx.dtsi:14.1-2 syntax error
FATAL ERROR: Unable to parse input tree
Makefile:148: recipe for target ‘src/arm/pelican_v0.dtb’ failed
make[1]: *** [src/arm/pelican_v0.dtb] Error 1
Makefile:96: recipe for target ‘all_arm’ failed
make: *** [all_arm] Error 2

[Anthony]

I have been trying to compile a new custom device tree for my custom board. However, I am running Ubuntu 18.04 on the laptop I used to compile and getting errors (unable to parse input tree) with the am33xx.dtsi file. I assume the compiler with my Ubuntu isn’t compatible with the version files I am modifying. If this is the case, can you please direct me to the appropriate version of DTB-Rebuilder?

[Author]

Posts