RE: 80c400 rom error codes

John,

This does not answer your question but...

Two things you should try that might eliminate those errors.

1)  Do not use "init_rom(RAM_START, RAM_END);".  Use the following instead:
    init_clearXSEG();
    init_copyivt();
    init_redirect();
    init_clearSystemRAM();
    init_mm(RAM_START, RAM_END);
    kmem_init(ROM400_KMEM_MODEL_SMALLEST + 2);
    init_ow(INIT_DIVISOR_28MHZ);
    init_network();
    init_eth();
    init_sockets();
    init_tick();
    task_genesis(ROM_SAVESIZE);
    init_enableinterrupts();
    task_settickreload(RELOAD_14_746);  // Necessary for accurate timing.
    clear_param_buffers();              // Necessary to make the network
stack behave.

2)  When you call task_fork() use a number larger than 384 (which is
ROM_SAVESIZE) for the second parameter.  Try 768 or even 1024.  I was having
problems with 512. eg: task_fork(NORM_PRIORITY, 1024);

Regards,
Bob Heise



-----Original Message-----
From: tini-admin-6tN4nzCoH/hBDgjK7y7TUQ@xxxxxxxxxxxxxxxx 
[mailto:tini-admin@xxxxxxxxxxx]On Behalf Of
john bogus
Sent: Wednesday, June 25, 2003 1:10 PM
To: tini-6tN4nzCoH/hBDgjK7y7TUQ@xxxxxxxxxxxxxxxx
Subject: [TINI] 80c400 rom error codes


We have been developing 'C' code for the 80c400 and
have been getting some unkown errors (non 0 return
values) back from from the rom calls (in particularly
the "connect" and "send" functions).  Does anyone know
what the error codes (return values) for these
functions mean?

Thanks

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/hBDgjK7y7TUQ@xxxxxxxxxxxxxxxx
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini

_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/hBDgjK7y7TUQ@xxxxxxxxxxxxxxxx
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini