Microblaze wiki page
Sites with limited access
Latest code is available at GIT server. http://git.monstr.eu/git/gitweb.cgi
Before sending your patches please do:
For working with FDT kernel you need to have DTS file which describes your Microblaze SoC.
This chapter is only for user which wants to update BSP.
For creating DTB which is passing to Linux kernel you need DTC
Please choose TOP BSP and set values there.
Before you start to build hardware you should choose our booting strategy. I would like to give you some options what you can choose.
|Memory consumption||Depends on your features||8k BRAM||>128k|
|Functions||Depends on what you want to develop||Copy SREC to memory, Boot kernel from Flash - reading||Full Flash, System ACE, Network-emaclite,emac,ll_temac, gpio, booting all kernel and a lot of others|
|Time of developing||Depends on your features but it is huge in compare to standard solution||-||Only adding features which are not there|
|Source code maintaining||Customer must care about||PetaLogix||me|
|Stability||uknown||~99.9% stable||~99% stable - Depends on setting|
You can use our own bootloader in all variants but be sure you have time and developer who will do it. Keep in your mind that if you want to use it after some years again someone take care about. Please counted how much money this option cost. You will not have any support of it.
mkimage executable files
Kernel can be place to almost every position. There are some limitation like. The last instruction of kernel cannot exceed limit which is placed approximately 16 kB from the end of memory. You have to calculate with the size of file system too.
From the lowest to the highest priority
|Rootfs on SystemACE||root=/dev/xsa2|
|NFS rootfs||root=/dev/nfs rw nfsroot=192.168.0.102:/tftpboot/rootnfs|
|Console on uart16550 or old uartlite||console=ttyS0,115200|
|Console on uarlite||console=ttyUL0,115200|
|Turn off console||silent=off|
|Single user mode||single|
|tmpfs as root||devfs=mount rw rootfstype=tmpfs root=/dev/ram|
|setup ipaddr by dhcp||ip=dhcp|
|setup static ipaddr||ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>|
There is second way how to read Linux kernel log buffer via XMD. This features is not available for free users. Here is the log to show you how this options works. There are new built-in features in xmd called log. The script find-out log buffer from latest Linux kernel code and you can just type log command to show whole log buffer.
ori r10, r0, 0x12345678 addik r11, r0, r0_ram + 0x300 addik r12, r0, r0_ram + 0x304 sb r10,r0,r11 sbr r10,r0,r12 XMD% mrd 0xd02b602c 10 D02B602C: 00000078 D02B6030: 78000000 D02B6034: 00000000
ori r10, r0, 0x12345678 addik r11, r0, r0_ram + 0x300 addik r12, r0, r0_ram + 0x304 sh r10,r0,r11 shr r10,r0,r12 XMD% mrd 0xd02b602c 10 D02B602C: 00005678 D02B6030: 78560000 D02B6034: 00000000
ori r10, r0, 0x12345678 addik r11, r0, r0_ram + 0x300 addik r12, r0, r0_ram + 0x304 sw r10,r0,r11 swr r10,r0,r12 XMD% mrd 0xd02b602c 10 D02B602C: 12345678 D02B6030: 78563412 D02B6034: 00000000