RTEMS on Zynq Microzed

Tue Feb 2 14:57:08 UTC 2016

Hi,

I hope it's not a problem to dig up this old thread.

Am 2015-10-01 15:54, schrieb Webb, Jeffrey A.:
> That is basically the process I followed, although I used the Xilinx
> xsdk tool.  (I did not know about the open source tool -- I will try
> it when I get a chance.  Do you still use the Xilinx tools to generate
> the fsbl, or something else?)  There seems to be a somewhat long delay
> when I boot up my RTEMS application the first time, and there is some
> issue with the serial port driver that causes missing characters at
> first.   I usually push the reset button, and things clear up on
> subsequent reboots.  Anyway, it sounds like there may need to be some
> changes to the bsp for the microzed, or at least some configuration
> parameters.  Did you look in the BSP configure script for options like
> clock rates that may need to be changed?  I had to change the
> peripheral clock configure option to get the ticker.exe tasks to run
> at the proper rate, although this didn't seems to alter the baud rate
> settings.  I might be able to get my hands on a microzed, but it will
> probably be a couple weeks before I
>   have time to try that.
> 

We have the same problem with the ticker-example here.
I found the configure option for the periphal clock, but I was wondering 
what value I need to set it to.
If I take a look at the clock configuration for the zync in Vivado I 
get:

Input frequency:  33.333 MHz
ARMPLL         : 666.666687 MHz

That seems to be in line with the standard bsp-configuration.
We also compared the settings with the same project set up for the 
normal Zedboard and they look the same.
It would be a great help if you could push us in the right direction.

Cheers,

    Jan

> ----- Original Message -----
>> Hi Jeff,
>> I've tried the following steps:
>> 
>>  - cloned https://github.com/antmicro/zynq-mkbootimage.git
>>  - create a bif file with fsbl.elf, fpga.bit, u-boot.elf (tried both 
>> the
>> unstripped and stripped version of hello.exe)
>>  - I renamed hello.elf into u-boot.elf and created BOOT.BIN
>>  - copied BOOT.BIN to the fat partition of the microSD
>> 
>> Nothing comes out of the terminal window:I repeadetly see the blue led 
>> for
>> a short period (I think is indicating the bitstream being loaded), 
>> followed
>> by a shot blink of a red led.
>> Am I doing anything wrong?
>> 
>> thank you for your help,
>> Davide
>> 
>> 
>> 2015-09-30 19:49 GMT+02:00 Jeff Webb <jeff.webb at nta-inc.net>:
>> 
>> > On 09/30/2015 10:34 AM, Davide Viti wrote:
>> >
>> >> Hi,
>> >> I own a Microzed board and recently managed to boot it using buildroot
>> >> using a recent (2015.07) uboot and the Zedboard DTS shipped in the Xilinx
>> >> repository of the linux kernel.
>> >> Given the above, I assumed I cuold try RTEMS on the Microzed, using the
>> >> Zedboard BSP.
>> >>
>> >> I successfully built the toolchain and the BSP (xilinx_zynq_zedboard) out
>> >> of the latest version of the git repositories and I'm trying to boot the
>> >> hello.exe sample following these steps:
>> >>
>> >> arm-rtems4.11-objcopy -R -S -O binary hello.exe hello.bin
>> >> mkimage -A arm -O rtems -T kernel -C none -n "RTEMS Application" -d
>> >> hello.bin hello.img
>> >>
>> >> I write the hello.img file on the microSD along with:
>> >>
>> >>   - BOOT.BIN
>> >>   - system.bit
>> >>   - u-boot-dtb.img
>> >>
>> >> and u-boot starts fine:
>> >>
>> >> ---------------------------
>> >> U-Boot SPL 2015.07 (Sep 25 2015 - 09:24:38)
>> >> mmc boot
>> >> reading system.dtb
>> >> spl_load_image_fat_os: error reading image system.dtb, err - -1
>> >> reading u-boot-dtb.img
>> >> reading u-boot-dtb.img
>> >>
>> >>
>> >> U-Boot 2015.07 (Sep 25 2015 - 09:24:38 +0200)
>> >>
>> >> Model: Zynq MicroZED Board
>> >> I2C:   ready
>> >> DRAM:  ECC disabled 1 GiB
>> >> MMC:   zynq_sdhci: 0
>> >> Using default environment
>> >>
>> >> In:    serial
>> >> Out:   serial
>> >> Err:   serial
>> >> Model: Zynq MicroZED Board
>> >> Net:   Gem.e000b000
>> >> Error: Gem.e000b000 address not set.
>> >>
>> >> zynq-uboot> fatload mmc 0 0x1000000 hello.img
>> >> reading hello.img
>> >> 1039120 bytes read in 107 ms (9.3 MiB/s)
>> >> zynq-uboot> bootm 0x1000000
>> >> ## Booting kernel from Legacy Image at 01000000 ...
>> >>     Image Name:   RTEMS Application
>> >>     Image Type:   ARM RTEMS Kernel Image (uncompressed)
>> >>     Data Size:    1039056 Bytes = 1014.7 KiB
>> >>     Load Address: 00000000
>> >>     Entry Point:  00000000
>> >>     Verifying Checksum ... OK
>> >>     Loading Kernel Image ... OK
>> >> ## Transferring control to RTEMS (at address 00000000) ...
>> >>
>> >> Could you please give me some advices?
>> >> Are there any known success stories with this board
>> >>
>> >
>> > I have RTEMS running on a ZedBoard, but I have not tried the microzed
>> > yet.  I did not use u-boot, however.  I built a new BOOT.BIN file using the
>> > SDK that consisted of the fsbl, fpga bitstream, and my RTEMS elf
>> > application.  (Basically, I just replaced u-boot with my RTEMS
>> > application).
>> >
>> > -Jeff
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > users mailing list
>> > users at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
>> >
>> 
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users