Experience with vendor's tools

[jefry876]

Hi guys, I am wondering what's your experience with using vendor's tools while working on their hardware? Let's say we talk about something like Layerscape series from NXP or STM32MP1 series. I've been working on a board based on one of the NXP's Layerscape SoC and I can't wrap my hand around the fact that the only tool they provide to bringup and verify eg. DDR is **bleep**ty IDE based on Eclipse. I mean, given the quality of this tool I wouldn't complain if they provided it for free but they charge hell a lot of money for a license. Want to learn how to do this or that using their IDE? Good luck, "best I can do" is, mostly not 100% accurate outdated, partial documentation, forum where you will always get an answer, that somebody will handle this and 240p video where you can barely see what's on the screen. I hope that I will only use it for DDR bringup and validation and will manage to do the rest without this tool. What's your experience with other vendors? How about TI? I've seen some tools from ST and they really looked much simpler but I don't have any practical experience.

[Bio_TICFSL]

Hello,

The Eclipse base is aging, the DDR tooling (DDR Stress Test Tool) is functional but clunky, and the licensing cost vs. quality ratio is a common complaint in embedded communities. The documentation gap is real — AN (Application Notes) are often the better resource than the official tool docs. Many engineers use it purely for DDR PHY init/training as you plan, then move on.

Practical Tips for NXP Layerscape DDR Bringup

Since you're stuck with it for now:

• The DDR Stress Test Tool standalone binary (separate from CodeWarrior) is sometimes available and lighter to use.
• NXP's i.MX/Layerscape community on GitHub has reference DDR configurations that can shortcut a lot of the tool-guided work.
• LSDK (Layerscape SDK) scripts sometimes expose DDR init parameters more transparently than the IDE.

Regards