Search found 45 matches

As others have already told you repeatedly, your oscillator configuration is way off. You're blinking an LED at either 500/500ms on/off or 100/100ms on/off but your animated picture shows your LED bli ...

Finally, as you can see I was in the process of converting the routines to programmatically derive the socket register locations and not be dependent on hard coded S0 through S7 values in the w5200.h ...

To add to the above, here's routines to open a TCP socket and open it, print a banner upon connection, listen on it for data, and write the data out to the first serial port. Works the same as the udp ...

I meant to post this code some time ago, but I always wanted to clean it all up and merge it with some W5100 code I'd been working on and work out a set of #DEFINEs so that the end user could switch b ...

Sadly, there's no difference. Mode 3 versus mode 1, the results are the same..

I use standard SPI to write to my WS2801 strips. A 4mhz SPI clock works fine.

There isn't much to these, you just need to spi_write() your rgb values times number of pixels on the strip, then pause ...

Well, you were right on the money there.

Judicious use of delay_cycles(16) does indeed have the code running at SPI_CLK_DIV_64..

The bad news? The problem that existed @4mhz SPI exists at 1mhz S ...

Out came the logic analyzer again and double checked everything.

The RTC is definitely returning the expected/proper data. The different SPI clock frequencies are definitely working.

I think at ...

Aha. Thanks! That makes more sense..

Sadly, it doesn't seem to help much. Changing my setup_timer_2 statement to EACH of the examples you gave yields the same results as I was seeing with a 4mhz cl ...

An interesting tidbit - I seem to hang when I call spi_write(0) or spi_write(0x00).

I recompiled and ran under the debugger. I can get as far as spi_write(0x8E) and the next spi_write(0x00) I never ...

Can't get T2 to clock slow enough.. the slowest is T2_DIV_BY_16 which, at 64mhz, is no different than SPI_CLK_DIV_16.

I've tried compiler version 5.011 and 4.141.

Same thing both times. My progr ...

So, after taking a couple of days off and fiddling around (rebuilt a whole new circuit on a breadboard) I've finally gotten somewhere (and I found out my hardware isn't faulty Smile

.

First - it seems ...

.. and as quickly as that I'm on to something..

Change SPI MODE to 3 and it looks like it may be working.. I'll keep quiet for now ;)

OK, so stripped down to just RTC access I'm still seeing the same thing:

sample main function:

void main()
{
unsigned int8 i;
BYTE hr,min,sec;

output_high(W5200_RS ...

Good idea. This is a new piece of hardware and I've been testing each piece bit by bit (first the eeprom, then the wiz820io, finally the RTC). What I didn't do was disable each piece (the first two wo ...