- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
- Home
- :
- i.MX Forums
- :
- i.MX Processors
- :
- Debian 12 SDK
Debian 12 SDK
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We have read that NXP has released a new version based on Debian 12 (kernel 6.6.3) for i.MX processors
We want to use it in our own design based on i.MX8m plus, so we need to port uboot and kernel.
Could you please help us to find out how to get the toolchain, rootfs, uboot and kernel source code ?
kind regards and thank you
Angel
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chavira,
Thank you very much for your help.
This could be an option, but we are also considering building the toolchain from NXP release 6.1.22_2.0.0, as this release includes gcc 12.2.
Both Debian 12 and gcc 12.2 include glibc 2.36, and this is an important point when our customers need to cross-compile their FW.
Best regards
Angel
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI @AngelF!
Thank you for contacting NXP Support!
You can see all the documentation available for Debian in the links below:
https://www.nxp.com/docs/en/user-guide/UG10155.pdf
Best Regards!
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chavira,
Thank you very much for your help.
My host is ubuntu 24.04, so I follow steps and now I have everything ready to generate Debian images inside a docker container.
Now we need to be able to offer our customers a toolchain so that they can cross-compile their applications in standalone mode aoutside the container. So we would like to be able to generate the toolchain in the same way as we generate it with yocto (populate_sdk command).
How can we get the toolchain using Flexbuild?
Best regards and thank you
Angel
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI @AngelF!
According with previous cases of the same topic.
After installing flex-builder and setting up compiling environment, you could find toolchain(GCC) is deployed in /usr/bin folder.
$ which aarch64-linux-gnu-gcc
/usr/bin/aarch64-linux-gnu-gcc
Glibc is deployed in /usr/aarch64-linux-gnu/lib/ folder.
If the tool chain doesn´t exist please let me know.
Best Regards!
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chavira,
Yes, I can find aarch64-linux-gnu-gcc and glibc in the container, but I was trying to generate the whole toolchain instead of copying file by file.
When installing NXP yocto firmware, we can use the populate_sdk command to generate the full toolchain and we can deploy to customers in a "professional" way.
So, with Debian 12, is it possible to generate a complete toolchain or do we have to go file by file?
Best regards and thank you
Angel
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @AngelF!
Talking with the internal team I got the next answer:
To cross-compile applications in standalone mode, users can use aarch64-linux-gnu-gcc compiler, which is installed by command "sudo apt-get install -y crossbuild-essential-arm64 gcc-aarch64-linux-gnu g++-aarch64-linux-gnu binutils-aarch64-linux-gnu" on Ubuntu host.
Best Regards!
Chavira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chavira,
Thank you very much for your help.
This could be an option, but we are also considering building the toolchain from NXP release 6.1.22_2.0.0, as this release includes gcc 12.2.
Both Debian 12 and gcc 12.2 include glibc 2.36, and this is an important point when our customers need to cross-compile their FW.
Best regards
Angel
