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 - risototh

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Re: I2C Stop bit
« on: December 30, 2010, 01:11:40 PM »
Ok, finaly, i have some results.

The datasheet from Freescale is more than horrible...
First, the address is 0x60, yes, but as 7-bit number ommiting LSB (W/R) bit... Therefore, in 8-bit the address is 0xC0!!!
Next, the app note explains the R/W procedure as simple process without delays... Bullshit. I must wait between the first two writes approx 5 ms to get a valid result from the device!

That's all folks. I'm very disapointed of the datashit.
Thank for watching, and thanks also to http://188.65.57.204/showthread.php?s=5501d8932bfa9a12653b4eb4f56fd48c&t=15445

2
NXPTM M522XX, KINETIS and i.MX RT / Re: I2C Stop bit
« on: December 30, 2010, 12:05:28 PM »
Thanks Mark,

i tried your advice to wait some ms to complete the write and to send the stop bit. Unfortunately, same result.
Now, i don't know what to do next. The data send (and sniffed by a scope) are correct, but the sensor did not reply anything... I replaced the sensor with another one = same result...

Has someone tried to communicate with this sensor? Are there any hidden blackholes?

3
NXPTM M522XX, KINETIS and i.MX RT / I2C and MPL115A2
« on: December 29, 2010, 02:31:14 PM »
Hi folks,

i have one little problem. I would like to communicate with MPL115A2 sensor over I2C, but it is impossible to get data from it for me... Now i have a scope attached on I2C and probably i found where is the problem, but i don't know how to solve it.
I need to send/receive somtething like this (according to AN3785 from Freescale):
[Start], 0x60+[W], 0x12, 0x01,[Stop]
[Restart], 0x60+[W], 0x00
[Start], 0x60+[R]
, 0xMSB Pressure, 0xLSB Pressure, [Stop]

I call something like this:
#define ADR_PRESSURE         0x60
unsigned char wbuff_1[] = {ADR_PRESSURE, 0x12, 0x01};
unsigned char wbuff_2[] = {ADR_PRESSURE, 0x00};
unsigned char IIC_IO_read[] = {16, ADR_PRESSURE|0x01, TASK_PRVY_START};
fnWrite(IICPort, wbuff_1, sizeof(wbuff_1));
fnWrite(IICPort, wbuff_2, sizeof(wbuff_2));
fnRead(IICPort, IIC_IO_read, 0);

The problem (i mean) is between the two writes. According to the application note, there is one stop bit between the two writes (bold red one). But how i can make this stop bit? I looked at the scope, i found the start bit of the second write command, but no stop bit on the end of the first one. Can you help me with this? Or if you have some experience with communication with this sensor i uTasker, can you share the code snippet?

Thanks a lot and Marry Christmas.

EDIT: Subject name

5
µTasker general / Re: TCP/IP Offload problem with Vista
« on: June 25, 2008, 10:51:13 PM »
this solved my problem with w2003 described in http://www.utasker.com/forum/index.php?topic=310.0
i have intel pro/1000 nic, which has the ability doing the hw tcp/ip offload. because it's a ftp server, it was turned on. but, i solved this with turning off the the offload engine on transmit rather than receive side.
in the driver is written on Offload Transmit TCP Checksum: Disable this feature when the server is supporting DOS-based clients.
maybe the windows DOS mode networking is written like pcap?

6
NXPTM M522XX, KINETIS and i.MX RT / Re: Can't ping on local machine
« on: June 25, 2008, 09:25:41 PM »
it looks the same problem.
the strange one is, that the arp response from simulator works fine. at least the firt one ;)

7
NXPTM M522XX, KINETIS and i.MX RT / Can't ping on local machine
« on: June 24, 2008, 10:59:55 PM »
I've successfully compiled the uTasker v1.3 SP7 with MS Visual Studio 6.0 under Windows 2003 Enterprise. I can't ping the running simulator on the same machine, but i can do it from any remote machine in the network.
I haven't any firewall installed, nor any network anti-virus sw.
Does anybody know, where the problem lies?

Pages: [1]