[Neeraj Dantu]

samsam,

Apps is currently working on the updated software package.

You should be able to generate code using CubeMX. Note that you will have to map the pins between STM32MP1 package and OSD32MP1 package. https://octavosystems.com/app_notes/osd32mp15x-pin-mapping-to-stm32mp1/ can help you do that. Should be pretty easy as all IO pin names are the same.

Best,

Neeraj

[Neeraj Dantu]

JenOnOctavo,

Thank you for bringing this to our attention. We are investigating the matter of un-flashed OSD32MP1-RED boards. For the boards that you have for development, we are making our flasher card available on the web here: https://octavosystems.com/files/osd32mp1-red-flash-image/.

The procedure to flash the eMMC on OSD32MP1-RED is given below:

1. Extract the flasher image from the above link

2. Program the flasher image into an SD card (32GB – Image is 16GB) using either Etcher(https://www.balena.io/etcher/) or Win32DiskImager(https://sourceforge.net/projects/win32diskimager/) software. On Linux, you can use ‘dd’

3. Put the board in SD boot mode (101b — 2 switched on either side away from the board, middle switch towards the board)

4. Insert the SD card you flashed with the flasher image into the board’s SD card slot

5. Power the board up and wait ~15 min. The board should indicate booting and function with HRTBT LED showing a heart beat pattern

6. Once the board is flashed, USRLED(below PWR LED) will turn ON. This indicates that the board flash is complete

7. To verify board flash, put the board into eMMC boot mode(010b — 2 switches on either side towards the board, middle switch away from the board) and power the board up. The board should boot without any SD card.

UPDATE: After investigation, we found that there is an issue with the flasher image programming the FSBL partition of OSD32MP1-RED. In order to rectify the issue, please follow the directions below:

Requirements: Host PC with Cube Programmer, USB-C cable and OSD32MP1-RED

Download the files required for flashing OSD32MP1-RED here: https://octavosystems.com/wp-content/uploads/2021/10/osd32mp1-red-emmc-deploy.tar.xz

On a Host Ubuntu PC:

– tar xvf osd32mp1-red-emmc-deploy.tar.xz

Set the boot mode on OSD32MP1-RED to USB/Serial (0b000)

Connect the board to the host PC using the USB-C cable

Verify that the board is connected to the PC in update mode:

– STM32_Programmer_CLI -l USB

The output of this command should indicate the USB port the board is connected to.

Now Flash the board’s TF-A partition using the following command:

– STM32_Programmer_CLI -c port=USB1 -w Flashlayout_emmc_osd32mp1-red-trusted-tfa.tsv

After the board is programmed(Should take <10 sec), set the boot mode to eMMC(0b010) and power up the board.

Best,

Neeraj

 

• This reply was modified 3 years, 6 months ago by Neeraj Dantu.

[Neeraj Dantu]

hzhu,

Have you connected PMIC_BSTIN to 5V input? The kernel message indicates that for some reason the driver unable to set the output voltage of the boost converter to 5.2V.

Best,

Neeraj

[Neeraj Dantu]

Manuel,

The pre-built image should be the same as built with the SDK. Please check if you have the following setting in device tree for PLL4: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/u-boot-v2018.11/osd32mp1-red-u-boot.dtsi#L169. This PLL is responsible for generating the clock for LTDC peripheral.

Best,

Neeraj

[Neeraj Dantu]

hzhu,

Please check the status of header pin PC02 when you connect to the the daughter board. You might be booting into DFU mode. If you want to avoid this issue, you can modify/remove the following line from BRK device tree: https://github.com/octavosystems/OSD32MP1-BRK-device-tree/blob/master/u-boot-v2020.01/stm32mp157c-osd32mp1-brk-u-boot.dtsi#L29.

Best,

Neeraj

 

BestNLPD9

[Neeraj Dantu]

Andrzej,

Please take a look at fbset command(https://linux.die.net/man/8/fbset). This can help you set margins and other display parameters at runtime.

Since all LCD screens are a little different, the  configuration in which the board is booting might not be optimal for your screen. According to https://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/LCDC.html, the driver used is /drivers/video/fbdev/da8xx-fb.c. You can also change the LCD initialization parameters here in the driver: https://elixir.bootlin.com/linux/latest/source/drivers/video/fbdev/da8xx-fb.c#L187.

Best,

Neeraj

[Neeraj Dantu]

Manuel,

Can you make sure that the jumper configuration on the board is such that the LCD pins are connected to the HDMI framer? Please see Sheet #3 of the RED schematic: https://octavosystems.com/docs/osd32mp15x-red-schematic-pdf/. It looks like the monitor is being recognized. If Weston is crashing, it could mean that the SoC is unable to push LCD data at a pixel rate that is required. Did you change any of the clock tree settings? One more thing to check is whether you are running the default RED image. Please use an SD card and see if the images on OSD32MP1-RED page will work(https://octavosystems.com/octavo_products/osd32mp1-red/#Software).

Best,

Neeraj

[Neeraj Dantu]

Orocle,

We are sorry that you are disappointed in the BRK. It is a low cost board that was designed for embedded use cases not requiring a screen. Thank you for your feedback on this and we will look at how we can make adjustments to this design in the future. In the meantime if you are looking to drive a full LCD display please see the OSD32MP1-RED that provides a couple of different connectors for screens.

Best,

Neeraj

[Neeraj Dantu]

Manuel,

It looks like the weston service is exiting with fault. Can you restart the service and see what happens? Please also report when this error occurs, does it occur when you are trying to plug in a monitor?

Try different monitors and resolutions as well.

Best,

Neeraj

• This reply was modified 3 years, 9 months ago by Neeraj Dantu.

[Neeraj Dantu]

mlarkin,

Your best bet is to use a USB hub connected to the USB host port you are using.

In order to use the OTG port as host, the ID pin must be connected to GND or to the USB port for the USB peripheral to detect the host configuration. For device configuration, this is not necessary(ID pin can be left floating).

Best,

Neeraj

[Neeraj Dantu]

mlarkin,

The BRK’s micro-USB is not setup to function as host. Please take a look at the requirements in section 10.1.12 (USB) of 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).

You can use the dedicated Host USB pins provided on PB29 and PB30 Header pins(https://octavosystems.com/docs/osd32mp1-brk-schematics/). You can use a USB Type A breakout (https://learn.sparkfun.com/tutorials/usb-type-a-female-breakout-hookup-guide/all) to implement a USB host port. You will not need to make a device tree change.

Best,

Neeraj

[Neeraj Dantu]

Manuel,

I have seen a similar error, but after the board was finished flashing. You could try re-installing Cube Programmer or using a previous version, may be 2.5/2.4.

Best,

Neeraj

[Neeraj Dantu]

Manuel,

Here are some steps you can take to debug this issue:

1. To verify that the hardware works, see if the RNDIS functionality works when you boot up Linux. You should see an extra virtual Ethernet interface

2. Try a different board such as the BRK, DK2 or EV1.

3. Change your USB cable.

4. Check whether you have all the device rules installed for your Cube Programmer software.

A couple of threads that may be interesting: https://community.st.com/s/question/0D53W000000aP9J/no-stm32-device-in-dfu-mode-connected  and https://community.st.com/s/question/0D53W00000LCUHa/no-stm32-device-in-dfu-mode-connected.

Best,

Neeraj

 

[Neeraj Dantu]

Karl,

1. We are currently working on updates to the RED board BSP to the latest v3.0 of OpenSTLinux. Expect an update in a few weeks.

2. It looks like from the documentation(https://docs.docker.com/docker-for-windows/wsl/), the SDK should be able to run on WSL. We will test the next version on WSL as well. For now, our best bet is a VM.

Best,

Neeraj

[Neeraj Dantu]

Arian,

Please take a look at https://community.st.com/s/question/0D50X0000B8iBSB/stm32mp157-ethernet-problem for more information and solution on this issue. Essentially, the RED board does not implement a 125MHz clock connection between the PHY and STM32MP1. So, this reference clock needs to be generated internally.

Along with  https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/linux-v4.19/stm32mp157c-osd32mp1-red.dtsi#L1808, You will also need to make changes to TF-A device tree like here: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/tf-a-v2.0/osd32mp1-red.dts#L164 and U-Boot device tree like here: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/u-boot-v2018.11/osd32mp1-red-u-boot.dtsi#L96.

 

For more information, please take a look at https://wiki.st.com/stm32mpu/wiki/Ethernet_device_tree_configuration#RGMII_with_Crystal_on_PHY-2C_no_125Mhz_from_PHY.

Best,

Neeraj

[Author]

Posts