Neeraj Dantu
Forum Replies Created
-
AuthorPosts
-
Matt,
We have observed this as well. It does not seem to be related to the dev board as most USB ports work just fine and some don’t.
Best,
Neeraj
Khan,
You can use the images that have an extension “LXQT” in the Older Debian images section of the software images page: https://beagleboard.org/latest-images. There are more flavors and currently tested images at https://rcn-ee.com/rootfs/.
There are several resources to get started on QT. Please take a look at http://exploringbeaglebone.com/chapter13/ from Exploring Beaglebone by Derek Molloy. There are several videos to walk you through the steps.
Official QT documentation for Beaglebone Black can be found here: https://doc.qt.io/archives/qt-5.8-devicecreation/qtee-supported-platforms.html.
Best,
Neeraj
Orocle,
There are 3 SPI ports enabled on OSD32MP1-BRK. Please take a look at the pinout section of the Getting Started Guide for the BRK board for specific pin locations here: https://octavosystems.com/app_notes/osd32mp1-brk-getting-started/#pin. They are also highlighted in the device tree here: https://github.com/octavosystems/OSD32MP1-BRK-device-tree/blob/master/linux-v5.4/stm32mp157c-osd32mp1-brk.dts#L1021.
Best,
Neeraj
We will update the SDK to be compatible with a newer version of the OpenSTLinux distribution sometime in Q2 of this year.
Best,
Neeraj
Hey Rishi,
Please review this thread from ST forums: https://community.st.com/s/question/0D53W00000cxRieSAE/wakeup-on-gpio-in-linux-on-stm32mp1.
You should be able to set GPIO wakeup in CubeMX and generate the device tree you need from there. Please also take a look at https://wiki.st.com/stm32mpu/wiki/How_to_define_your_low-power_strategy and https://wiki.st.com/stm32mpu/wiki/Power_overview.
Best,
Neeraj
Khan,
QT is a good option for UI development. Couple of other options to consider:
– TI SDK Matrix GUI: http://software-dl.ti.com/processor-sdk-linux/esd/docs/04_03_00_05/linux/Examples_and_Demos.html
– Storyboard from Crank Software: https://blog.cranksoftware.com/try-it-now-beaglebone-black-demo-image/
Best,
Neeraj
Carlos,
You are right. matrix-keymap is used to define function keys rather than setup a GPIO matrix keypad. CONFIG_INPUT_MATRIXKMAP should also be set to use the function mapping tool for the matrix keymap.
Coming to your implementation, please try and simplify your declaration:
– Get rid of all unnecessary configuration like drive-inactive-cols and wakeup-source. You can add them later after you get the base device tree working for the keymap.
– Make use of proper node referencing as shown in https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt. I am unsure whether your hex codes reference the correct GPIO nodes in the device tree.
– A good example I found: https://blog.gegg.us/2017/08/a-matrix-keypad-on-a-raspberry-pi-done-right/ but note the difference in GPIO node notation for MP1(example: https://github.com/STMicroelectronics/linux/blob/v5.10-stm32mp/arch/arm/boot/dts/stm32mp157c-dk2.dts#L92).
Best,
Neeraj
Carlos,
Looks like your device tree might be a little out of date. Please take a look at device tree bindings corresponding to CONFIG_INPUT_MATRIXKMAP here: https://www.kernel.org/doc/Documentation/devicetree/bindings/input/matrix-keymap.yaml. CONFIG_KEYMAP_MATRIX is from an older version of the kernel.
If CONFIG_INPUT_MATRIXKMAP option if a ‘y’, you should not have to recompile the kernel. Here is the driver that is compiled: https://github.com/STMicroelectronics/linux/blob/v5.10-stm32mp/drivers/input/matrix-keymap.c.
Best,
Neeraj
Rishi,
Based on the battery output voltage, you might have to configure VDD to be 1.8V instead of 3.3V. This is recommended if you are using a battery according to the PMIC datasheet. Please take a look at the Power System Overview for OSD32MP1: https://octavosystems.com/app_notes/osd32mp1-power-system-overview/.
Best,
Neeraj
Carlos,
– It would be cleaner to edit the device tree you are booting instead of applying an overlay
– Please make sure that you have proper pinmux defined in pinctrl node
– Make sure you have kernel config that enables the matrix keypad(CONFIG_KEYPAD_MATRIX)
Best,
Neeraj
Rishi,
The Boost and switches on STPMIC1A cannot be turned ON automatically. They have to be turned ON either during boot or after. You can do this by setting the enabled bit on in the BST_SW_SR register of the PMIC. Please see the PMIC datasheet for more information: https://www.st.com/resource/en/datasheet/stpmic1.pdf.
Best,
Neeraj
Andreas,
Apologies for the delayed reply. I don’t see any images in the post.
Please checkout this guide: https://octavosystems.com/forums/topic/getting-started-with-osd32mp1-brk-st-link-jtag-interface/ for reference on how to connect to the BRk via ST-Link.
Best,
Neeraj
Jack,
The config that we use and have found that works well is from beaglebone.org. Please take a look at https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black for image build help and rcn-ee build script used in the page: https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.14.y/build_kernel.sh.
I would diff the omap2plus vs the beagle defconfig to see if you can add to the omap2plus for your custom kernel build.
best,
Neeraj
Akshay,
That should work as long as you have all the features you need in U-Boot. Please check the SD card detect declaration in CubeMX generated device tree and make sure that it is the same pin as the CD pin connected in the BRK schematics. I suspect this is preventing the board boot.
Best,
Neeraj
Carlos,
Apologies for the late reply. OSD32MP1 is connected to the HDMI Framer via I2S interface for Audio. So, the RED board does support audio through HDMI.
There are no audio codecs on the RED board. If you are looking for a codec implementation, please take a look at STM32Mp157c-DK2(https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html). OSD32MP1 version of this board is available as a reference design here: https://octavosystems.com/octavo_products/osd32mp15x/#Reference%20Designs.
Best,
Neeraj
-
AuthorPosts