Re: Need some help with the TINI EVAL Kit

"Kris Ardis" <Kristopher.Ardis-6tN4nzCoH/[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.tini
Message-ID <00ed01c3fd6f$9173fa00$764000b4@kardis>
> Now why is it that the dallas app. note on getting started with Keil
> says to put 0x10000 as off-chip RAM start and length 0x3FFF in the
> target options dialog box and not the SRAM configuration mentioned
> above?

Please see the page at the C library web site on memory configuration
(ftp://ftp.dalsemi.com/pub/tini/ds80c400/c_libraries/memory.html).  The
memory listed here is only for Keil variables.  There are other memory
spaces needed by programs using the 400 ROM, such as space for ROM system
variables, memory manager, and a possible file system.

> Also, why is that for the init_rom(RAM_START,RAM_END) function
> most of the sample programs have RAM_START ->0x14000 and RAM_END ->
> 0x5FFFF. This is very confusing and an explanation would be much
> appreciated.

There are also some examples that declare the file system for 0x60000 to
0x7FFFF.  Since most of the examples have a certain amount of cut-and-paste
from the other ones, many of their configurations look similar.  They are
only meant to be examples, and real applications will tweak these numbers to
their needs.

> I have followed the sample socket app and the rom400_sock.h file
> documentation on using the socket creation commands but my program never
> creates a socket successfully. Once again I would appreciate any help in
> figuring out this problem. Thanks.

Can you post any code snippets you are using, and also talk about the return
codes of the functions?  You can check the file rom400_err.h for information
on the return codes.

Kris



_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.