This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Lpc2368 communication

Hello,
I want communicate with my lpc2368 by the Ethernet port using an application whose create with visual basic.
It is possible ?
How ?

Thanks,

Mickael

Parents
  • Needing five languages is tough. I only implement english.

    I have a 12-byte table keeping track of all parameters. Two bytes are the parameter index (can be optimizaed away if parameter list doesn't contain any holes, but I also store a bit there to inform if the parameter is read-only or may be written). Two bytes indicates data type and formatting (such as shown in table, separation into different pages, ... A few "data types" represents callback functions) Four bytes represents memory address. Can be shrunk to two bytes since the LPC2368 has less than 64kB RAM. 4kB of the address space can be used to point at a configuration sector in flash. Four bytes points to a text string. The average string size is less than 20 bytes but with 20 bytes, 1000 parameters would take less than 32kB of code space to describe. I normally only need a fraction of that count. Maybe 100 .. 250 parameters.

    I may have maybe 2-3kB boiler-plate HTML/CSS, but the rest is dynamically built based on the formatting information.

    In reality, some data types are of type "two 32-bit unsigned", or similar - for example to retrieve debug info about # of received and transmitted bytes on a link as a single snapshot parameter.

Reply
  • Needing five languages is tough. I only implement english.

    I have a 12-byte table keeping track of all parameters. Two bytes are the parameter index (can be optimizaed away if parameter list doesn't contain any holes, but I also store a bit there to inform if the parameter is read-only or may be written). Two bytes indicates data type and formatting (such as shown in table, separation into different pages, ... A few "data types" represents callback functions) Four bytes represents memory address. Can be shrunk to two bytes since the LPC2368 has less than 64kB RAM. 4kB of the address space can be used to point at a configuration sector in flash. Four bytes points to a text string. The average string size is less than 20 bytes but with 20 bytes, 1000 parameters would take less than 32kB of code space to describe. I normally only need a fraction of that count. Maybe 100 .. 250 parameters.

    I may have maybe 2-3kB boiler-plate HTML/CSS, but the rest is dynamically built based on the formatting information.

    In reality, some data types are of type "two 32-bit unsigned", or similar - for example to retrieve debug info about # of received and transmitted bytes on a link as a single snapshot parameter.

Children