Comments on: Linux on Microblaze HOWTO (part I) https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/ Anything I found worthy to write down. Thu, 26 Mar 2026 13:15:15 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Pravin Khule https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-1113 Pravin Khule Mon, 07 Sep 2015 05:10:30 +0000 https://billauer.se/blog/?p=1589#comment-1113 thanx...... thanx……

]]> By: Denis https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-1010 Denis Tue, 14 Oct 2014 18:19:02 +0000 https://billauer.se/blog/?p=1589#comment-1010 Hi. I had similar problem with the "Cannot find MLD..." error. In my case the source of problem was an obsolete version of the SDK. Device tree files on the Xilinx`s GitHub is intended for some new 2014.x version. I had solved the problem like that: 1) Take old repository: "device-tree" (deprecated), not the new "device-tree-xlnx". Use this URL: https://github.com/Xilinx/device-tree 2) I had cloned repository using TortoiseGIT (do not download .zip!). Then I have opened its history and checked out revision, that was tagged like my SDK verion. 3) After check-out this old version there will be corresponding files: "device-tree_v2_1_0.mld" and "device-tree_v2_1_0.tcl". I had copied them into SDK folder where it intended to be. I do not sure now, it was like EDK/.../sw/lib/... there was multiple "standalone" and "xilkernel" folders there. I created folder according error messsage (where it searches for this files). Hope it helps. Hi.
I had similar problem with the “Cannot find MLD…” error.

In my case the source of problem was an obsolete version of the SDK. Device tree files on the Xilinx`s GitHub is intended for some new 2014.x version.

I had solved the problem like that:

1) Take old repository: “device-tree” (deprecated), not the new “device-tree-xlnx”. Use this URL: https://github.com/Xilinx/device-tree

2) I had cloned repository using TortoiseGIT (do not download .zip!). Then I have opened its history and checked out revision, that was tagged like my SDK verion.

3) After check-out this old version there will be corresponding files: “device-tree_v2_1_0.mld” and “device-tree_v2_1_0.tcl”. I had copied them into SDK folder where it intended to be. I do not sure now, it was like EDK/…/sw/lib/… there was multiple “standalone” and “xilkernel” folders there. I created folder according error messsage (where it searches for this files).

Hope it helps.

]]> By: Jae https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-962 Jae Tue, 22 Jul 2014 19:47:25 +0000 https://billauer.se/blog/?p=1589#comment-962 when I execute the command below on Xilinx Shell, "libgen -hw system.xml -lp device-tree -pe microblaze_0 -log libgen.log system.mss" I get an error saying, "Cannot find MLD file device-tree_v2_1_0.mld for the os device-tree 0.00.x" Do you have any idea on this? when I execute the command below on Xilinx Shell,
“libgen -hw system.xml -lp device-tree -pe microblaze_0 -log libgen.log system.mss”

I get an error saying,
“Cannot find MLD file device-tree_v2_1_0.mld for the os device-tree 0.00.x”

Do you have any idea on this?

]]> By: eli https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-930 eli Fri, 28 Mar 2014 10:45:19 +0000 https://billauer.se/blog/?p=1589#comment-930 Hi, The SPI flash has 8 MB of memory, which is more than enough for a Linux kernel + an initramfs image with some application. Besides, Linux can mount its root filesystem from the LAN using nfs. So if you insist on this not-so-impressive board, you can run whatever you want on it. Not that I understand why you bother... Anyhow, uCLinux is for processors with no MMU, and has nothing to do with the memory's size, so I suggest dropping that. What I would do if I were you is first to see that I can compile a simple standalone (no Linux) "Hello, world" program. Then try to get U-boot compiled and booted into the system (I expect this to be the difficult part). And then get the device tree right and boot Linux. It's not going to be easy, I can tell you that. Did I mention partitioning the SPI flash? (Don't ask me how to do it) Hi,

The SPI flash has 8 MB of memory, which is more than enough for a Linux kernel + an initramfs image with some application. Besides, Linux can mount its root filesystem from the LAN using nfs. So if you insist on this not-so-impressive board, you can run whatever you want on it. Not that I understand why you bother…

Anyhow, uCLinux is for processors with no MMU, and has nothing to do with the memory’s size, so I suggest dropping that.

What I would do if I were you is first to see that I can compile a simple standalone (no Linux) “Hello, world” program. Then try to get U-boot compiled and booted into the system (I expect this to be the difficult part). And then get the device tree right and boot Linux.

It’s not going to be easy, I can tell you that. Did I mention partitioning the SPI flash? (Don’t ask me how to do it)

]]> By: jerry https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-929 jerry Fri, 28 Mar 2014 08:19:52 +0000 https://billauer.se/blog/?p=1589#comment-929 Hi, Thanks for your answering! My goal is to install a linux to microblaze on SP601.As you can see , there is not enough room to realize.So i 'm now trying uclinux but the interrupt configuration is too complex to understand. And i really don't know what to do now.Nothing similar to my task has been found on the Internet.Can you help me to finish it if you are available? thank you very much! Hi,
Thanks for your answering!
My goal is to install a linux to microblaze on SP601.As you can see , there is not enough room to realize.So i ‘m now trying uclinux but the interrupt configuration is too complex to understand.
And i really don’t know what to do now.Nothing similar to my task has been found on the Internet.Can you help me to finish it if you are available?
thank you very much!

]]> By: eli https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-928 eli Thu, 27 Mar 2014 10:33:11 +0000 https://billauer.se/blog/?p=1589#comment-928 Hi, This guide is more than two years old, and both the kernel and the other tools have made a long way. As for SP601, it doesn't have an SystemACE interface, so the boot process will have to be completely different. Doesn't Xilinx supply information about how to boot from the QSPI flash? Hi,

This guide is more than two years old, and both the kernel and the other tools have made a long way.

As for SP601, it doesn’t have an SystemACE interface, so the boot process will have to be completely different. Doesn’t Xilinx supply information about how to boot from the QSPI flash?

]]> By: jerry https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-927 jerry Thu, 27 Mar 2014 05:14:40 +0000 https://billauer.se/blog/?p=1589#comment-927 i'm now doing the same thing . Is this HOWTO availiable with SP601? and i have problem with "Setting up the processor",for i can't find the options you descirbed. thank you very much for your sharing! i’m now doing the same thing . Is this HOWTO availiable with SP601? and i have problem with “Setting up the processor”,for i can’t find the options you descirbed.
thank you very much for your sharing!

]]> By: Dr.Fuzzy https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-923 Dr.Fuzzy Fri, 14 Feb 2014 17:04:31 +0000 https://billauer.se/blog/?p=1589#comment-923 Implemented the MB system and built the Kernel sources (xilinx_v3.0) according to your guide on a SP605, the boot process seems to start but goes nowhere after the following message is displayed: early_printk_console is enabled at 0x40600000 Ramdisk addr 0x00000003, Compiled-in FDT at 0xc02888c8 The only suspicious warning appears on the SDK when I build the device-tree: WARNING:EDK - : console ip RS232_Uart_1 was not found. This may prevent output from appearing on the boot console. Any ideas? Implemented the MB system and built the Kernel sources (xilinx_v3.0) according to your guide on a SP605, the boot process seems to start but goes nowhere after the following message is displayed:

early_printk_console is enabled at 0x40600000
Ramdisk addr 0x00000003, Compiled-in FDT at 0xc02888c8

The only suspicious warning appears on the SDK when I build the device-tree:
WARNING:EDK – : console ip RS232_Uart_1 was not found. This may prevent output
from appearing on the boot console.

Any ideas?

]]> By: Sandeep https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-910 Sandeep Sat, 04 Jan 2014 03:28:48 +0000 https://billauer.se/blog/?p=1589#comment-910 I have posted my question @xilinx forums , no reply till now, Thanks Sandeep I have posted my question @xilinx forums , no reply till now,

Thanks
Sandeep

]]> By: eli https://billauer.se/blog/2011/08/linux-microblaze-howto-tutorial-primer-1/comment-page-1/#comment-909 eli Fri, 03 Jan 2014 14:20:15 +0000 https://billauer.se/blog/?p=1589#comment-909 I've never read through that script, so I can't help you. I suggest contacting Xilinx' support on this. I’ve never read through that script, so I can’t help you. I suggest contacting Xilinx’ support on this.

]]>