Neeraj Dantu

Forum Replies Created

Viewing 15 posts - 361 through 375 (of 601 total)

← 1 2 3 … 24 25 26 … 39 40 41 →

Author

Posts
February 9, 2021 at 9:12 am in reply to: Debian Source and Steps for Compilation #11209
Neeraj Dantu
Moderator
Leox,

We will release the Debian build system in the coming weeks along with some documentation. Please keep a look out for announcements.

Best,

Neeraj
February 6, 2021 at 2:35 pm in reply to: Linux Device Tree for OSD32MP1-RED #11205
Neeraj Dantu
Moderator
azdagron,

We will be releasing the device tree for OSD32MP1-RED along with the board over the next week. Please keep an eye on https://octavosystems.com/octavo_products/osd32mp1-red/.

Best,

Neeraj
February 5, 2021 at 11:30 am in reply to: C-SIP RED Platform, pullups to SYS_VDD1_3P3V #11203
Neeraj Dantu
Moderator
Scott,

There is little significance to these pull-up voltage source. It is just much easier to pull-up these signals with a SYS_VDD1_3P3V power plane vs SYS_VDD3_3P3V. Please see OSD3358-SM-RED layout: https://octavosystems.com/octavo_products/osd3358-sm-red/#Design%20Files%20-%20OSD335x-SM

Best,

Neeraj
February 3, 2021 at 11:26 am in reply to: Powered by Battery Only #11198
Neeraj Dantu
Moderator
Marton,

Thanks for letting us know that it works.

The LDO4 of the PMIC is connected to the ENABLE pin of the TL5209 LDO and powers the (VDDA3P3V_USB0 + VDDA3P3V_USB1) pins of the processor. These pins power the USB PHY. Based on the Schematic Checklist(https://www.ti.com/lit/an/sprabn2a/sprabn2a.pdf), disconnecting these should not be an issue for the processor. However, the USB ports will not function in this configuration.

Best,

Neeraj
February 1, 2021 at 11:56 am in reply to: Powered by Battery Only #11195
Neeraj Dantu
Moderator
Marton,

That is correct. For 1.8V IO, you will need to connect VDDSHVx pins to SYS_VDD_1P8V. With the IO pins powered by VDD_1P8V, there should be no leakage between SYS_VDD1_3P3V and SYS_VDD3_3P3V.

Note that you will have utilize level translators as necessary to communicate with peripherals that do 3.3V IO only. An external Battery management solution such as one on Beaglebone Blue: https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf could also be an option.

Best,

Neeraj
February 1, 2021 at 9:13 am in reply to: Boot Issues from eMMC #11194
Neeraj Dantu
Moderator
Joe,

Appreciate the update. Please let us know if you have more questions.

Best,

Neeraj
January 27, 2021 at 11:09 am in reply to: Boot Issues from eMMC #11170
Neeraj Dantu
Moderator
Adam,

The Flashing script should provide a good error message if something is going wrong. Please verify the correct mmcblk’X'(corresponding to eMMC) is being flashed.

I would also boot the board without connecting the LCD to remove any unknown pull-up/pull-down messing with the boot configuration.

As long as you are flashing the patched SPL/U-Boot(with EEPROM ID patches), you should see boot-up messages on the console. That is one more thing to check.

Best,

Neeraj
January 25, 2021 at 6:53 pm in reply to: Boot Issues from eMMC #11156
Neeraj Dantu
Moderator
ABierman1986,

A couple of things:

1. See if you have additional components on the LCD interface. You can probe the SYSBOOT pins(at boot-up) to verify that the boot mode is being set correctly. If there is another device on the LCD interface that is pulling the SYSBOOT pins differently(Note that these pull-ups / pull-downs are weak), the ROM code might be probing the wrong boot interfaces.

2. Verify that you have a bootable image in the eMMC. You can boot via SD card and mount the partitions of the eMMC to check whether it has been flashed correctly. Also verify that you are flashing the patched SPL and U-Boot that skip EEPROM ID verification.

I missed the fact that you are using a C-SiP. As the eMMC is internal, you would not be able to probe the CLK line.

Best,

Neeraj
- This reply was modified 4 years, 2 months ago by Neeraj Dantu.
January 25, 2021 at 10:52 am in reply to: C-SIP RED Platform, reset supervisor VCC #11155
Neeraj Dantu
Moderator
Scott,

SYS_VDD1_3P3V is directly powered by the SYS_VOUT output of the PMIC. SYS_VOUT is switched from all the inputs of the PMIC(AC, USB, BAT). SYS_VDD1_3P3V was chosen as it is closest to SYS_VOUT, which is also independent from the internal power rails of the PMIC.

Best,

Neeraj
January 21, 2021 at 2:41 pm in reply to: Kernel Panic at Shutdown #11145
Neeraj Dantu
Moderator
ryanclem,

Please take a look at this thread for the exact issue: https://octavosystems.com/forums/topic/kernel-panic-on-shutdown/

Best,

Neeraj
January 20, 2021 at 1:23 pm in reply to: No kernel modules loaded after installing a new kernel. #11143
Neeraj Dantu
Moderator
Ivan,

Please take a look at https://www.digikey.com/eewiki/display/linuxonarm/OSD3358-SM-RED for a reference procedure to build image for OSD3358-SM-RED with bb-kernel. This was created by Robert Nelson as well. Please make sure you are building/copying kernel modules: https://www.digikey.com/eewiki/display/linuxonarm/OSD3358-SM-RED#OSD3358-SM-RED-CopyKernelModules.

The Debian 9.1 image from the website should work on the board without issue. You might try re-flashing or use another SD card. To see whether the interface is working, you can stop boot at U-Boot and use the mmc command(http://www.denx.de/wiki/view/DULG/UBootCmdGroupMMC) to verify the MMC interfaces and memory devices on them.

Please let us know if you have further questions.

Best,

Neeraj
January 18, 2021 at 10:48 am in reply to: Boot Issues from eMMC #11138
Neeraj Dantu
Moderator
ABierman1986,

The issue probably is boot mode setting. If the MMC interface on which the eMMC is present is not in the “Boot sequence” for a particular boot setting, the ROM code will not poll the eMMC for boot image.

Please take a look at Table 26-7 of AM335x Technical Reference Manual(https://www.ti.com/lit/ug/spruh73q/spruh73q.pdf) for boot mode settings and corresponding Boot sequences. Make sure the the MMC interface the eMMC is on is in the boot sequence for the SYSBOOT pin configuration you have or change the SYSBOOT configuration to include the MMC interface.

If the MMC interface is in the Boot Sequence, check whether the ROM code gets stuck on an interface with higher priority. You can probe the MMC_CLK line to verify whether ROM code is probing the eMMC for a valid image.

Best,

Neeraj
January 13, 2021 at 10:51 am in reply to: I2C4 strange behavior #11119
Neeraj Dantu
Moderator
ramio,

Glad you could solve your issue. Please let us know if you have more questions.

Best,

Neeraj
December 22, 2020 at 12:44 pm in reply to: _MinialConfig build instruction for new MXCube (v6.1.1) #11056
Neeraj Dantu
Moderator
Kevin,

We were able to generate code on CubeMX 6.1.1 with no issues for the minimal project. Please make sure to chose “migrate” when you first open the project and CubeMX prompts you.

CubeMX will also download the latest firmware package when it is generating the code. You can chose to install Cube FW 1.3 there.

Best,

Neeraj
December 22, 2020 at 10:19 am in reply to: Exception during first boot #11055
Neeraj Dantu
Moderator
dcallahan,

As aedancullen said, errors during TF-A execution indicate a device tree configuration issue. Particularly, please take a look at clock tree configuration as described here: https://community.st.com/s/question/0D53W000005qRjZSAU/cannot-boot-up-custom-board-which-based-on-stm32mp157cdk2-only-get-message-from-uart-panic-at-pc-0x2ffdc323-exception-mode0x00000016-at-0x2ffda000

We provide a minimal CubeMX project that you can also modify in this application note: https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/

Best,

Neeraj
Author

Posts

Viewing 15 posts - 361 through 375 (of 601 total)

← 1 2 3 … 24 25 26 … 39 40 41 →