On Jun 7, 1:45 am, Shant <shantchandra...@gmail.com> wrote:
> On Jun 5, 4:02 pm, John Williams <jwilli...@itee.uq.edu.au> wrote:
>
>
>
>
>
> > Hi Shant,
>
> > Shant wrote:
> > > My basic version of design has two interconnected microblaze, FSL has
> > > been used for interconnection.
> > > There is one application on each microblaze such that frist writes to
> > > second then the second microblaze sends some data back to the first
> > > one.
>
> > Sounds reasonable.
>
> > > My problem is that while performing Build all user application, it
> > > builds the application present in first microblaze but throws errror
> > > while building the application in second microblaze.
>
> > Details of the error message would be helpful!
>
> > John
>
> Hey John,
>
> Thanks for the reply...
>
> The problem has been figured out. It was because both the microblazes
> were using the same Uartlite for their printf function. After removing
> the printf from the second microblaze, the build process does not
> error out.
>
> Thanks again.
>
> Shant- Hide quoted text -
>
> - Show quoted text -

I had a similar problem using printf on MicroBlazes. I would
definitely just use the smaller xil_printf instead for MicroBlazes. It
also reduces the size of the program (stdio versus iostream)
significantly (since we're talking limited local BRAM), which can be
helpful. I also had issues where several MBs were sending data to
stdout at the same time, and it's pretty funny to see two messages
combined into one when they both use the same UART. Well, it's funny
now. It wasn't quite so funny at the time. :)

Just curious, but was the error concerning the "outbyte" function for
the 2nd processor?

If this is the case, I have found a work-around.  Just copy the /
libsrc directory from the first processor's directory to the 2nd
processors.  Everything should work out OK.

On Jun 5, 4:02 pm, John Williams <jwilli...@itee.uq.edu.au> wrote:
> Hi Shant,
>
> Shant wrote:
> > My basic version of design has two interconnected microblaze, FSL has
> > been used for interconnection.
> > There is one application on each microblaze such that frist writes to
> > second then the second microblaze sends some data back to the first
> > one.
>
> Sounds reasonable.
>
> > My problem is that while performing Build all user application, it
> > builds the application present in first microblaze but throws errror
> > while building the application in second microblaze.
>
> Details of the error message would be helpful!
>
> John

Hey John,

Thanks for the reply...

The problem has been figured out. It was because both the microblazes
were using the same Uartlite for their printf function. After removing
the printf from the second microblaze, the build process does not
error out.

Thanks again.

Shant

Hi Shant,

Shant wrote:

> My basic version of design has two interconnected microblaze, FSL has
> been used for interconnection.

> There is one application on each microblaze such that frist writes to
> second then the second microblaze sends some data back to the first
> one.

Sounds reasonable.

> My problem is that while performing Build all user application, it
> builds the application present in first microblaze but throws errror
> while building the application in second microblaze.

Details of the error message would be helpful!

John

Hi,

My basic version of design has two interconnected microblaze, FSL has
been used for interconnection.

There is one application on each microblaze such that frist writes to
second then the second microblaze sends some data back to the first
one.

My problem is that while performing Build all user application, it
builds the application present in first microblaze but throws errror
while building the application in second microblaze.

I am using EDK 9.1i, please throw some expert comments on this
problem.

Regards,
Shant Chandrakar