/*------------------------------------------------------------------------------------------------------------*/
void cgi_reset( void * pStruct )
{
struct HTTP_REQUEST * http_request;
http_request = (struct HTTP_REQUEST *) pStruct;
cgi_PrintHttpheaderStart();
if ( http_request->argc == 0 )
{
printf_P( PSTR( "<form action=\"reset.cgi\" method=\"get\" accept-charset=\"ISO-8859-1\">"
"<p><input type=\"submit\" name=\"reset\" value=\"reset\"></p></form>" ));
cgi_PrintHttpheaderEnd();
}
else if( PharseCheckName_P( http_request, PSTR("reset") ) )
{
if ( !strcmp_P( http_request->argvalue[ PharseGetValue_P( http_request, PSTR("reset") ) ] , PSTR("reset") ) )
{
printf_P( PSTR("Reset"));
cgi_PrintHttpheaderEnd();
STDOUT_Flush();
CloseTCPSocket( http_request->HTTP_SOCKET );
softreset();
while(1);
}
}
}
/* -----------------------------------------------------------------------------------------------------------*/
void LEDTAFEL_process_cmd( struct TAFEL_CMD_HEADER * CMD )
{
switch( CMD->TAFEL_CMD )
{
case write_raw: LEDTAFEL_copy_screen( CMD->TAFEL_DATA, CMD->TAFEL_X, CMD->TAFEL_Y, CMD->TAFEL_W, CMD->TAFEL_H );
CMD->TAFEL_CMD = ack;
break;
case write_lum_raw: LEDTAFEL_copy_screenlum( CMD->TAFEL_DATA, CMD->TAFEL_X, CMD->TAFEL_Y, CMD->TAFEL_W, CMD->TAFEL_H );
CMD->TAFEL_CMD = ack;
break;
case intensity: LEDTAFEL_set_intensity( CMD->TAFEL_DATA[0] );
CMD->TAFEL_CMD = ack;
break;
case clear: LEDTAFEL_set_clearscreen();
CMD->TAFEL_CMD = ack;
break;
case hardreset: CMD->TAFEL_CMD = ack; // trotzdem nen ACK senden!
softreset();
while(1);
case fade_out: LEDTAFEL_fadeout_display( (int) CMD->TAFEL_DATA[0] , LEDTAFEL_screenlum );
CMD->TAFEL_CMD = ack;
break;
case graphic_direct: LEDTAFEL_graphic_direct( CMD->TAFEL_DATA, CMD->TAFEL_X,CMD->TAFEL_Y, CMD->TAFEL_W );
CMD->TAFEL_CMD = ack;
break;
default: CMD->TAFEL_CMD = nak;
}
}
void initialize_lcd_dri() {
initialize(0);
softreset(0);
ev3_driver_t driver;
driver.init_func = NULL;
driver.softreset_func = softreset;
SVC_PERROR(platform_register_driver(&driver));
}
/*---------------------------------------------------------------------------*/
static void
reset(void)
{
PRINTF("enc28j60: resetting chip\n");
enc28j60_arch_spi_init();
/*
6.0 INITIALIZATION
Before the ENC28J60 can be used to transmit and receive packets,
certain device settings must be initialized. Depending on the
application, some configuration options may need to be
changed. Normally, these tasks may be accomplished once after
Reset and do not need to be changed thereafter.
6.1 Receive Buffer
Before receiving any packets, the receive buffer must be
initialized by programming the ERXST and ERXND pointers. All
memory between and including the ERXST and ERXND addresses will be
dedicated to the receive hardware. It is recommended that the
ERXST pointer be programmed with an even address.
Applications expecting large amounts of data and frequent packet
delivery may wish to allocate most of the memory as the receive
buffer. Applications that may need to save older packets or have
several packets ready for transmission should allocate less
memory.
When programming the ERXST pointer, the ERXWRPT registers will
automatically be updated with the same values. The address in
ERXWRPT will be used as the starting location when the receive
hardware begins writing received data. For tracking purposes, the
ERXRDPT registers should additionally be programmed with the same
value. To program ERXRDPT, the host controller must write to
ERXRDPTL first, followed by ERXRDPTH. See Section 7.2.4 “Freeing
Receive Buffer Space for more information
6.2 Transmission Buffer
All memory which is not used by the receive buffer is considered
the transmission buffer. Data which is to be transmitted should be
written into any unused space. After a packet is transmitted,
however, the hardware will write a seven-byte status vector into
memory after the last byte in the packet. Therefore, the host
controller should leave at least seven bytes between each packet
and the beginning of the receive buffer. No explicit action is
required to initialize the transmission buffer.
6.3 Receive Filters
The appropriate receive filters should be enabled or disabled by
writing to the ERXFCON register. See Section 8.0 “Receive Filters
for information on how to configure it.
6.4 Waiting For OST
If the initialization procedure is being executed immediately
following a Power-on Reset, the ESTAT.CLKRDY bit should be polled
to make certain that enough time has elapsed before proceeding to
modify the MAC and PHY registers. For more information on the OST,
see Section 2.2 “Oscillator Start-up Timer.
*/
softreset();
/* Workaround for erratum #2. */
clock_delay_usec(1000);
/* Wait for OST */
while((readreg(ESTAT) & ESTAT_CLKRDY) == 0);
setregbank(ERXTX_BANK);
/* Set up receive buffer */
writereg(ERXSTL, RX_BUF_START & 0xff);
writereg(ERXSTH, RX_BUF_START >> 8);
writereg(ERXNDL, RX_BUF_END & 0xff);
writereg(ERXNDH, RX_BUF_END >> 8);
writereg(ERDPTL, RX_BUF_START & 0xff);
writereg(ERDPTH, RX_BUF_START >> 8);
writereg(ERXRDPTL, RX_BUF_END & 0xff);
writereg(ERXRDPTH, RX_BUF_END >> 8);
/* Receive filters */
setregbank(EPKTCNT_BANK);
writereg(ERXFCON, ERXFCON_UCEN | ERXFCON_CRCEN | ERXFCON_BCEN);
/*
6.5 MAC Initialization Settings
Several of the MAC registers require configuration during
initialization. This only needs to be done once; the order of
programming is unimportant.
1. Set the MARXEN bit in MACON1 to enable the MAC to receive
frames. If using full duplex, most applications should also set
TXPAUS and RXPAUS to allow IEEE defined flow control to function.
2. Configure the PADCFG, TXCRCEN and FULDPX bits of MACON3. Most
applications should enable automatic padding to at least 60 bytes
and always append a valid CRC. For convenience, many applications
may wish to set the FRMLNEN bit as well to enable frame length
status reporting. The FULDPX bit should be set if the application
will be connected to a full-duplex configured remote node;
otherwise, it should be left clear.
3. Configure the bits in MACON4. For conformance to the IEEE 802.3
standard, set the DEFER bit.
4. Program the MAMXFL registers with the maximum frame length to
be permitted to be received or transmitted. Normal network nodes
are designed to handle packets that are 1518 bytes or less.
5. Configure the Back-to-Back Inter-Packet Gap register,
MABBIPG. Most applications will program this register with 15h
when Full-Duplex mode is used and 12h when Half-Duplex mode is
used.
6. Configure the Non-Back-to-Back Inter-Packet Gap register low
byte, MAIPGL. Most applications will program this register with
12h.
7. If half duplex is used, the Non-Back-to-Back Inter-Packet Gap
register high byte, MAIPGH, should be programmed. Most
applications will program this register to 0Ch.
8. If Half-Duplex mode is used, program the Retransmission and
Collision Window registers, MACLCON1 and MACLCON2. Most
applications will not need to change the default Reset values. If
the network is spread over exceptionally long cables, the default
value of MACLCON2 may need to be increased.
9. Program the local MAC address into the MAADR1:MAADR6 registers.
*/
setregbank(MACONX_BANK);
/* Turn on reception and IEEE-defined flow control */
setregbitfield(MACON1, MACON1_MARXEN | MACON1_TXPAUS | MACON1_RXPAUS);
/* Set padding, crc, full duplex */
setregbitfield(MACON3, MACON3_PADCFG_FULL | MACON3_TXCRCEN | MACON3_FULDPX |
MACON3_FRMLNEN);
/* Don't modify MACON4 */
/* Set maximum frame length in MAMXFL */
writereg(MAMXFLL, MAX_MAC_LENGTH & 0xff);
writereg(MAMXFLH, MAX_MAC_LENGTH >> 8);
/* Set back-to-back inter packet gap */
writereg(MABBIPG, 0x15);
/* Set non-back-to-back packet gap */
writereg(MAIPGL, 0x12);
/* Set MAC address */
setregbank(MAADRX_BANK);
writereg(MAADR6, enc_mac_addr[5]);
writereg(MAADR5, enc_mac_addr[4]);
writereg(MAADR4, enc_mac_addr[3]);
writereg(MAADR3, enc_mac_addr[2]);
writereg(MAADR2, enc_mac_addr[1]);
writereg(MAADR1, enc_mac_addr[0]);
/*
6.6 PHY Initialization Settings
Depending on the application, bits in three of the PHY module’s
registers may also require configuration. The PHCON1.PDPXMD bit
partially controls the device’s half/full-duplex
configuration. Normally, this bit is initialized correctly by the
external circuitry (see Section 2.6 “LED Configuration). If the
external circuitry is not present or incorrect, however, the host
controller must program the bit properly. Alternatively, for an
externally configurable system, the PDPXMD bit may be read and the
FULDPX bit be programmed to match.
For proper duplex operation, the PHCON1.PDPXMD bit must also match
the value of the MACON3.FULDPX bit.
If using half duplex, the host controller may wish to set the
PHCON2.HDLDIS bit to prevent automatic loopback of the data which
is transmitted. The PHY register, PHLCON, controls the outputs of
LEDA and LEDB. If an application requires a LED configuration
other than the default, PHLCON must be altered to match the new
requirements. The settings for LED operation are discussed in
Section 2.6 “LED Configuration. The PHLCON register is shown in
Register 2-2 (page 9).
*/
/* Don't worry about PHY configuration for now */
/* Turn on autoincrement for buffer access */
setregbitfield(ECON2, ECON2_AUTOINC);
/* Turn on reception */
writereg(ECON1, ECON1_RXEN);
}
int cmd_reset( int argc, char ** argv )
{
softreset();
return(0);
}