OpenCores
no use no use 1/1 no use no use
Difference between or32-uclibc-gcc and or32-uclinux-gcc
by Unknown on Apr 18, 2004
Not available!
Hi all, Just needed some clarifications regarding the difference between or32-uclibc-gcc and or32-uclinux-gcc Which one should I use when.. I wanted to compile to or1k but I don't want to use any OS ucLinux or RTEMS. Thanks! Learner __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash
Difference between or32-uclibc-gcc and or32-uclinux-gcc
by Unknown on Apr 19, 2004
Not available!
'or32-uclibc-gcc' is for building applications which will run on ucLinux. 'or32-uclinux-gcc' is for building ucLinux itself and the simulator. If you want to build vanilla targets with no OS dependencies I would recommend building the tools with the target as 'or32-elf'. The 'Build the OR1K tools' section in http://www.asisi.co.uk/or1kecos.html will tell you how to do it; alternatively follow the build rules defined for the or32-rtems target in http://www.opencores.org/projects.cgi/web/or1k/ats as I believe the or32-rtems target doesn't have OS library dependencies like the or32-linux target (please correct me if I'm wrong). Robert Cragie, Design Engineer _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655 _______________________________________________________________
-----Original Message----- From: openrisc-bounces@opencores.org [mailto:openrisc-bounces@opencores.org]On Behalf Of kernel_learner Sent: 18 April 2004 01:11 To: List about OpenRISC project Subject: [openrisc] Difference between or32-uclibc-gcc and or32-uclinux-gcc Hi all, Just needed some clarifications regarding the difference between or32-uclibc-gcc and or32-uclinux-gcc Which one should I use when.. I wanted to compile to or1k but I don't want to use any OS ucLinux or RTEMS. Thanks! Learner __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25" http://photos.yahoo.com/ph/print_splash _______________________________________________ http://www.opencores.org/mailman/listinfo/openrisc



Difference between or32-uclibc-gcc and or32-uclinux-gcc
by Unknown on May 6, 2004
Not available!
I noticed the ECOS link doesn't have any info about building the
simulator. Forgive my ignorance but will the or1ksim run binaries built
using the ECOS configured tools? Does the or1ksim simulator need to be
configured in any special way in order for this to work?

--Chris

Robert Cragie wrote:

'or32-uclibc-gcc' is for building applications which will run on ucLinux. 'or32-uclinux-gcc' is for building ucLinux itself and the simulator. If you want to build vanilla targets with no OS dependencies I would recommend building the tools with the target as 'or32-elf'. The 'Build the OR1K tools' section in http://www.asisi.co.uk/or1kecos.html will tell you how to do it; alternatively follow the build rules defined for the or32-rtems target in http://www.opencores.org/projects.cgi/web/or1k/ats as I believe the or32-rtems target doesn't have OS library dependencies like the or32-linux target (please correct me if I'm wrong). Robert Cragie, Design Engineer _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655 _______________________________________________________________
-----Original Message----- From: openrisc-bounces@opencores.org [mailto:openrisc-bounces@opencores.org]On Behalf Of kernel_learner Sent: 18 April 2004 01:11 To: List about OpenRISC project Subject: [openrisc] Difference between or32-uclibc-gcc and or32-uclinux-gcc Hi all, Just needed some clarifications regarding the difference between or32-uclibc-gcc and or32-uclinux-gcc Which one should I use when.. I wanted to compile to or1k but I don't want to use any OS ucLinux or RTEMS. Thanks! Learner __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25" http://photos.yahoo.com/ph/print_splash _______________________________________________ http://www.opencores.org/mailman/listinfo/openrisc
_______________________________________________ http://www.opencores.org/mailman/listinfo/openrisc



Difference between or32-uclibc-gcc and or32-uclinux-gcc
by Unknown on May 7, 2004
Not available!
* Chris J Hescott (hesc0002@umn.edu) wrote:
I noticed the ECOS link doesn't have any info about building the
simulator. Forgive my ignorance but will the or1ksim run binaries built
using the ECOS configured tools? Does the or1ksim simulator need to be
configured in any special way in order for this to work?


it will work without anything special.

regards,
p.

Difference between or32-uclibc-gcc and or32-uclinux-gcc
by Unknown on May 7, 2004
Not available!
No, perhaps I could have included that but I was building for a hardware target. You should be able to run eCos on the simulator, although I have not done it myself. I managed to help someone else in this area, so I have enclosed the details: Dear Robert Thanks a lot it works .. thanks very much BR Ken --- Robert Cragie rcc@jennic.com> wrote:
1) You

have not changed CYGPKG_HAL_STARTUP to RAM as
I suggested. You need to make sure you change this: [snip] # > # Startup type # Selects whether code initially runs from ROM or RAM. In the case of ROM startup, # it's possible for the code to be copied into RAM and executed there. # cdl_component CYG_HAL_STARTUP { # Flavor: data # No user value, uncomment the following line to provide one. # user_value ROM # value_source default # Default value: ROM # Legal values: "RAM" "ROM" [snip] to this: [snip] # > # Startup type # Selects whether code initially runs from ROM or RAM. In the case of ROM startup, # it's possible for the code to be copied into RAM and executed there. # cdl_component CYG_HAL_STARTUP { # Flavor: data user_value RAM # value_source default # Default value: ROM # Legal values: "RAM" "ROM" [snip] The rest in 'my.ecc' should be OK but you must rebuild your 'tree' from scratch, so delete your old tree and do 'ecosconfig --config=my.ecc tree' again. You may also need to make sure or1ksim is configured appropriately in the sim.cfg file - Marko mentioned something about the mc (presumably memory controller) being configured correctly. Something like this in sim.cfg might be OK, but don't forget I have *not* tried this: section memory pattern = 0x00 type = unknown /* Fastest */ nmemories = 1 device 0 name = "RAM" ce = 0 baseaddr = 0x00000000 size = 0x02000000 delayr = 2 delayw = 4 enddevice end 2) You do not use the simulator part of GDB at all. You run or1ksim first, then run GDB, then connect GDB to or1ksim using 'target jtag jtag://localhost:9999' as mentioned before. GDB then thinks it's talking to 'real' hardware via a JTAG connection.
Robert Cragie, Design Engineer Direct: +44 (0) 114 281 4512 _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655 Confidential _______________________________________________________________
-----Original Message----- From: openrisc-bounces@opencores.org [mailto:openrisc-bounces@opencores.org]On Behalf Of Chris J Hescott Sent: 06 May 2004 22:43 To: List about OpenRISC project Subject: Re: [openrisc] Difference between or32-uclibc-gcc and or32-uclinux-gcc I noticed the ECOS link doesn't have any info about building the simulator. Forgive my ignorance but will the or1ksim run binaries built using the ECOS configured tools? Does the or1ksim simulator need to be configured in any special way in order for this to work? --Chris Robert Cragie wrote:
>'or32-uclibc-gcc' is for building applications which will run on ucLinux.
>'or32-uclinux-gcc' is for building ucLinux itself and the simulator.
>
>If you want to build vanilla targets with no OS dependencies I would
>recommend building the tools with the target as 'or32-elf'. The

'Build the
>OR1K tools' section in http://www.asisi.co.uk/or1kecos.html will tell you >how to do it; alternatively follow the build rules defined for the >or32-rtems target in
http://www.opencores.org/projects.cgi/web/or1k/ats as I
>believe the or32-rtems target doesn't have OS library

dependencies like the
>or32-linux target (please correct me if I'm wrong). > >Robert Cragie, Design Engineer >_______________________________________________________________ >Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK >http://www.jennic.com Tel: +44 (0) 114 281 2655 >_______________________________________________________________ > > >
>-----Original Message----- >From: openrisc-bounces@opencores.org >[mailto:openrisc-bounces@opencores.org]On Behalf Of kernel_learner >Sent: 18 April 2004 01:11 >To: List about OpenRISC project >Subject: [openrisc] Difference between or32-uclibc-gcc and >or32-uclinux-gcc > > >Hi all, > > Just needed some clarifications regarding the >difference between or32-uclibc-gcc and >or32-uclinux-gcc >Which one should I use when.. > >I wanted to compile to or1k but I don't want to use >any OS ucLinux or RTEMS. > >Thanks! >Learner > > > > > > > >__________________________________ >Do you Yahoo!? >Yahoo! Photos: High-quality 4x6 digital prints for 25" >http://photos.yahoo.com/ph/print_splash >_______________________________________________ >http://www.opencores.org/mailman/listinfo/openrisc > > >
> >_______________________________________________ >http://www.opencores.org/mailman/listinfo/openrisc > >
_______________________________________________ http://www.opencores.org/mailman/listinfo/openrisc



no use no use 1/1 no use no use
© copyright 1999-2025 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.