[Neeraj Kumar Reddy Dantu]

Hey T,

The following things can be implemented to achieve higher current on USB host terminal:

– Switch TPS2051 current switch as you mentioned with a switch with a higher capacity.

– You are also right that you would have to move the supply voltage rail for VBUS to an different 5V supply other than SYS.

Best,

Neeraj

[Neeraj Kumar Reddy Dantu]

Hi Steven,

Please make sure that you have the latest image on PocketBealgle. The image requirements for different clicks can be found on this page: https://github.com/beagleboard/pocketbeagle/wiki/Click-boards%E2%84%A2

All the device tree overlays reside in /lib/firmware/. So, a good way to verify the device tree overlay was invoked properly or where it failed is to go through the boot log. You can see the boot log on UART0 terminal while the board is booting or you can find it in /var/log folder.

Can you attach the boot log file here?

[Neeraj Kumar Reddy Dantu]

Thank you very much for documenting the procedure! Very helpful

Neeraj

[Neeraj Kumar Reddy Dantu]

Tk,

It looks like the device tree binary file am335x-boneblack-emmc-overlay.dtb could not be found in /boot/dtbs/[kernel version] directory. Following Andy’s post above https://octavosystems.com/forums/topic/custom-board-boot-missing-emmc-dtb-file/#post-6401 is a good way to go about for bringing up a custom board. Please let us know if you face anymore issues.

Checkout these links for additional information regarding boot process and device tree:

https://octavosystems.com/app_notes/osd335x-design-tutorial/osd335x-lesson-2-minimal-linux-boot/osd335x-lesson-2-linux-boot-process-with-the-osd335x/

https://octavosystems.com/app_notes/osd335x-design-tutorial/osd335x-lesson-2-minimal-linux-boot/linux-device-tree/

Neeraj

 

[Neeraj Kumar Reddy Dantu]

We will look into fixing the formatting. Thanks

[Neeraj Kumar Reddy Dantu]

Hey Dave,

Thank you for sharing the valuable info! For anyone looking for more information, here is a hardware design oriented application note describing how to integrate wireless into your design with the OSD335x/OSD335x-SM: https://octavosystems.com/app_notes/enabling-iot-with-osd335x/

Neeraj

[Neeraj Kumar Reddy Dantu]

Hey J,

From the image TAMU1.png, it looks like you have the line that enables the overlay commented. Remove the beginning ‘#’ and you should be able to invoke the device tree overlays.

Best,

Neeraj

[Neeraj Kumar Reddy Dantu]

Great! Thanks for the update. Very cool looking board.

Neeraj

[Neeraj Kumar Reddy Dantu]

If the board shows shorts on the rails you have listed even before it is powered up, it would point to a manufacturing issue. Solder bridging could be the cause.

Also, from a design point of view, make sure none of the devices that connect to the OSD335x drive the IO pins for the OSD335x-SM before the device completely powers up as that can cause faulty behavior.

• This reply was modified 6 years, 9 months ago by Neeraj Kumar Reddy Dantu.

[Neeraj Kumar Reddy Dantu]

Glad you are able to resolve the issue. Thanks for letting us know. We plan to create more collateral around CAN bus and Buildroot in the future.

Neeraj

[Neeraj Kumar Reddy Dantu]

Samy,

From the boot logs, it looks like the processor is unable to detect the ethernet PHY by probing the MDIO interface. We will be reaching out to you shortly for a closer look at your PHY hardware configuration.

Neeraj

[Neeraj Kumar Reddy Dantu]

Samy,

If you are using the same hardware configuration as Beaglebone Black (same circuit with PHY connected to AM335x on MII1 and MDIO interfaces), you should be able to bring up the network without modification to the Beagle image, since you already have the magic number in your EEPROM. Coming to your question, the line is setting the PHY address ‘0’, i.e., the kernel is going to look for an ethernet PHY at address ‘0’ on the MDIO interface for identification and driver load. Note that the address of the ethernet PHY can be set in hardware (See section 3.7 in LAN8710 datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/00002164B.pdf).

Can you attach your boot logs for a closer look at the error?

Neeraj

[Neeraj Kumar Reddy Dantu]

Samy,

You can ignore the uboot error if you are not using ethernet at uboot. If you are unable to bring up the network after Linux boot, make sure you have the correct PHY address in the device tree. You can find the PHY address settings in the PHY datasheet. Here is an example of the PHY address setting on the Beaglebone Black device tree: https://github.com/RobertCNelson/dtb-rebuilder/blob/4.14-ti/src/arm/am335x-bone-common.dtsi#L421

Best,

Neeraj

[Neeraj Kumar Reddy Dantu]

Samy,

Can you post the complete boot logs so we can determine where in the boot process is it entering this fault condition?

If this is from uboot, you could try halting the autoboot process when the board gets to uboot by hitting the space bar(You will have 2 seconds to do this). You will have a uboot command line from which you should be able to use uboot commands to stop the USB module and USB PHY.

Also, see http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot

Best,

Neeraj

[Neeraj Kumar Reddy Dantu]

Samy,

If you left the USB interface pins unconnected in your design, you should be able to just boot up Linux without issue. If you need to explicitly disable the USB ports, you will have to make a custom device tree that does not enable the USB subsystem. Please see https://github.com/RobertCNelson/dtb-rebuilder for examples of device trees you can modify.

More info on device tree: https://octavosystems.com/app_notes/osd335x-design-tutorial/osd335x-lesson-2-minimal-linux-boot/linux-device-tree/

Another way to achieve this is by changing kernel configuration options when you build the kernel. See http://e2e.ti.com/support/arm/sitara_arm/f/791/p/413913/1470309 for additional info.

Neeraj

[Author]

Posts