How can I remove all Bootloader output messages on Colibri IMX6DL Module

Hi~. I don’t want any boot message through serial port(COM1) while Colibri IMX6DL module is booting.
So, I set the bootloader config like this

set boot.silent = 1
save boot
and then reboot.
I expected there are no messages on serial port. But Bootloader still print some messages like under.

Toradex Bootloader 1.0 for Colibri Built Mar 23 2016
Board: Colibri iMX6 DualLite 512MB
CPU is running at 984000MHz.
Using eMMC boot partition (size: 4096 sectors).
Loading EBoot configuration…
16 sectors of configuration data loaded form boot.

What do I have to do to remove whole boot message?..

The boot.silent option or the option to change the serial port used for bootloader messages is not yet supported in the i.mx6 bootloader, we will put this in our roadmap soon, but we currently have no due date for this feature.

I hope that you will put this issue in your roadmap as soon as possible.

We have added the implementation of boot.silent feature in our roadmap, but it is yet to be scheduled.
roadmap link

Thank you to add this issue in your roadmap.

I have another question. If i buy BootLoader Customize Kit and then use that, Could I get the result what I want.

Let me just try and get back to you soon.


We just tested by using bootloader customizer kit and compiling it with platform builder you can disable completely serial output on iMX6 module. This can solve your issue.

Also, in your bootloader customization, it would be good if you provide a way to re-enable serial output, maybe by using GPIO, this will be helpful during debugging.

Hi~!. Thank you for your testing.

Could you please let me know How to buy Bootloader Customizer Kit and Bootloader Customizer Kit’s price.

And I’ve known that Bootloader Customizer Kit support customization via message sent to a callback function. Can I recompile the Bootloader with platform builder, if i’ll get Bootloader Cusomizer Kit ?


For Bootloader Customizer kit we charge 8 support hours.

We implemented the bootloader kit as a callback function that is called multiple times during the boot process, more or less like a Window Procedure in Windows.

The idea behind this is that in this way adding new “hook” points inside the bootloader will not require any change in existing integration, not even rebuilding and adding a dummy stub.
When you don’t process a message you can just return 0, this will let the bootloader behave in the standard way.

The downside is that you’ll have a long switch statement (obviously it may be splitted in functions) and that you may need to cast input parameters for some of the sub-functions (more or less what happens with LPARAM in Windows).

Since the loader is built by linking the blkit and another static lib containing the bootloader code you’ll be able to access function, globals etc. inside it.
For example to change configuration parameters etc.

Gpios can be controlled using the same API we implemented for apps. Only interrupts are not supported.
I included an header file with the “messages” that I already implemented. Let me know if you see something missing or something that may be improved.


  1. Usually, we don’t recommend using the bootloader kit if not really necessary, as we have added your issue in the roadmap. If you can wait for some time then it would be better.
  2. If you want us to implement bootloader silent feature at earliest in that case we would ask for 4 support hours and within ONE week after successful payment, we can build a new bootloader having bootloader silent feature implemented.
  3. The bootloader must be build by WEC7 platform builder(it uses ARMv4 assembly and the WEC2013 assembler does weird things on it).

Is the boot.silent option supported now? I tried the default WEC 2013 1.3b4 image and I was unable to suppress bootloader output. Are there additional settings to disable bootloader output on the splash screen? My system is on a Colibri iMX6

boot.silent removes messages on the serial port and I can confirm that it works on bootloader 1.3b4.
If you want to disable messages also on the splash screen you should set ss.dbginfo to 0 using this procedure:

  • connect on the serial console on UARTA (115200bps,8N1)
  • press space at power-up/reset to enter the boot menu
  • press X to enter the console
  • type: set ss.dbginfo 0
  • type: save ss
  • reboot

Thank you! Setting ss.dbginfo to 0 was what I was missing.