Neeraj Dantu
Forum Replies Created
-
AuthorPosts
-
August 27, 2020 at 9:18 am in reply to: Working custom design works great for 6 months – now dead #10605
Matt,
VIN/USB power sources should be okay to power as the PMIC can decide which power input it can use. Take a look at section 8.3.9 in PMIC datasheet(https://www.ti.com/lit/ds/symlink/tps65217.pdf)
Plotting the power up sequence of the failed part will allow you to determine which power rail is failing. My suspicion is that a short on an IO pin can cause failure on VDDSHV_3V3 and that can lead to the PMIC shutting down after it tries to bring the rail up. So, you don’t necessarily have to have a short on the power rail for the power up sequence to fail. This would align with the theory that the eMMC failure leading to an IO short could be the cause for your boot fail.
Please also check the PMIC – SoC interface signals for shorts as well. They are listed here: https://octavosystems.com/app_notes/osd335x-design-tutorial/bare-minimum-boot/power-management/
Best,
Neeraj
August 26, 2020 at 12:36 pm in reply to: Working custom design works great for 6 months – now dead #10596Matt,
It looks like there are 2 separate issues here:
1. Boot log texts that don’t really cause any faulty behavior: According to Beagle, these are normal informational messages. Please see https://forum.digikey.com/t/question-for-card-did-not-respond-to-voltage-select/2763
2. Failed board:
This may be caused by a number of reasons. Note that eMMC and SD cards have a certain amount of read/write cycles they are good for. After that, they may fail randomly. We recommend you maintain a RAM based filesystem for logging and push the SD card/eMMC once in a while to reduce the wear and tear. For a crash like you described, reflashing the eMMC with a new image could be necessary as data could be corrupted.
From the power up behavior you described, a short is a likely cause. A good way to get to the bottom of this is to test the power up behavior of the failed board to determine which rail/pin is faulty. Please take a look at the power application note for power up sequence to verify: https://octavosystems.com/app_notes/osd335x-sm-power-application-note/.
Best,
Neeraj
Tobias,
Please take a look at https://github.com/STMicroelectronics/meta-st-stm32mp/blob/dunfell/recipes-kernel/linux/linux-stm32mp/README.HOW_TO.txt#L185 for compilation flags including the LOADADDR. The helper file is useful when using the Developer Package: https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package
Best,
Neeraj
yme,
The files linked are U-boot/kernel device tree sources. They cannot be used to compile TF-A.
If you are using BSP v1.2 from ST, you can use the CubeMX project from the CubeMX application note here:https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/ for minimal device tree for TF-A.
If you are using BSP v2.0, please see attached zip folder for a minimal CubeMX project. We are working on the full peripheral CubeMX project for the BRK which will be made available in coming weeks.
Best,
Neeraj
Attachments:
Will,
The current listed in the datasheet is ideally what you would limit the current of SYS_VOUT to. While it should be okay to draw 700mA, we recommend you draw the additional current from VIN_AC as it is the same voltage.
Best,
Neeraj
Beko,
Thanks for the follow up. It is interesting that the TI recommendation did not work. We will investigate. Glad you are able to bring up your design successfully! Please let us know if you have any more questions.
Best,
Neeraj
Yes, emmc v5.1 should work if you follow the guidelines in the app note linked above.
Best,
Neeraj
Coder,
A couple of things you can try from this thread: https://community.st.com/s/question/0D50X0000B6PIH1/stm32mp157cdk2-flash-didnt-work
1. Use the Windows GUI programmer
2. Add timeout to the programmer command
You could also use ‘dd’ to flash individual partitions on to the SD card.
Can you verify the USB connection between the computer and the target board?
Best,
Neeraj
We are currently working on updating our images to OpenST v2.0 and will create an CueMX file as part of this effort. Will keep you updated here.
Best,
Neeraj
Gzazo,
Yes, this is valid for eMMC v5.1.
Best,
Neeraj
Tobias,
Currently there is no CubeMX file for this board. The board device tree can be accessed here: https://github.com/octavosystems/osd32mp1-brk-device-tree.
We are planning on CubeMX based collateral around the BRK in a near future.
Best,
Neeraj
Gzazo,
Connecting A6 to VSS should not effect anything as all NC pins of the eMMC can be routed over and are physically not connected internally. RFU pins as described in the application note liked above should not be routed over.
Best,
Neeraj
Tobias,
Please check the binary file you are flashing for u-boot. From the boot log, it looks like you are using the EV1 binary file and not the board specific one you have created. The U-boot SDK does build multiple binaries for multiple boards based on the configuration in Makefile.sdk.
Please also check the board name printed on the output of the FSBL(First stage bootloader) to be the DK-2 and not EV-1. If it is not what you expect, you may not have flashed the right FSBL as well.
Also make sure you have 2 partitions (ssbl1 and ssbl2) programmed with the u-boot you generated.
Best,
Neeraj
Tobias,
Please check on your version of the CubeMX software you are using. CubeMX version 5.6 is not compatible with the developer package 2.0. Version 6.0 works with the new developer package.
Best,
Neeraj
Hey Jack,
Hopefully you were able to communicate to the PHY with the offline inputs we have provided. Please let us know if you have additional questions.
Best,
Neeraj
-
AuthorPosts