Re: XIP / PIC

Hi Vincent,

Carr, Vincent wrote:

>>Steve Sanders wrote:
>>I've never heard of running the kernel directly from flash.  But that
> 
> doesn't mean it can't be done.  You'd certainly have to > copy some
> sections to SRAM _before_ starting the OS so that the kernel can update
> variables...
> 
> Reading more about executing the kernel directly from FLASH I've seen
> that this can be done if the kernel is built for XIP (eXecute In Place).
> Some documentation say that the Kernel is always XIP.  Is that true?

> For applications to run directly from flash however the compiler must be
> capable of generating Position Independent Code(PIC) and capable fo
> generating the PIC form of flat executable.
> 
> Does the current version of mb-gcc support PIC?

You don't need PIC to run the kernel in place from flash - the basic 
build infrastructure is already in place.  As Steve said, you'll need to 
relocate the data segments into RAM of some sort.

Create appropriate platform subdir arch/microblaze/platform/xxxxx (see 
the doco in linux-2.4.x/Documentation/microblaze)

Edit arch/microblaze/Boards.make, create a new section for your 
platform, and adding the line MODEL=flash inside the if/endif pair. 

Re: help with build of uCLinux for Xilinx XUP board, with EDK 7.1.1

Hi Kris,

Kris Heyrman wrote:

> 
> 3. Now my build is almost done, but it stops at:
>     mb-flthdr -z /home/krish/edk/xup-uclinux/uclinux-src/uClinux-dist
>       /romfs/bin/*
>     Cannot read header of /home/krish/edk/xup-uclinux/uclinux-src/
>       uClinux-dist/romfs/bin/[
>     zflat /home/krish/edk/xup-uclinux/uclinux-src/uClinux-dist/romfs/bin
>       agetty --> /home/krish/edk/xup-uclinux/uclinux-src/uClinux-dist/
>       romfs/bin/agetty
>      can't run cmd gzip -9 -f >> /tmp/flatF92eni
>     Which gives me a sinking feeling.

It's a build issue with the version of mb-flthdr that was bundled with 
EDK7.1  Grab a copy of the mb-flthdr that comes with the toolchain that 
is distributed on the website.

I'm still seeing issues with building under gcc-3.4, even once you get a 
clean compile.  I haven't had any time recently to look at it, so will 
be very interested to hear of your progress.

Cheers,

John

CFI Flash on 8bit bus?

Hi everyone,

I have been struggling with flash for the last few days, and I'm at my wit's
end.

I have configured mtd to use Intel flash and to use 8bit bus width.

During boot I get the following message:

[snip]
physmap flash device: 1000000 at 24000000
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x20000,blocks=128
Using buffer write method
physmap: no partition info available, registering whole flash at once [snip]

That tells me that it did detect the chip, as its block size is
0x20000(128KB) and it has 128 blocks for a total of 16MB.

But when I try and format(or dd) it I get the following:

[snip]
# ftl_format /dev/mtd0
Partition size = 16 mb, erase unit size = 128 kb, 1 transfer units Reserved
5%, formatted size = 15631872 bytes Erasing all blocks...
Chip reports improper command sequence: status 0x7000000000

block erase failed: Input/output error
format failed.
[snip]

Fwd: UCLINUX Support for Linux Test Project

Hi folks,

Just forwarding an announcement from uClinux-dev, in turn forwarded from 
the Linux Test Project mailing list.  Patches to support the BlackFin 
uClinux port have been contributed to the LTP.

If anyone has a chance to look into this for MicroBlaze, please let us know.

Cheers,

John

From: Robin Getz <rgetz@...>
Subject: [uClinux-dev] FWD: [LTP] [PATCH 0/16] UCLINUX Support for Linux Test Project
Date: 2005-07-03 01:39:22 GMT

Just thought people here might be interested:

On Wednesday (Wed 6/29/2005 3:55 PM) Paul J.Y. Lahaie wrote to the Linux 
Test Project mailing list:

>Following are a set of patches to the Linux Test Project that implement 
>support for UCLINUX targets.
>

Re: Fwd: UCLINUX Support for Linux Test Project

Hi John,

As I commented you several weeks ago, I'm interested in strong tests for 
Microblaze so I catch the challenge.

I will inform the list about my advances.

On Monday 04 July 2005 02:02, John Williams wrote:
> Hi folks,
>
> Just forwarding an announcement from uClinux-dev, in turn forwarded from
> the Linux Test Project mailing list.  Patches to support the BlackFin
> uClinux port have been contributed to the LTP.
>
> If anyone has a chance to look into this for MicroBlaze, please let us
> know.
>
> Cheers,
>
> John

--

-- 
Alejandro Lucero
OS3, OS Serveis i Solucions
www.os3sl.com
Ingeniería Informática
+34 665687168
Av.Benjamin Franklin
CEEI. Parque Tecnológico de Paterna
Valencia(Spain)

Microblaze ucLinux and C++ applications with the STL

I am having no luck getting any C++ applications to compile with an in-tree compile with microblaze
uclinux.  I have made a variety of attempts

a) There is a C++ Test Program that comes with the uclinux tree.  Enabling that in the build config also
enables STLport, and that fails during compilation

b) I have tried a simple hello world with the STL, and since STLport didn't compile I tried using the headers
in microblaze-elf-tools, but when using those it fails with a 
message about a missing file called ?_G_config.hpp? (name is not exact, I can retrieve the exact name if it
would help, I have been hacking away at this for a while)

Has anyone got a simple C++ application that uses the STL to compile with microblaze uclinux? 

If not, is there some reason for this?  Such that the C++ STL is known to not work with uClinux?

Btw, a C++ application without the STL compiles fine.

Thanks, Joshua Moore-Oliva

Re: GDB debugging with threads

Hi John,

    I am getting the same errors that Sowmya was getting. I have not
applied any patch or have not worked on your instructions. May be, I
am having the dist where your instructions have already been applied.
Will you please tell me how to fix these compilation problems and get
the gdb server working. Is there any other way to debug user programs?
I am using spartan -3 1500 Nu horizon's evaluation board.

Please help me.

Regards

Anand Shivhare
Reliance Infocomm
ITIC Gurgaon.
Ph : 09350245275

On 6/14/05, John Williams <jwilliams@...> wrote:
> Hi Sowmya,
> 
> Sorry for the delayed reply, things have been very busy at this end.
> Please see my comments below.
> 
> Jadda, Sowmya (GE Infrastructure Security) wrote:
> 
> > I tried the instructions which you sent me in your previous mail. I got a couple of compile errors during
the build process.
> >
> > In utils.c file in user/gdbserver, in the function "perror_with_name", sys_nerr and sys_errlist are

Re: kernel compilation error: 'vmlist_lock undeclared'

Hi David,

   I have got a spartan-3 1500 board from nu-horizon, (sent by you)
and currently working with uClinux. I am having problem with
compilation of gdbserver. I want to use it for debug my own user
application. please help me.
   Is there any other way to debug user application?

Please help me.

Anand Shivhare
Reliance Infocomm
ITIC Gurgaon
India

On 5/27/05, David Banas <dbanas@...> wrote:
> Thanks, John!
> 
> As part of preparing an "official" release for submission to your Web site,
> I've attempted to chose the appropriate tag for users to specify when
> checking out both kernel and dist. sources from the archive, the intent
> being to know for certain that the patches I supply as part of that release
> will apply cleanly to the particular version of the source that I recommend
> and that the resultant code will compile.
> 
> I settled on "uClinux-2_4_29-uc0" for the kernel source, only because the
> date associated with the more recent tag,
> "before-snapgear-code-sync-20050504", (May 4, 2005) appeared to be
> coincident with some complaints regarding recently introduced kernel
> instabilities, which I thought I recalled coming through the list.

RE: XIP / PIC

John,

Thanks for the pointers.

> John Willams wrote:
> Create appropriate platform subdir arch/microblaze/platform/xxxxx (see
the doco in linux-2.4.x/Documentation/microblaze)

I've worked through the steps for adding a new platform
(AddingPlatforms.txt) but it the auto-config mechanism doesn't appear to
be working.

When I compile using 'make all' I see the following when time.c is being
compiled.

	In file included from time.c:26:
	uClinux-2.4.x/include/asm/microblaze_timer.h:17: #error CPU
Clock frequerncy not defined!
	uClinux-2.4.x/include/asm/microblaze_timer.h:25: #error No timer
peripheral specified
	make[2]: *** [time.o] Error 1
	make[2]: Leaving directory
`uClinux-2.4.x/arch/microblaze/kernel'
	make[1]: *** [_dir_arch/microblaze/kernel] Error 2
	make[1]: Leaving directory `uClinux-2.4.x'
	make: *** [linux] Error 1

This is the offending excerpt from microblaze_timer.h
	
	/* Hack to optionally use Xilinx autoconfig if available */

RE: kernel compilation error: 'vmlist_lock undeclared'

Hi Anand,

2 Things:

1) A general question to you and the group,
	What happens if you try and remotely debug a user-space application
the way you debug the booting kernel? (That is, using the gdb-server built
into XMD, as opposed to one running on the target.)

2) As you can see from John's reply, below, as well as the many messages on
this topic, which have come through the list in the recent months, this is
not a quickly solved problem. Regrettably, I'm unable to provide any sort of
"quick fix" for this one.

Regards,

David Banas
Field Applications Engineer
Nu Horizons Electronics Corp.
2070 Ringwood Avenue
San Jose, CA 95131
(408)434-0800 - office
(415)846-5837 - cell
http://www.nuhorizons.com
> -----Original Message-----
> From: owner-microblaze-uclinux@... [mailto:owner-microblaze-
> uclinux@...] On Behalf Of Anand Shivhare
> Sent: Tuesday, July 05, 2005 7:23 AM
> To: microblaze-uclinux@...
> Subject: Re: [microblaze-uclinux] kernel compilation error: 'vmlist_lock