Re: [microblaze-uclinux] A few small things which might be bugs

[John Williams <john.williams@xxxxxxxxxxxxx>]

Hi Marco,

Thanks for your email, comments inline below.

On Fri, Mar 20, 2009 at 9:38 PM, Hoefle Marco
<Marco.Hoefle@xxxxxxxxxxxxx> wrote:

> first of all I want to thank you for the good work in the past. We are
> really happy with petalogix as it eases SoC software designs a lot.

Great  to hear - thanks for the feedback.

> Yesterday I checked out the latest petalogix sources and used it with one of
> our project. We use EDK 10.1 SP3 on a Debian Lenny system.
>
> I had to modify a few things to get u-boot working:
>
> in
> /software/petalinux-dist/u-boot/include/configs/petalogix-microblaze-auto.h.template
>
> I changed:
> #ifdef CONFIG_UARTLITE
> by
> #ifdef CONFIG_SERIAL_UARTLITE
>
> and
>
> #define CONFIG_SERIAL_BASE      CONFIG_STDINOUT_BASEADDR
> by
> #define CONFIG_SERIAL_BASE      CONFIG_XILINX_UARTLITE_0_BASEADDR
>
> in /software/petalinux-dist/u-boot/drivers/serial_xuartlite.c
>
> I replaced
> #ifdef  CONFIG_UARTLITE
> by
> #ifdef CONFIG_SERIAL_UARTLITE

The petalinux BSP generator changed slightly a few months ago, in its
export of this CONFIG_UARTLITE / CONFIG_UART16550, so that u-boot (and
the linux system) could use either uartlite or uart16550 as the
console.

I think what you actually need to do is regenerate your Kconfig.auto
and auto-config.h, using the new BSP tools that would have been
installed when you pulled from the SVN tree.

I'm guessing maybe you used your old Kconfig.auto from an earlier release?

Michal did this change - @Michal  can you please confirm my suggestion
is correct?

> The hardware design is on a spartan3a starter kit. A CPU clock of 66.7 MHz
> is used (Design is based on the XPS base system builder).
> On the device I get the following output:
> # cat
> /proc/cpuinfo
> CPU-Family:
> MicroBlaze
> FPGA-Arch:
> spartan3a
> CPU-Ver:
> 7.10.d
> CPU-MHz:
> 100.00
> BogoMips:
> 49.66
> HW-Div:
> yes
> HW-Shift:
> yes
> Icache:
> 8kB
> Dcache:
> 8kB
> HW-Debug:       yes


Again, I suspect an inconsistency between the Kconfig.auto you are
building with the kernel, and the actual hardware.

This is easy to check/correct - in your HW project directory
(hardware/user-platforms/XXXXX) re-run

$ petalinux-prepare-hardware
$ make -f system.make libs
$ petalinux-copy-autoconfig

(assuming that your vendor/platform selection is already correct in
petalinux-dist tree)

Regards,

John
-- 
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/