Skip to main content ↑ ↓

Messages

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

Messages - ian

8596
Hack a Day projects / Re: Updated software
I'm interested in upgrading to the latest TCP/IP stack (v5.0), and perhaps substituting a pin-compatible dsPIC33 for the 24FJ64GA002.
8597
Bus Pirate Support / Re: I2C, no ACK at random times
As you'll note on your LA, the byes come in squirts while the terminal waits to push characters through the serial port. That could also be a potential issue.

There's a three byte UART hardware buffer, but the long term goal (on the issue tracker) is to have a big buffer (2000K?) that feeds the serial TX on an interrupt.
8605
Bus Pirate Support / Re: I2C, no ACK at random times
Fozzy Vis and I have been discussing this issue by e-mail before moving it here. I'll have one of these chips to work with in a day.

What happens if you use a full stop and start sequence instead of a repeated start?
Quote
[0xd0 1 [0xd1 r] >>> [0xd0 1 ][0xd1 r]

I'd look at how the code handles the repeated start. I didn't write the I2C library, it's GPL'd code from an example site. It's always worked fine for me, so I've never bothered with it. Maybe we should write a public domain version with more options?

The speed issue is a possibility. I second a speed option that reduces the delays in the I2C library, either as a setup step or as a configuration macro(#). It would probably be worth checking I2C.c and base.c for delay problems too, for a while there was a variable type overflow problem with one of the delays but I think I caught it a while back.

The latest nightly build adds version check with the 'i' menu. PIC revisions: A3/A4=0x3003, B4=0x3042, B5=0x3043
8606
Bus Pirate Support / Re: Hardware I2C master and slave
Thanks, I'll apply the patch.

v0a and v2 (both) should have pull-ups.

The three digit numbers, and sometimes just XXX, that precede output in older demos and code was supposed to be an RFC977-style (USENET) coding system so GUIs could interact with the Bus Pirate. I dropped it when I implemented the centralized terminal translation system that recycles the same text messages for each library.

What revision PIC do you have?
8607
Bus Pirate Support / Re: Hardware I2C master and slave
The Bus Pirate code (with a few exceptions) is a public domain/creative commons '0' licensed project, could you please release your patch under the same. I'm going to ask patch contributors to acknowledge this once, or include the license in their patch, so there's no confusion later on.

Built in functions sound great, I hadn't hunted them down yet. I've just been working with the example code from the datasheet to see how table read works.

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01692425544session_write_close ( )...(null):0
20.01722557168ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01722557944Database_MySQL->query( ).../DatabaseHandler.php:119
40.06142696704Database_MySQL->error( ).../Db-mysql.class.php:273