Elan-104NC - supported?

Is the Elan-104 NC supported under Neutrino?

We bought the development kits with QNX 4 last year and would like to
upgrade to Neutrino.

When I boot with the QNX boot floppy (made from the CD) I get

Stack at CPU fault:
[ hex dump]

Unsupported Interrupt 06
[hex dump]

Am I just not understanding how to install it? (These boards have a hard
drive, floppy drive, and CD ROM attached so I though I could just install
them like a normal PC.)

Thanks!

Dana

Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Dana Echtner <dana@ece.concordia.ca> wrote:

Is the Elan-104 NC supported under Neutrino?

We bought the development kits with QNX 4 last year and would like to
upgrade to Neutrino.

When I boot with the QNX boot floppy (made from the CD) I get

Stack at CPU fault:
[ hex dump]

Unsupported Interrupt 06
[hex dump]

Am I just not understanding how to install it? (These boards have a hard
drive, floppy drive, and CD ROM attached so I though I could just install
them like a normal PC.)

Thanks!

Dana

Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Can the Elan 104 board boot from a CD-ROM? If so, try installing it
that way.


Dave Green (dgreen@qnx.com)

Custom Engineering Services
QNX Software Systems Ltd.
http://www.qnx.com

Dave Green wrote:


Is the Elan-104 NC supported under Neutrino?

Can the Elan 104 board boot from a CD-ROM? If so, try installing it
that way.

No, there is no such option in the BIOS.

Any other ideas?

D. (man, my ass is grass here) :wink:


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hi Dana,

I have an Elan 104 board here, I am going to see if it is possible to
boot from a drive with the RTP already installed.

I will keep you posted.

E.


Dana Echtner <dana@ece.concordia.ca> wrote:

Dave Green wrote:



Is the Elan-104 NC supported under Neutrino?

Can the Elan 104 board boot from a CD-ROM? If so, try installing it
that way.

No, there is no such option in the BIOS.

Any other ideas?

D. (man, my ass is grass here) > :wink:


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hardware Support Account wrote:

I have an Elan 104 board here, I am going to see if it is possible to
boot from a drive with the RTP already installed.

I will keep you posted.

Thanks!!!


I’m also making progress here - we contacted Arcom and they’re
sending us a floppy with an alternate boot image.

They’re also shipping a version of Neutrino that can just be flashed in.

I’ll also let you know how I’m doing.

Thanks so much! (I’m feeling much better already, this morning I
figured it was the pretty much the end of the world but I think it’s ok
now.) :slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hi Dana,

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

I will see if I can narrow down what util is causing this and then
perhaps we can come up with a fix.

E.


Dana Echtner <dana@ece.concordia.ca> wrote:

Hardware Support Account wrote:

I have an Elan 104 board here, I am going to see if it is possible to
boot from a drive with the RTP already installed.

I will keep you posted.

Thanks!!!



I’m also making progress here - we contacted Arcom and they’re
sending us a floppy with an alternate boot image.

They’re also shipping a version of Neutrino that can just be flashed in.

I’ll also let you know how I’m doing.

Thanks so much! (I’m feeling much better already, this morning I
figured it was the pretty much the end of the world but I think it’s ok
now.) > :slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hardware Support Account wrote:


I will see if I can narrow down what util is causing this and then
perhaps we can come up with a fix.

Great, thanks!

I’m still waiting for Arcom’s “fix” to arrive in my inbox. I’ll let you
know if it works!

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

How about a QNX 6 boot/install disk image with the non-PCI diskboot and
the aha2 driver on it? Many older laptops don’t have PCI, and the
Adaptec SCSI controllers covered by aha2 are quite common in PC Cards,
port replicators and docking stations, usually without their own BIOS
since the main intention is for use with CD-ROM, Zip and other
removables. You would have many many laptop users jumping for joy if
such a disk image was made available to download. :slight_smile:

Hardware Support Account wrote:

Hi Dana,

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

I will see if I can narrow down what util is causing this and then
perhaps we can come up with a fix.

E.

Dana Echtner <> dana@ece.concordia.ca> > wrote:
Hardware Support Account wrote:

I have an Elan 104 board here, I am going to see if it is possible to
boot from a drive with the RTP already installed.

I will keep you posted.

Thanks!!!

I’m also making progress here - we contacted Arcom and they’re
sending us a floppy with an alternate boot image.

They’re also shipping a version of Neutrino that can just be flashed in.

I’ll also let you know how I’m doing.

Thanks so much! (I’m feeling much better already, this morning I
figured it was the pretty much the end of the world but I think it’s ok
now.) > :slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hardware Support Account wrote:


I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

An interesting data point.

I was able to install with no problem on an older verson of the Elan 104.
I’m not sure how it’s different from the new, I’ll find out. (The only
visible difference I found is that the older board doesn’t have ethernet
on-board, it has to have a card for that.)

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hardware Support Account wrote:

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

Arcom came through and gave us a Neutrino image that works. I don’t know
what they did though. :slight_smile: (But it did involve a bios upgrade)

So that problem being solved, it’s time to tackle all the others. :slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

We provided an alternative method to access the flash using qnet between the
board and a hard drive. The BIOS upgrade is basically our same BIOS with the
ipl extension…

We are still having trouble booting a hard drive, though I can’t seem to
figure out what the trouble is. It occurs even with working, custom boot
images ( with and w/o seedres and pci-bios) that load just the necessities
to boot a hard drive as root. So, if anyone has an idea please continue to
make suggestions.

Thanks,

Hardware Support Account wrote:

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

Arcom came through and gave us a Neutrino image that works. I
don’t know
what they did though. > :slight_smile: > (But it did involve a bios upgrade)

So that problem being solved, it’s time to tackle all the others.
:slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Hi Wendy,

We tried to flash 3 Elan-104NC with a new boot image,
but it ‘jams’ at 73%, the main problem is that now
we have 3 board flashed that are not working at all… =(

Is there a way to recover or to fix that problem gracefully !?

At least, come back to the original flash ?

Any help would be very appreciated,

Sincerly yours,
Fred.


We provided an alternative method to access the flash using qnet between
the
board and a hard drive. The BIOS upgrade is basically our same BIOS with
the
ipl extension…

We are still having trouble booting a hard drive, though I can’t seem to
figure out what the trouble is. It occurs even with working, custom boot
images ( with and w/o seedres and pci-bios) that load just the necessities
to boot a hard drive as root. So, if anyone has an idea please continue to
make suggestions.

Thanks,

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

Arcom came through and gave us a Neutrino image that works. I
don’t know
what they did though. > :slight_smile: > (But it did involve a bios upgrade)

So that problem being solved, it’s time to tackle all the others.
:slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

I’ve discussed this with Dana via email. If you can’t reload with RTP, one
way to restore the flash and eliminate any hardware problems is to use the
FlashFX utilities for QNX or DOS and reformat the flash. When she tried
this, she said it formatted fine. Take care that the total image you create
isn’t too large to fit onto the flash (ie. boot image < 512K, total image <
8M).

  • Wendy

“Fred” <fprog@nowhere.users.sourceforge.net> wrote in message
news:96uio4$5f4$1@inn.qnx.com

Hi Wendy,

We tried to flash 3 Elan-104NC with a new boot image,
but it ‘jams’ at 73%, the main problem is that now
we have 3 board flashed that are not working at all… =(

Is there a way to recover or to fix that problem gracefully !?

At least, come back to the original flash ?

Any help would be very appreciated,

Sincerly yours,
Fred.


We provided an alternative method to access the flash using qnet between
the
board and a hard drive. The BIOS upgrade is basically our same BIOS with
the
ipl extension…

We are still having trouble booting a hard drive, though I can’t seem to
figure out what the trouble is. It occurs even with working, custom boot
images ( with and w/o seedres and pci-bios) that load just the
necessities
to boot a hard drive as root. So, if anyone has an idea please continue
to
make suggestions.

Thanks,

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

Arcom came through and gave us a Neutrino image that works. I
don’t know
what they did though. > :slight_smile: > (But it did involve a bios upgrade)

So that problem being solved, it’s time to tackle all the
others.
:slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal,
Canada

rw-rw-rw-: The file protection of the beast

\

wendy wrote in message <96uogj$8dn$1@inn.qnx.com>…

I’ve discussed this with Dana via email. If you can’t reload with RTP, one
way to restore the flash and eliminate any hardware problems is to use the
FlashFX utilities for QNX or DOS and reformat the flash. When she tried
this, she said it formatted fine. Take care that the total image you create
isn’t too large to fit onto the flash (ie. boot image < 512K, total image
8M).

  • Wendy

Weird, anyway, she’s gone for a week,
but at the last news I got from her,
she had 3 Elan-104NC non-working.

I will talk about that with the other sysadmins here,

Thanks!

Fred.

We tried to flash 3 Elan-104NC with a new boot image,
but it ‘jams’ at 73%, the main problem is that now
we have 3 board flashed that are not working at all… =(

Is there a way to recover or to fix that problem gracefully !?

At least, come back to the original flash ?

Any help would be very appreciated,

Sincerly yours,
Fred.


We provided an alternative method to access the flash using qnet between
the
board and a hard drive. The BIOS upgrade is basically our same BIOS with
the
ipl extension…

We are still having trouble booting a hard drive, though I can’t seem to
figure out what the trouble is. It occurs even with working, custom boot
images ( with and w/o seedres and pci-bios) that load just the
necessities
to boot a hard drive as root. So, if anyone has an idea please continue
to
make suggestions.

Thanks,

I used a new version of diskboot that doesn’t need the pci bios, it
went ok to a point then I also got the core dump from the processor.

Arcom came through and gave us a Neutrino image that works. I
don’t know
what they did though. > :slight_smile: > (But it did involve a bios upgrade)

So that problem being solved, it’s time to tackle all the
others.
:slight_smile:

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal,
Canada

rw-rw-rw-: The file protection of the beast



\

wendy wrote:

I’ve discussed this with Dana via email. If you can’t reload with RTP, one
way to restore the flash and eliminate any hardware problems is to use the
FlashFX utilities for QNX or DOS and reformat the flash. When she tried
this, she said it formatted fine. Take care that the total image you
create isn’t too large to fit onto the flash (ie. boot image < 512K, total
image < 8M).

Well, it sort of worked.

Under DOS it formats fine, looks file, works fine, but as soon as I boot
into QNX and use flashctl over qnet to erase the flash I get the “erase
protect error” again. I’ve tried

FXFMT 80 /p64k

and

FXRECLM and both worked fine, but it doesn’t fix my problem.
(the problem being that doing an erase with flashctl fails with “erase
protect error” and a cp of an image freezes at 70-some percent. (I assume
at the same place as the erase protect error))

I’m still futzing with it but not really getting anywhere.

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

Dana Echtner <dana@ece.concordia.ca> wrote:

wendy wrote:

I’ve discussed this with Dana via email. If you can’t reload with RTP, one
way to restore the flash and eliminate any hardware problems is to use the
FlashFX utilities for QNX or DOS and reformat the flash. When she tried
this, she said it formatted fine. Take care that the total image you
create isn’t too large to fit onto the flash (ie. boot image < 512K, total
image < 8M).

Well, it sort of worked.

Under DOS it formats fine, looks file, works fine, but as soon as I boot
into QNX and use flashctl over qnet to erase the flash I get the “erase
protect error” again. I’ve tried

FXFMT 80 /p64k

and

FXRECLM and both worked fine, but it doesn’t fix my problem.
(the problem being that doing an erase with flashctl fails with “erase
protect error” and a cp of an image freezes at 70-some percent. (I assume
at the same place as the erase protect error))

I’m still futzing with it but not really getting anywhere.

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca > / ECE, Concordia University, Montreal, Canada

What type of flash is on the Elan 104 board? If it’s Intel, I’ve seen other
situations where Intel flash somehow gets certain sectors locked, such that
they can’t be erased.

If it’s Intel, the following program will unlock the flash. It assumes
a single 16 bit, 8MB flash part, mapped to address 0xff000000.
You’ll need to change your defines accordingly.

Also, if your flash is interleaved, or a different bus width, you’ll need to
change the pointer size, etc.


#include <stdlib.h>
#include <stdio.h>
#include <sys/neutrino.h>
#include <sys/mman.h>
#include <errno.h>
#include <fcntl.h>
#include <unistd.h>
#include <x86/inout.h>

#define REGION1 0xff000000
#define FLASHSIZE 0x800000

// function prototypes

void* Map_Physical(unsigned long, unsigned long);
void unlock_flash(void*);

int main(void)
{
void *addr;

ThreadCtl(_NTO_TCTL_IO, 0);
addr=Map_Physical(REGION1,FLASHSIZE);
unlock_flash(addr);

return(0);
}

void* Map_Physical(unsigned long region, unsigned long size)
{
int fd;
char *addr;

// Open physical memory
fd = shm_open(“Physical”, O_RDWR | O_CREAT, 0777);
if (fd == -1)
{
fprintf(stderr, “Open failed:%s\n”, strerror(errno));
exit(1);
}

// Map specified region

addr = mmap_device_memory(0, (size_t)size, PROT_READ | PROT_WRITE | PROT_NOCACHE,
MAP_SHARED, region);

if (addr == (void *) -1)
{
fprintf(stderr, “mmap failed : %s\n”,strerror(errno));
exit(1);
}
return(addr);
}


void unlock_flash(void *addr)
{
unsigned short *s = (unsigned short *)addr;

s[0] = 0x0060; // send unlock_device command to flash
s[0] = 0x00d0;
}


Dave Green (dgreen@qnx.com)

QNX Software Systems Ltd.
http://www.qnx.com

Dave Green wrote:


What type of flash is on the Elan 104 board? If it’s Intel, I’ve seen
other situations where Intel flash somehow gets certain sectors locked,
such that they can’t be erased.

Oooh, that sounds like exactly my problem… (Yes, it is Intel flash)
(as far as I know) :slight_smile:

If it’s Intel, the following program will unlock the flash. It assumes
a single 16 bit, 8MB flash part, mapped to address 0xff000000.
You’ll need to change your defines accordingly.

Also, if your flash is interleaved, or a different bus width, you’ll need
to change the pointer size, etc.

Um, I don’t know. Wendy, can you help? How can I map the flash to
somwhere aftter I boot with your qnet boot disk? Any mods that this little
program needs?

Dave: Thanks!!! If this works you’ll have saved a lot of people a
lot of hassle. :slight_smile:

Dana

Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

Dana Echtner <dana@ece.concordia.ca> wrote:

Dave Green wrote:



What type of flash is on the Elan 104 board? If it’s Intel, I’ve seen
other situations where Intel flash somehow gets certain sectors locked,
such that they can’t be erased.

Oooh, that sounds like exactly my problem… (Yes, it is Intel flash)
(as far as I know) > :slight_smile:

If it’s Intel, the following program will unlock the flash. It assumes
a single 16 bit, 8MB flash part, mapped to address 0xff000000.
You’ll need to change your defines accordingly.

Also, if your flash is interleaved, or a different bus width, you’ll need
to change the pointer size, etc.

Um, I don’t know. Wendy, can you help? How can I map the flash to
somwhere aftter I boot with your qnet boot disk? Any mods that this little
program needs?

Dave: Thanks!!! If this works you’ll have saved a lot of people a
lot of hassle. > :slight_smile:

No problem. :slight_smile: If you’re using flashctl, then you’re likely using a devf-*
driver for the flash, and the flash is already mapped somewhere. It’s just
a matter of finding out where. If it’s the devf-arcom driver that I think
it is, then it’s a single, 8M flash, 16 bits wide, mapped at 0x2000000. If
so, you can just change the 0xff000000 in the program to 0x2000000.

So, start the driver, run the unlock program, then use flashctl to erase
the flash.


Dave Green (dgreen@qnx.com)

QNX Software Systems Ltd.
http://www.qnx.com

Dave Green wrote:

If it’s the devf-arcom driver
that I think it is, then it’s a single, 8M flash, 16 bits wide, mapped at
0x2000000.

So, start the driver, run the unlock program, then use flashctl to erase
the flash.

Wooohoooo, it worked, thank you!!!

Dana


Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast