[Neeraj Dantu]

Carlos & mkleox,

The apps team is currently working on this. We are currently testing and resolving issues with Debian SDK v3.0 (compatible with OpenSTLinux v3.0). I will update once the repo is updated.

Best,
Neeraj

[Neeraj Dantu]

Gil,

For DDR3, the current listed in the table is the total worst case power consumption of DDR that includes everything. As described in the app note you linked(https://octavosystems.com/app_notes/osd32mp1-power-budgeting/), it is hard to determine the exact power consumption of the board as it depends heavily on application/use case. Moreover, some of the current consumption on power rails like in your list(VDDA1V1_REG, VDDA1V8_REG, VDD3V3_USB) are very low compared to the system power consumption and can be neglected during power budgeting, which is why only PMIC, DDR and SoC core current consumptions were taken into account in the application note. Also note that the power consumption of each interface is different when it is in use vs idle.

For VDD power consumption, you can generate test cases for CubeMX as shown in Section 2.2 of the above app note. We recommend you go through the power budgeting process as shown in the app note and then determine the low power states you want to implement where the current consumption on each rail becomes much more important.

Best,
Neeraj

[Neeraj Dantu]

Farid,

My apologies, I assumed you wanted USB2 to be a HOST port because you are connecting a USB type-A connector. If you are intending to use USB2 as a device, you can use OSD32MP1-BRK device tree(https://github.com/octavosystems/OSD32MP1-BRK-device-tree/blob/master/linux-v5.4/stm32mp157c-osd32mp1-brk.dts). You can find the schematics for BRK here: https://octavosystems.com/docs/osd32mp1-brk-schematics/.

Best,
Neeraj

[Neeraj Dantu]

Gil,

This can be a little tricky. According to the PMIC programming document from ST(https://www.st.com/resource/en/application_note/dm00682242-the-stpmic1-ic-programming-guide-stmicroelectronics.pdf), the minimum circuitry needed for the PMIC re-programming is power input on VIN, VIO and I2C line connections.

Can you try pulling NRST LOW and seeing if the PMIC responds to I2C commands? NRST disables the power outputs. So, you should be able to program the PMIC if it responds to I2C commands. If this does not work, and you cannot change the circuit configuration to not connect VDD to VDDA1V8_REG, you could try letting it set to 3.3V by default. Although, it is not clear whether the part will survive this.

As described in the PMIC programming document linked above, we recommend adding some configuration around VDDA1V8_REG and BYPASS_REG1V8 to be able to program the PMIC during manufacturing.

Best,
Neeraj

[Neeraj Dantu]

Farid,

interrupt-parent and interrupt values depend on which pins you use for the interrupt. If you want to use PD14 as the interrupt pin, the interrupt-parent value is “gpiod” and interrupts value is “14 IRQ_TYPE_LEVEL_HIGH”.

Best,
Neeraj

[Neeraj Dantu]

Farid,

Please taka a look at section 10.1.12 on the hardware getting started guide for STM32MP1: https://www.st.com/resource/en/application_note/dm00389996-getting-started-with-stm32mp151-stm32mp153-and-stm32mp157-line-hardware-development-stmicroelectronics.pdf for all possible USB configurations including using USB2 port as HOST. You can also find an example circuit in Sheet 6 of OSD32MP1 RED: https://octavosystems.com/docs/osd32mp15x-red-schematic-pdf/.

An example of the device tree for using USB1 as HOST port is shown here as part of OSD32MP1-RED device tree: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/linux-v5.10-r0/stm32mp157c-osd32mp1-red.dts#L1400.

Best,
Neeraj

[Neeraj Dantu]

mlarkin,

As discussed above, it is unclear what the cause of this error might be. As it looks like it is working correctly on Ubuntu, it could be a bug in the Windows specific version of the Cube Programmer. We suggest you report this to ST.

Best,
Neeraj

[Neeraj Dantu]

Gil,

You can reprogram the PMIC to set the output voltage of BUCK3 to 1.8V permanently. Please see https://octavosystems.com/app_notes/stpmic1-non-volatile-memory-programming-guide/ for a method to reprogram STPMIC. “NVM_BUCKS_VOUT_SHR”(https://www.st.com/resource/en/datasheet/stpmic1.pdf) can be used to set output of BUCK3.

Please also note that you will have to set PMIC outputs in TF-A device tree(https://github.com/STMicroelectronics/arm-trusted-firmware/blob/v2.4-stm32mp/fdts/stm32mp15xx-dkx.dtsi#L102), U-Boot(https://github.com/STMicroelectronics/u-boot/blob/v2020.10-stm32mp/arch/arm/dts/stm32mp15xx-dkx.dtsi#L360) and Linux(https://github.com/STMicroelectronics/linux/blob/v5.10-stm32mp/arch/arm/boot/dts/stm32mp15xx-dkx.dtsi#L360).

Best,
Neeraj

[Neeraj Dantu]

gile_he,

That is correct. You can use any of the Turn-ON conditions you described from the PMIC datasheet.

Best,
Neeraj

[Neeraj Dantu]

gil_he,

You are correct that you will need to set VDD to 1.8V in order to make use of HS200 mode for eMMC. Please see https://www.st.com/resource/en/application_note/dm00389996-getting-started-with-stm32mp151-stm32mp153-and-stm32mp157-line-hardware-development-stmicroelectronics.pdf for details. Please make sure that you will need this performance as most applications do not require the HS200 mode.

You will not need VDD as 1.8V for Gig LAN implementation. Please see https://octavosystems.com/octavo_products/osd32mp1-red/ for a reference implementation of RGMII with 3.3V as VDD.

Looks like you have taken a look at https://octavosystems.com/forums/topic/procedure-for-configuring-vdd1-8v/. The post describes all the configuration required for 1.8V IO.

Best,
Neeraj

[Neeraj Dantu]

Farid,

USB enumeration happens as part of the boot process as well as once the board boot is complete. What I think you are experiencing is the delay between when the board powers up and when the kernel finishes boot up, which is when the enumeration happens. The actual enumeration should take ~1 sec once the cable is connected.

You can verify this by using the barrel connector to power the board. Once the board is booted up(this would take ~35 sec), you can connect the USB cable to see it come up instantly.

Finally, USB peripheral cannot be accessed by the M4 core. You will need to use the A7 core to control the USB peripheral.

Best,
Neeraj

[Neeraj Dantu]

Carlos,

Please take a look at the webinar we put together with Witekio on this topic here: https://app.livestorm.co/witekio/webinar-leveraging-software-power-on-a-system-in-package-platform/. The 3rd presenter goes through the differences between Debian and OpenSTLinux. Both distributions have their advantages. Hopefully, the webinar helps you make the decision.

Best,
Neeraj

[Neeraj Dantu]

imahgin,

You should find the latest updates on meta-octavo-osd32mp1 repo now. Note that there are still a couple of issues we are working on fixing. Please use the SD card interface for development for now.

Best,
Neeraj

[Neeraj Dantu]

VDDA1V8_REG is connected internally to VDDA1V8_DSI. You can find this as a test point on the MP1: VDDA1V8_REG, ball R7. VDD1V2_DSI_REG is connected internally to VDD1V2_DSI_PHY. You can find this as a test point on the MP1: VDD1V2_DSI_REG, ball R6.

Best,
Neeraj

[Neeraj Dantu]

imahgin,

We are doing our final testing on OpenSTLinux 3 support for OSD32MP1-RED. Thank you for your patience so far. We will be updating the repo this week.

Best,

Neeraj

[Author]

Posts