Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Administrator

Pages: [1] 2 3 ... 12
1
Ethernet Boards (8-bit) / Re: images change without flickering
« on: August 31, 2008, 11:41:38 PM »
Hello Kometen

Glad to hear you solved the problem. You could also have a look at some of the web pages provided with the Microchip TCP/IP demo stack. I kind of remember one of their example applications showed red and green images that changed with the state of the port pins.

2
Ethernet Boards (8-bit) / Re: SBC65EC new user
« on: August 20, 2008, 07:36:55 PM »
If you programmed the board with firmware that does not work, you have to start the board in safemode and use the "Modtronix Network Bootloader" to restore the original firmware hex file AND web pages.

The procedure for doing this is described in detail on the online documentation here.

3
Ethernet Boards (8-bit) / Re: 25LC1024 vs 24LC512
« on: August 18, 2008, 12:06:49 AM »
Hello

You have to do software and hardware changes to use the 25LC1024 chip.

Hardware:
You have to make solder jumper J5, and break solder jumper J6 on the back of the board. By default, J6 is made, and J5 is open. See schematics for details.

Software:
Some software changes are required I think. Have not looked into this too much. I think people on this forum have done it. Search for 25LC1024 on forum.

4
Ethernet Boards (8-bit) / Re: Display the client IP
« on: August 21, 2006, 10:26:18 PM »
You will have to create tags for displaying this information on your web page. There are currently no tags for doing this. You will have to add code to do this in the HTTPGetVar() function in the "httpexec.c" file.

5
Ethernet Boards (8-bit) / Re: Digital Inputs Problem with SBC65EC
« on: August 21, 2006, 10:18:03 PM »
Hello

Port RB6 (board LED) is by default controlled by the software, and will flash. If you want to control the board's LED, you have to disable this functionally on the "System Setting" page of the web based configuration for the SBC65EC.

There is also an error in your code. You are reading the value of LATG0. See the PIC18F6627 datasheet for details on port latches. The latch is only for writing outputs to the port. When you read a latch, you will read the last value you wrote to the port, NOT the input on that port. To read the input value of a port, you have to read the port pin, NOT the latch. Replace LATG0 in your code with PORTG_RG0.

6
Programming / Re: fsee EEprom Routines....
« on: August 21, 2006, 10:01:24 PM »
Hi

As far as I know you can write each location of the EEPROM 1,000,000 times. For your application you will be writing different locations all the time, is that right? You should have no problem. For details, download Microchip's Endurance Calculation Software. See:
www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010003

7
Ethernet Boards (8-bit) / Re: Help compiling SBC68EC rev 3.04
« on: August 21, 2006, 09:56:14 PM »
Hello Jaa

For MPLAB7.30 and C18 V3.02 you have to use SBC68EC rev 3.04 source code. You say you have done this, but still get errors. It should work. Please confirm the following:

1) You have configured MPLAB for the PIC18F6680 chip. You do that via the <Configure><Select Device...> menu in MPLAB. Then select the PIC18F6680 chip.

2) If your MPLAB C18 compiler is not in stalled at "c:\mcc18v302", then follow the steps in the documentation. See "Program Versions" section on "Building The Project" page:
www.modtronix.com/products/sbc68ec/websrvr68_v304/page_build_project.html

3) If it still fails, please email me whole build output. Please send to david <at> modtronix.com - replace <at> with email at sign.


8
Development Kits / Re: New beta code for DEVKIT44B
« on: August 08, 2006, 08:28:30 PM »
Yes, the USB boards will be shipped with the free Microchip Bootloader programmed onto it. Microchip has C code for a couple of different USB implementations on their site. All code can be compiled with their free MPLAB and C18 tools.

9
Hello Thierry

Thanks for your mail. I will add your fixes to the next release of our TCP/IP stack! I guess it is OK if I put your name in the change log of the TCP/IP stack?

10
Development Kits / Re: New beta code for DEVKIT44B
« on: August 08, 2006, 02:23:42 PM »
Hello

The LCD3S board has now gone into production. It will however still take a couple of weeks for the first boards to be available.

The first USB board will be the SBC44UC, and will use the PIC18F4550 44 pin USB chip. The SBC board has the same format as our other compact SBC boards, and will be pin compatible. The SBC44UC board can be USB powered, or powered via an external 7V - 30V transformer. It also has a socket for an MCP23008 and a external EEPROM. Space is also provided for a RAMTRAN chip to be assembled. It has the standard MicroX daughter and frontend board connectors. It also has a Micro Match connector with I2C and SPI signals - this connector can be connected to the LCD3S serial LCD display for example. For schematics and layout see www.modtronix.com/products/sbc44uc/sbc44ucr1.pdf

New USB board will be a full size USB board like the SBC44B. It will probably have USB and I/O connectors. Design has not been finalized yet.

11
Projects / Sprinkler Controller using the IOR5E and SBC65EC
« on: August 08, 2006, 02:03:54 PM »
Helmut Hissen from Zeebar Technology has created a nice web page documenting how to turn the IOR5E and SBC65EC into a sprinkler controller. For details, see www.zeebar.com/notes/modtronix.html

12
IOR5E / Turning the IOR5E into a Sprinkler Controller
« on: August 08, 2006, 02:01:49 PM »
Helmut Hissen from Zeebar Technology has created a nice web page documenting how to turn the IOR5E and SBC65EC into a sprinkler controller. For details, see www.zeebar.com/notes/modtronix.html

13
Development Kits / Re: New beta code for DEVKIT44B
« on: August 06, 2006, 03:58:20 PM »
Hello

Not yet, but I will soon add that. The MCP23008 and MCP23016 will also be used in some new boards. Two new USB boards will soon be released that use the MCP23008 chip. One is a compact SBC board, and the other a full size board. The compact SBC board has gone into prototyping stage, and will soon go into production.


14
Ethernet Boards (8-bit) / == Compatible third party boards ==
« on: June 18, 2006, 11:33:50 PM »
The following section list some compatible third party boards that can be used to add additional functionality to our MicroX SBC boards.

=== LCD Board for the SBC65EC and SBC68EC boards =====
A LCD board with LED backlight, RTC, 1-wire bus master is available from SKPang here.

=== RTC and 1-Wire Daughter board for the SBC65EC and SBC68EC boards ===
RTC and 1-Wire Bus Master for the SBC65EC and SBC68EC is available from SKPang here.

=== Metal Enclosure for the SBC44EC and SBC45EC boards ===
A metal enclosure for the SBC44EC and SBC45EC is available from SKPang here.

If you have any custom boards you would like listed here, please contact us.

15
Ethernet Boards (8-bit) / Re: Some detail questions....
« on: June 06, 2006, 04:04:05 PM »
Hello

Sorry about the delay with the RAMTRON functions. It will hopefully be added to the next version of the TCP/IP stack. No release date has however been set yet.

Regarding your second question. By default, you can only use one bank (256 bytes) for a single section with the MPLAB C18 compiler. To use more, you have to define the section in your linker. This is what we did in the TCP/IP stack for the TCP_SOCKET_INFO_SEG section.

Have a look in the "18f6627_v302.lkr" file. Databanks 12 and 13 have been commented out, and their space used for the TCP_SOCKET_INFO_SEG section. This section is then used in the "tcp.c" file to declare an array that is larger than 256 bytes. The code in "tcp.c" is:
Code: [Select]
    #pragma udata TCP_SOCKET_INFO_SEG
    SOCKET_INFO TCB[MAX_SOCKETS];
    #pragma udata   //Return to default section

You can use this same method to declare your structure. Do the following:

1) Reserve some data in the linker file (see in your project in MPLAB what linker file is use). For example, if you are using the "18f6627_v302.lkr" file, you can replace the following lines:
Code: [Select]
DATABANK   NAME=gpr10      START=0xA00          END=0xAFF
DATABANK   NAME=gpr11      START=0xB00          END=0xBFF
with:
Code: [Select]
//Reserve 128 + 256 bytes = 384 bytes for custom section
DATABANK   NAME=gpr10      START=0xA00          END=0xA7F
//DATABANK   NAME=gpr10      START=0xA00          END=0xAFF
//DATABANK   NAME=gpr11      START=0xB00          END=0xBFF

2) Next, you have to declare your new section in the "18f6627_v302.lkr" file. Add the following to the end of the "18f6627_v302.lkr" file:
Code: [Select]
DATABANK   NAME=MY_384BYTE_SEG      START=0xA80          END=0xBFF

3) Now, you can use this 384 bytes segment in your code. You have to define your structure as follows:
Code: [Select]
    #pragma udata MY_384BYTE_SEG
    struct{
        BYTE  dataByte0[128];
        BYTE  dataByte1[128];
        unsigned int dataWord[28];
      }DATA_BYTES;
    #pragma udata   //Return to default section

You could actually reduce your segment to 128 + 128 + 28 = 284 bytes for your structure. To do this, replace the code in your linker file with:
Code: [Select]
//Reserve 256 + 28 bytes = 384 bytes for custom section
DATABANK   NAME=gpr10      START=0xA00          END=0xAE3    //Leave last 28 bytes free
//DATABANK   NAME=gpr10      START=0xA00          END=0xAFF
//DATABANK   NAME=gpr11      START=0xB00          END=0xBFF


To check amount of free RAM, you have to tell the compiler to create a MAP file. You then have to look at the RAM defined in your MAP file, and sort of figure out what is left. This is a really bad way of doing it, maybe someone knows of an easier way? It is very simple with the HiTech compiler, seeing that it tells you exactly how much ram is used, and what is left.

Pages: [1] 2 3 ... 12