EM500W |
Top Previous Next |
Memory space
RAM |
EM500W: 17,920* bytes for application variables and data |
Flash |
327,680 bytes for application storage, data cannot be stored in this memory |
EEPROM |
200 bytes for application data |
* RAM available in the debug mode is smaller by 257 bytes. All memory is available in the release mode.
Supported Objects, variable types, and functions
•Sock — socket communications (up to 16 UDP, TCP, and HTTP sessions);
•Net — controls the Ethernet port;
•Wln — handles the Wi-Fi interface (requires GA1000 add-on module);
•Ser — in charge of the serial port (UART, Wiegand, and clock/data modes);
•Io — handles I/O lines, ports, and interrupts;
•Fd* — manages flash memory file system and direct sector access (requires an externally connected flash IC);
•Stor — provides access to the EEPROM;
•Romfile — facilitates access to resource files (fixed data);
•Pppoe — provides access to the Internet over an ADSL modem;
•Ppp — provides access to the Internet over a serial modem (GPRS, POTS, etc.);
•Pat — "plays" patterns on a pair of LEDs;
•Button — monitors the MD line (setup button);
•Sys — in charge of general device functionality.
* Fully supported with the exception of fd.copyfirmware. Disabled by default -- enable it in Project Settings -> Customize.
This platform supports the standard set of variable types and functions (a.k.a. "syscalls") except aes128enc and aes128dec. These AES128 functions are not present on the EM500W platform.
Platform-specific constants
You can find them here.
Miscellaneous information
Available network interfaces |
Ethernet (net.)(1) |
Bidirectional |
|
Not supported(2) |
|
Not supported(3) |
|
16 byte for TX, 16 bytes for RX |
|
Not supported, frequency is fixed at 80MHz |
|
8 bytes for MAC storage |
|
4 bytes, the number can't be changed |
|
Dedicated memory for firmware/application Data cannot be stored in this memory |
|
Green (SG) and red (SR) Status LED lines (their brightness indicates Ethernet link status) One additional dedicated link status LED line |
|
Ethernet / UDP Broadcast transport Ethernet /WinPCap transport |
Comments:
1.The sock.allowedinterfaces property refers to the Ethernet interface as "NET". Sock.targetinterface and sock.currentinterface properties rely on the pl_sock_interfaces enum, whose members differ depending on the platform.
2.CTS is permanently mapped to 0- PL_INT_NUM_0 (0- PL_IO_NUM_0_INT0). RTS is permanently mapped to 2- PL_IO_NUM_2.
3.Connect the GA1000 add-on module as follows (also see schematic diagram C in Connecting GA1000):
CS |
|
CLK |
|
DI |
5- PL_IO_NUM_5 (yes, DI and DO lines are on the same GPIO line) |
DO |
|
RST |
Choose any suitable GPIO or use NAND gates to generate reset |