MON390: Maxim TINI Board Software Problems

Information in this article applies to:

• C51 All Versions

SYMPTOM

When using the Maxim (formerly Dallas Semiconductor) TINI boards with the Maxim DS80C390 or DS80C400, problems may occur if you use the on-board TCP/IP network stack and if your application uses DATA memory below 0x20.

CAUSE

The TINI board uses memory in the register bank 2 and 3 address space (0x10-0x1F) for the TCP/IP stack implementation. If your application also uses memory in this space, it may be corrupted by calls into the networking API.

RESOLUTION

Avoid using this memory area. You can use the linker's DATA directive to specify a new starting address for DATA objects. For example:

lx51 ... DATA(0x20)

specifies that DATA space begins at 0x20. This directs the linker to begin locating DATA objects at 0x20 (which avoids the memory used by the TINI TCP/IP stack).

Check your TINI documentation thoroughly for any other memory areas that may not be available to your application.

MORE INFORMATION

• MON390: Cannot Connect to Maxim Tini 400's Serial Port 0
• MON390: Redirecting Interrupt Vectors
• MON390: Downloading MON390 Into the Maxim/Dallas TINI Board Using Keil
• ISD51: Does ISD51 Work with the Maxim 390, 5240, or 400?

SEE ALSO

• Refer to Project in the µVision3 User's Guide.
• C51: Maxim 390 Math Accelerator Operations
• C51: Configuring Dallas 390 and 400 for Contiguous Mode
• MON390: CANNOT CONNECT TO DALLAS DS80C400 ON THE DS-TINI-1 B
• C51: Memory Types for Maxim 390 Contiguous Mode

Last Reviewed: Thursday, February 25, 2021