Neeraj Dantu
Forum Replies Created
-
AuthorPosts
-
November 10, 2021 at 12:28 pm in reply to: UART/Debug access via USB-C port on OSD32MP1-RED design #11925
Farid,
Apart from ssh over RNDIS as Aedan mentioned above, there is no way to get console logs from STM32MP1 via USB while the board is still booting. Alternatively, you can add an extra USB port with an FTDI chip to convert UART4(default console output for STM32MP1) output to USB.
Best,
Neeraj
imaghin/mhdzr/aliberal,
This is currently being worked on. Please expect a git repo(https://github.com/octavosystems/meta-octavo-osd32mp1) update by 1st/2nd week of Nov.
Best,
Neeraj
October 27, 2021 at 10:25 am in reply to: How to read OSD32MP1-RED CPU/SiP Temperature in Debian Image #11906In addition to inputs from Carlos, please take a look at the temp sensor device tree entries for OSD32MP1-BRK here: https://github.com/octavosystems/OSD32MP1-BRK-device-tree/blob/master/linux-v5.4/stm32mp157c-osd32mp1-brk.dts#L993
Best,
Neeraj
mlarkin,
We apologize for the delay. You should see a BRK release this week followed by a RED release.
Best,
Neeraj
Manu,
Please look at an update to the post here: https://octavosystems.com/forums/topic/osd32mp1-red-no-pre-loaded-debian-linux/#post-11732. The root cause of this issue is that the Flasher image was not able to program the FSBL(TF-A) partition of the image with the proper TF-A binary. You should be able to get the eMMC boot to work with the workaround described in the updated forum post.
Best,
Neeraj
Khan,
There are multiple ways of configuring pins for OSD33x. Beaglebone provides a user space utility called config-pin(https://www.bacpeters.com/2020/01/25/configuring-the-beaglebone-black-gpio-pins-permanently/) that you can use to change the pin functions from I2C-2 to GPIO.
You can also make changes in the device tree to do this. Please take a look at the pinmux application note here: https://octavosystems.com/app_notes/osd335x_pinmux/. The latest repository for device trees is https://github.com/beagleboard/BeagleBoard-DeviceTrees. You can recompile device trees using the instructions in the repository,
Best,
Neeraj
eldam_fr,
Thanks for the update on this issue. We are glad you were able to determine the root cause.
Best,
Neeraj
Question is being dealt with offline. Closing out the ticket here.
Best,
Neeraj
samsam,
You can find all the peripherals activated and assigned to A7 are listed in the device tree: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/linux-v4.19/osd32mp1-red.dts. The M4 is not assigned any peripherals. For CubeMX project, we recommend you start with https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/ which provides you with a minimal project that you can start with. We are first working on getting the Debian SDK and OpenSTLinux support for the RED board with a CubeMX project added later.
Best,
Neeraj
BiggTrim,
TIDA-010013 looks like a reference design to convert RGB to LVDS displays. Please see https://focuslcds.com/the-mipi-and-lvds-display-interfaces/ for an understanding of the difference between LVDS and DSI interfaces. If you need RGB to DSI interfacing, https://www.mouser.com/new/toshiba-semiconductors/toshiba-tc358778xbg-dsi/ looks like a solution. We have not verified whether this will work with AM335x.
Best,
Neeraj
geferay,
Do you observe activity on SD card interface CLK/CMD? If you are, then ROM code is correctly evaluating the boot mode, and something is going wrong after.
Since you are measuring correct voltage at the boot pins, this might not reveal much, but what is the size of pull-ups you are using on the BOOT mode pins?
Best,
Neeraj
Matthew,
Which Kernel version are you using?
If you are using a 4.19 kernel, that is probably the reason you are seeing the behavior you are seeing. The low power modes are not properly supported in this kernel. You should see the difference between the RED board and the BRK. BRK has no trouble entering a low power state as it uses 5.4 Kernel. We are working on upgrading both RED and BRK to the latest (5.10) kernel in the coming weeks. You should see a release in 9/2021.
Best,
Neeraj
geferay,
As aidancullen below states, please try and verify along with the boot mode settings(at the boot pin side of the boot mode resistors), whether the ROM code tries to get FSBL from the SD card. https://wiki.st.com/stm32mpu/wiki/STM32MP15_ROM_code_overview provides an overview of the ROM code.
Best,
Neeraj
Hey Akshay,
We could not find an opensource Linux driver for this module. It looks like you can use the M4/A7 cores to send AT commands(see manual here: https://www.u-blox.com/zh/ubx-viewer/view/u-connectXpress-ATCommands-Manual_UBX-14044127?url=https%3A%2F%2Fwww.u-blox.com%2Fsites%2Fdefault%2Ffiles%2Fu-connectXpress-ATCommands-Manual_UBX-14044127.pdf) Please contact ublox for any support they have for a driver on the Linux side or a library for the M4 core.
Best,
Neeraj
Akshay,
You are correct, unfortunately, USB1 port can only be set as USBH(Host). Please take a look at https://wiki.st.com/stm32mpu/wiki/USBPHYC_internal_peripheral for more information. You could use PA11 and PA12 for an additional USB OTG port that can be used to connect to a PC as a peripheral. Please see section 10.1.12 of the hardware getting started guide(https://www.st.com/resource/en/application_note/dm00389996-getting-started-with-stm32mp151-stm32mp153-and-stm32mp157-line-hardware-development-stmicroelectronics.pdf) for the configuration.
For the WiFi module, please take a look at the documentation provided by ublox on their website: https://www.u-blox.com/zh/product/nina-w13-series#tab-documentation-resources. You will have to contact ublox to see if they provide Linux driver support for the module.
Best,
Neeraj
-
AuthorPosts