Re: [rtl] Jumptec
I've been using it on one... seems to work fine, but if you've got one with the BIOS-compatible flash disk, that won't work. The newer ones are IDE-compatible, methinks. -Cory On Fri, 25 Aug 2000, Andreas Oeder wrote: > Hi everybody, > > > Does anyone know if RTLinux runs on Jumptec MOPSlcd4 or MOPSlcd6 Boards > ? > > Thank you very much. > > Andy -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] IDE flash disk boot problems
I'd just like to say that I have resolved the conflict. Although
everything appeared to be in order (devices made, kernel has support for
everything, root= and initrd= in the right place, etc), it seems that it had
something to do with the libraries that init wanted. I did an ldd on init and
put the libraries it wanted into /lib on the initrd, but it never did work. I
ended up using a color.gz rootdisk from the slackware distro and modifying
that. (good ol' slackware... :)
Thanks for the suggestions
-Cory
On Fri, 4 Aug 2000, Jacob Chen wrote:
> Hi,
>
> > Warning: unable to open an initial console.
> > Kernel panic: No init found. Try passing init= option to kernel
> >
>
> Try make the /dev/console a softlink to /dev/ttyS0 (or one of the ttyx) to
> get rid of this warning.
>
> Jacob
> - Original Message -
> From: "wolfgang guldner" <[EMAIL PROTECTED]>
> To: "Cory Papenfuss" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 02, 2000 1:11 AM
> Subject: Re: [rtl] IDE flash disk boot problems
>
>
> Hello,
>
> I´m using the same sort of ide-compatible flash disk´s this more than a half
> year,
>
> and there is always this message. But everything works fine. So I think
> there is
> no worry
> about this.
>
> Regard Wolfgang
>
> Cory Papenfuss wrote:
>
> > Hello all... I've got a PC104 with 16MB chipdisk ide-compatible
> flash
> > disk that I'm trying to make boot. The original plan was to hold
> compressed
> > ramdisk on the flash, and run the rt system and module with ramdisk as the
> > rootfs. The rest of the flash would be for logging data alone. The
> problem is
> > that I'm not sure just how "compatible" this IDE drive is. As I'm trying
> these
> > different boot schemes (currently kernel and minimal rootfs directly on
> > /dev/hda1 flash disk), the kernel loads, but then spits out:
> >
> > hda: hda1
> > hdb: hdb1 hdb2 (the development HD with full linux install)
> > hda: hda1
> > hda: drive_ccmd: status=0x51 { DriveReady SeekComplete Error }
> > hda: drive_cmd: error=0x04 { DriveStatusError }
> > hda: hda1
> > VFS: Mounted root (ext2 filesystem) readonly
> > Freeing unused kernel memory: 28k freed
> > Warning: unable to open an initial console.
> > Kernel panic: No init found. Try passing init= option to kernel
> >
> > ... but /dev/tty0-8 and /sbin/init are in place on this filesystem as they
> are
> > supposed to. Any ideas on if these funky seek errors are to blame? I've
> > already tried the "hda=slow' kernel option at bootup, but same thing.
> >
> > Thanks in advance,
> > -Cory
> >
> > -- [rtl] ---
> > To unsubscribe:
> > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> > echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
> > ---
> > For more information on Real-Time Linux see:
> > http://www.rtlinux.org/rtlinux/
>
> --
>
> _
>
> BFAD GmbH & Co. KG
>
> Wolfgang Guldner
> Kornblumenweg 36
> D-78247 Hilzingen
>
> Tel.07731-9057-73
> Fax 07731-9057-66
> E-Mail: [EMAIL PROTECTED]
> Homepage: www.bfad.de
>
>
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
>
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
[rtl] IDE flash disk boot problems
Hello all... I've got a PC104 with 16MB chipdisk ide-compatible flash
disk that I'm trying to make boot. The original plan was to hold compressed
ramdisk on the flash, and run the rt system and module with ramdisk as the
rootfs. The rest of the flash would be for logging data alone. The problem is
that I'm not sure just how "compatible" this IDE drive is. As I'm trying these
different boot schemes (currently kernel and minimal rootfs directly on
/dev/hda1 flash disk), the kernel loads, but then spits out:
hda: hda1
hdb: hdb1 hdb2 (the development HD with full linux install)
hda: hda1
hda: drive_ccmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: hda1
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 28k freed
Warning: unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel
... but /dev/tty0-8 and /sbin/init are in place on this filesystem as they are
supposed to. Any ideas on if these funky seek errors are to blame? I've
already tried the "hda=slow' kernel option at bootup, but same thing.
Thanks in advance,
-Cory
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
[rtl] BIOS-flash disk access?
Hello all... I'm using a PC/104 586 machine from Jumptec, and it has a 1.6 MB flash disk that I'd like to be able to dump a few bytes to in rt-space (for saving NV parameters). Unfortunately, I think the only access to it is through BIOS calls, since it's not IDE compatible. Any ideas on how or if this can be done? Thanks, -Cory Papenfuss -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] hrtime_t -> int
I've (sorta) figured it out. The int must first be cast as a long long
or the multiplication will overflow, but when I tried putting a division in a
rt-space function to return miliseconds since boot, I get
./init.o: unresolved symbol __divdi3
when I try to load up my init.o module. Is the access of the longlong division
forbidden within rt-space?
BTW, getlrtime that produced that error is little more than
unsigned long int getlrtime(void){
return((unsigned long)((long long)gethrtime() / 100LL)
}
-Cory
On Mon, 26 Jun 2000, Michael Barabanov wrote:
> Cory Papenfuss ([EMAIL PROTECTED]) wrote:
> > Hey all... I've got something that's been bugging me for awhile on this
> > project. I really only need millisecond resolution (since I'm logging data to
> > disk), but the hrtime_t doesn't like to be divided by 1000 (NS_PER_MS), as
> > it's a funky type. Any way I can get around that and get a millisecond
> > timestamp?
>
> What do you mean it doesn't like to be divided? hrtime_t is just
> an alias for long long.
>
> > On a related note, I've got a user-space app that can send new
> > pthread_make_period_np periods (again in [ms]). Problem is that if I try to
> > send a time greater than 2147 ms, the machine craps out. I suspect it's a
> > rollover on my
> >
> > looptime = * 100;
> > pthread_make_periodic_np(thread[0], genesis+OFFSET, looptime);
> >
> >
> > What's a good way to do arithmetic on these hrtime_t creatures?
>
> looptime = * (long long) 100;
>
> Michael.
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
[rtl] hrtime_t -> int
Hey all... I've got something that's been bugging me for awhile on this project. I really only need millisecond resolution (since I'm logging data to disk), but the hrtime_t doesn't like to be divided by 1000 (NS_PER_MS), as it's a funky type. Any way I can get around that and get a millisecond timestamp? On a related note, I've got a user-space app that can send new pthread_make_period_np periods (again in [ms]). Problem is that if I try to send a time greater than 2147 ms, the machine craps out. I suspect it's a rollover on my looptime = * 100; pthread_make_periodic_np(thread[0], genesis+OFFSET, looptime); What's a good way to do arithmetic on these hrtime_t creatures? -Cory -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: [rtl] fpu exception 7 ??
I had the same problem when I tried to initialize a thread with pthread_setfp_np() in the init_module() portion of module. As near as I could tell, once I pthread_create()'d the module, even though the very next line was to enable fp, the thread had tried executing fp code before it was enabled to do so. I inserted a pthread_suspend_np() in the thread and then a pthread_wakeup_np() in the init and it seemed to work around it. BTW, is this a silly thing to do? What's the correct order to create threads and set their parameters if not? cheers, -Cory On Tue, 20 Jun 2000, Paul Jacyk wrote: > Hello, > > I just got the new RTLinux 3.0-pre6. So far it works well. More of my > program actually runs now than in RTLinux 2.3 (still not all the way) > I'm running all of this on an AMD K6 machine that according to > /proc/cpuinfo has a floating point unit. > > A message appeared "rtl_debug exception 7" when I inserted my module. > I'm not sure why this would happen. Isn't floating point supported in > RTLinux on a K6 ? I compiled the kernel with the "K6/II/III" processor > option for CONFIG_M386 and all other options set to "no" in the > processor type and features config. Are the exceptions different on a K6 > than on a intel chip ? > > As far as I can tell I'm calling pthread_setfp_np in the correct place. > If I am not calling in properly what error message will show up ? > > >From a table of interrupt assignments in the Intel 386, 486 SX/DX > processors, and the Pentium processor. > > 7Device not available > Exception 7 is used to signal that a floating point processor is > not present in the SX model. Exception 7 is used for programs > and OSs that have floating point emulation. In addition, the DX > chips can be set to trap floating point instructions by setting > bit 2 of CR0. > > Thanks, > > Paul > > > > > -- [rtl] --- > To unsubscribe: > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > echo "unsubscribe rtl " | mail [EMAIL PROTECTED] > --- > For more information on Real-Time Linux see: > http://www.rtlinux.org/rtlinux/ > -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
[rtl] Data Acq. I/O Problems
Hello all... I've been working for a few days (weeks?) with rtlinux
trying talk with a data acquisistion board for rt-control. I've found the
debugger code, but I'm unable to figure out what the problem is. I've got a
simple single thread for scanning the A/D channels, with a
while(1){
pthread_wait_np();
}
main loop. The thread is initialized with
int init_module (void) {
struct sched_param p;
hrtime_t now = gethrtime();
pthread_create (&thread[0], NULL, scan_ad_channels, (void *) 1);
pthread_make_periodic_np (thread[0], now + 1, 10);
pthread_setfp_np (thread[0], 1);
p . sched_priority = 1;
pthread_setschedparam (thread[0], SCHED_FIFO, &p);
return 0;
}
The main problem I get are "exception 14 in init..." and gdb inidicates a fault
at the cleanup_module(), even before it's supposed to execute. Am I stomping
on memory somewhere? Can I find a listing of which exceptions are what
somewhere?
Thanks for any help
-Cory
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl " | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
