Neeraj Dantu

Forum Replies Created

Viewing 15 posts - 481 through 495 (of 600 total)

← 1 2 3 … 32 33 34 … 38 39 40 →

Author

Posts
September 25, 2019 at 2:27 pm in reply to: How to enter USB boot #9161
Neeraj Dantu
Moderator
Eric,

Thanks for the update. If you want to use the Uniflash tool, please make sure to configure it at described in section 6.2.1 of the application note

Best,

Neeraj
September 24, 2019 at 4:40 pm in reply to: Ethernet Gadget in U-Boot #9156
Neeraj Dantu
Moderator
srebers,

From the logs(last lines), it looks like the board is trying to use CPSW(ethernet PHY) as the communication interface. The RED board uses a different PHY than the Beaglebone Black. Can you verify that the USB RNDIS is being used by using “printenv ethact”?

Addition info in this thread: https://stackoverflow.com/questions/32747239/can-u-boot-support-more-than-one-ethernet-port

Also note that we demonstrated TFTP boot over USB interface on the RED board in this app note: https://octavosystems.com/app_notes/programming-emmc-with-usb/

Please follow up here.

Best,

Neeraj
September 24, 2019 at 2:56 pm in reply to: EEPROM programming via JTAG #9154
Neeraj Dantu
Moderator
Memaher,

Please take a look at baremetal code attached to the EEPROM application note: https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/#_Toc382081438

Best,

Neeraj
September 23, 2019 at 11:48 am in reply to: 3D Diagram #9116
Neeraj Dantu
Moderator
Hey Randy,

Thank you for the input. Currently, you can generate a Solidworks model with Altium 3D model export support: https://www.altium.com/documentation/15.1/display/ADES/NFS_15_1((Enhanced+3D+Model+and+Export+Support))_AD

We will add the 3D model on our website as well in the future.

Best,

Neeraj
September 20, 2019 at 5:07 pm in reply to: OSD3358-SM custom board linux boot issue #9111
Neeraj Dantu
Moderator
Anthony,

See https://octavosystems.com/forums/topic/osd335x-c-sip-bootloader-issues/ for relevant discussion. Aleix was kind enough to put together a guide: https://docs.google.com/document/d/1mLe8aKckKvg9QwjWJkdTg8gPltMKCRK__lkcNBFa6k0/edit

Best,

Neeraj
September 19, 2019 at 12:58 pm in reply to: UART0 hardware flow control #9085
Neeraj Dantu
Moderator
Kartik,

I am assuming the flow control pins for UART0(C12/C13) are accessible on your custom board. Hardware flow control is supported in omap uart driver.

You should be able to test hardware flow control for UART. First, you will have to set pin multiplexing for these pins in your device tree. You should add pin mux details of C12 and C13 her: https://github.com/RobertCNelson/dtb-rebuilder/blob/4.14-ti/src/arm/am335x-bone-common.dtsi#L92

Please see application notes regarding device tree for help:

Pin multiplexing for OSD335x: https://octavosystems.com/app_notes/osd335x_pinmux/

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

For testing, please take a look at: http://processors.wiki.ti.com/index.php/Linux_Core_UART_User%27s_Guide. You can also create a test environment by setting up your board as transmitter and pull down the CTS pin to GND to see if the processor stops communication.

Best,

Neeraj
September 18, 2019 at 8:19 pm in reply to: How to enter USB boot #9084
Neeraj Dantu
Moderator
Eric,

I am able to verify that the RNDIS ethernet adapter does show up in Windows 10 when you hold down the boot button with no SD card present.

Did you check whether you have the RNDIS driver installed? The board should send out BOOTP requests on the USB interface before it jumps to UART boot mode on UART0. If you are seeing characters on the UART console, it means that the board has cycled through the other boot modes in the list.

I would advise to try a different host Windows machine.

Another suggestion is for you to install the Uniflash tool from TI and try to boot from USB:http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_Tools.html#sitara-uniflash

We demonstrate how to use Uniflash to program EEPROM for the OSD335x family here: https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/#_Toc382081434

Please let us know if you make progress or if you have additional questions.

Best,

Neeraj
September 17, 2019 at 4:24 pm in reply to: How to enter USB boot #9078
Neeraj Dantu
Moderator
Eric,

You should be able to see a USB RNDIS adapter on your computer. Please make sure you have the RNDIS driver(https://developer.toradex.com/knowledge-base/how-to-install-microsoft-rndis-driver-for-windows-7). The board should show up under “Network Adapters” in Device Manager.

Also, make sure the RED board is functional and boots through eMMC and SD card.

Best,

Neeraj
September 17, 2019 at 10:10 am in reply to: OSD3358-SM custom board linux boot issue #9077
Neeraj Dantu
Moderator
Anthony,

Thanks for the update! Glad you are able to get it to work.

I am not sure why you were unable to boot with the BLANK image. Do you have an RTC oscillator on OSC1 on the board? If you do not, my guess is that u-boot is trying to exercise RTC and running into a fault(See https://octavosystems.com/forums/topic/osd335x-c-sip-bootloader-issues/)

Let us know if you have any other questions.

Best,

Neeraj
September 16, 2019 at 10:42 pm in reply to: OSD3358-SM custom board linux boot issue #9074
Neeraj Dantu
Moderator
Anthony,

Yes, you should be able to boot the board with the PocketBeagle device tree

Best,

Neeraj
September 16, 2019 at 7:07 pm in reply to: OSD3358-SM custom board linux boot issue #9072
Neeraj Dantu
Moderator
Anthony,

The model you enter does make a difference for start-up services. I would suggest try the Beaglebone Black model name to try and boot the board and communicate via the RNDIS ethernet adapter since that is your first goal.

You will not need a separate device tree to boot the board if you are booting from the SD card interface using the same pins as PocketBeagle and if you are using the same USB0 configuration as on the PocketBeagle.

Now, in order for the board to be fully functional however, you would need to build a custom device tree that includes the wifi module and other devices on your board.

Hope that helps.

Best,

Neeraj
September 16, 2019 at 5:05 pm in reply to: OSD3358-SM custom board linux boot issue #9070
Neeraj Dantu
Moderator
Hey Anthony,

The error log for the dtb rebuilder indicates that there is an error in line 14 of file am33xx.dtsi. Did you change anything in this file?

Please see the device tree tutorial: https://octavosystems.com/app_notes/osd335x-design-tutorial/osd335x-lesson-2-minimal-linux-boot/linux-device-tree/ and pinmux tutorial for dtb-rebuilder usage: https://octavosystems.com/app_notes/osd335x_pinmux/

Note that the USB RNDIS adapter gadget is started by a startup script: https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh and it checks for the model name “/proc/device-tree/model” against the strings here: https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L113(may vary for different Beagle images). The model is set in the device tree like: https://github.com/RobertCNelson/dtb-rebuilder/blob/4.14-ti/src/arm/am335x-boneblack.dts#L16. If you are using a custom device tree, you may want to copy Beaglebone Black model name and compatibility string in the device tree.

For the board, if you are able to see the ethernet gadget for a little while, the board has indeed booted and is at least running the internal ROM code.

We suggest you use one of the BLANK images from Beagle from https://rcn-ee.com/rootfs/bb.org/testing/ without any patch being necessary. These images do not check for a Beagle ID in the EEPROM. For example: BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz

You should also verify all the output voltage rails and clock on the SD card CLK line to make sure that the board is not failing and is probing the SD card for an image to boot.

Please let us know how it goes and if you have more questions.

Best,

Neeraj
September 3, 2019 at 3:43 pm in reply to: Welcome to the OSD32MP1 Forum! #9006
Neeraj Dantu
Moderator
Hey Aliberal,

The DDR type and specification used in OSD32MP1 is the same as the one on the DK2 board. So, DDR configuration for both can be interchangeable. The tuning parameters might differ a little. But, they can be easily regenerated with CubeMX DDR testing suite. We have tested the <OCATVO PART NUMBER>_MinimalConfig.ioc on a standard DK2 board and it works.

Please let us know if you have more questions.

Best,

Neeraj
August 30, 2019 at 4:10 pm in reply to: Choice of Driver IC for TFT Display #8957
Neeraj Dantu
Moderator
Hi Randy,

The best way to decide would be to see if these displays have Linux drivers and whether the driver support is enabled via kernel modules in your system.

Out of the 4, it looks like ILI9327(https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/display/panel/ilitek,ili9322.txt) and HX8352(https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/display/himax,hx8357d.txt) have potentially compatible drivers.

You can find out if the drivers were built as kernel modules by searching the device driver specific config variable in the kernel compilation config file. This file is available in /boot/ directory for the Beagle images.

Regarding choice of display, we would suggest you look at Display capes for Beaglebone Black/Wireless such as https://4dsystems.com.au/4dcape-70t

or

https://www.mouser.com/new/newhaven-display/newhaven-beaglebone-cape/

Using existing display designs will make your prototyping much easier than bringing up a new display.

Best,

Neeraj
August 15, 2019 at 12:19 pm in reply to: Component Libraries? #8882
Neeraj Dantu
Moderator
Thanks for the feedback! We will include the download links on the top of our article.

Best,

Neeraj
Author

Posts

Viewing 15 posts - 481 through 495 (of 600 total)

← 1 2 3 … 32 33 34 … 38 39 40 →