[Neeraj Dantu]

Fury,

You are correct. You will only be able to set/change the CPU frequency via the CubeMX tool/device tree modification. The OSD32MP1 currently integrates the stm32mp157c version of the processor which specifies a maximum frequency of 650MHz. 800MHz version of OSD32MP1 will be supported later.

Best,

Neeraj

[Neeraj Dantu]

Fury,

The USB host pins can be used to attach an external USB  host port. 5V can come in from VIN(at 5V) or another external power source. Just make sure to tie the GND pins of the external source and the board together. If you are using a computer/laptop USB port to power the board, you will have to account for the current consumption/inrush of the USB device inserted for it to work.

USB Host Power – Either VIN or External power

USB Host DM – DM pin of BRK

USB Host DP – DP pin of BRK

USB Host GND – GND for BRK + External power GND

 

Best,

Neeraj

[Neeraj Dantu]

Ian,

STM32MP1 can boot from various removable and non-removable boot devices. Please take a look at https://wiki.st.com/stm32mpu/wiki/STM32MP15_ROM_code_overview for all the boot devices that can be used.

You are right that the eMMC has a small pitch. But, you can still use thick trace widths routing through the NC pins. Please take a look at https://octavosystems.com/app_notes/designing-for-flexibility-around-emmc/ for the details.

Best,

Neeraj

[Neeraj Dantu]

PD,

The best way to utilize the GPMC interface would be to use the OSD335x-SM, which does not include the eMMC and therefore can provide access to all the pins of the GPMC interface. 

Using the C-SiP for this purpose would be unnecessary, as your use case disregards the eMMC completely.

Best,

Neeraj

[Neeraj Dantu]

Aaron,

Yes, The USB pins on the header(PB29, PB30) are by default in host mode.

Best,

Neeraj

[Neeraj Dantu]

Hey Alberto,

We are currently working on application notes to generate the images and will make the device tree source files for the board along with an update to the existing CubeMX app note available in the coming weeks. We will keep you updated here.

Best,

Neeraj

[Neeraj Dantu]

April,

You should be able use standby mode on by default on a supporting kernel. See https://processors.wiki.ti.com/index.php/AM335x_Power_Management_Standby_User%27s_Guide for more information on low power states.

Can you upgrade to a current version of the Beagle image and try again?

Best,

Neeraj

[Neeraj Dantu]

Beko,

Thanks for the inputs. We will create some documentation around the issue.

Best,

Neeraj

[Neeraj Dantu]

Beko,

Both #1 and #2 are not recommended and will result in operating the SiP and SoC out of spec.

The way to mitigate these issue would be the following:

1. Use buffers(bidirectional if needed) with enable input. You can tie the enable pin to either SYS_VDD3_3P3V(powers the IO domain of the SoC) or a GPIO that you can control based on when you want the device to communicate with off-board peripherals.

2. You should not connect any GPIO to 5V. This poses a risk of permanent damage to the SoC. A voltage translator buffer is the best solution for this issue.

Please let us know if you have more questions.

Best,

Neeraj

[Neeraj Dantu]

Hey Hardik,

Apologies for the late response.

1. Based on the user manual, the USB Pro Touch utility connects via USB. So, you will have to tap into the USB interface and connect to a computer to do the software configuration.

Note that all of the configuration settings necessary are provided through strap pins and if you just copy the circuit configuration on OSD3358-SM-RED, you should have no issues setting if the PHY as host with 4 downstream ports.

2. You are correct. Ideally, VBUS_DET should be pulled up to 5V via a resistor divider. But, we have not had any issues with the direct connection.

Best,

Neeraj

[Neeraj Dantu]

Aleix,

Thanks for pointing this out. The symbols we have do indicate the pin number A1. But, the origin should be as you pointed out on the upper left corner. We are glad that you were able to find the issue. We will add this change to our next release.

Best,

Neeraj

[Neeraj Dantu]

Alberto,

How is the customer powering the VREF pin? This board boot(presumably using starter image for Discovery Kit – 2(DK-2)) assumes that they have the same configuration as DK-2. If they are powering VREF buffer externally, while also turning it on in the device tree could cause it to fault resulting in failure of ADC subsystem to come up.

 

See https://wiki.st.com/stm32mpu/wiki/ADC_device_tree_configuration for info on configuration of ADC according to hardware.

Best,

Neeraj

 

[Neeraj Dantu]

Hardik,

Unfortuntely, due to the volatility in availability of passive components, the passive components could change between builds(although specifications remain the same), we do not publish a BOM for the reference design.

For the capaciors, the general rule of thumb is the voltage rating needs to be about double the voltage that it will be connected accross. So, 10V capacitors should work well.

Please let us know if you have more questions. Please feel free to go through our sales channel as well if you need additional information regarding the BOM.

Best,

Neeraj

[Neeraj Dantu]

Hardik,

You are correct. The pin layout for the Micro-HDMI connector is mislabelled. Note that however, the hardware layout is correct and verified to be working. It is just the symbol pin numbers not matching the correct pins of the connector. We will correct this ASAP. Thanks for pointing this out.

Best,

Neeraj

[Neeraj Dantu]

Beko,

Yes. The recommendation is to have the RTC subsystem turned ON in function as well as power. You will need to add an RTC crystal on OSC1 in order to enable the RTC subsystem.

Please let us know if you have more questions.

Best,

Neeraj

[Author]

Posts