| by admin | No comments


Part and Inventory Search. IEE Floating Point addition 7. I’ll give the scope a try and compare to the LA though. Radiation Detection Circuit 1. On , at So, I’m guessing you have not looked at the bus with a scope at this point And it doesn’t have to be fancy.

Uploader: Kajikasa
Date Added: 16 February 2006
File Size: 59.37 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 98053
Price: Free* [*Free Regsitration Required]

I’ll also have a look at your code and see if we’re doing something differently. I haven’t poured over the datasheet, mmsp430f5438 taking a look.

Protecting the IoT with Invisible Keys. It is skewed one bit when you load it into the MSP register. I would not worry about looking at the buss with the scope from here unless to check voltage levels. How do i check whether an I2C device works? Ic2 for the help.

Heat sinks, Part 2: Onat 9: Related to source pull simulation for rectifier 0. Look closely at the address.

I2C troubles

Low Look closely at the address. Friday, December 04, How to upload a counter value to a website automatically 3. It says you will see the ack on the buss and I’m taking it you did see the ack with the logic analyzer.


How can the power consumption for computing be reduced for energy harvesting? Embedded Software Engineer Loft Orbital’s mission is to make space simple for organizations that need My I2C stuff here Why I am getting this substrate picture, when i create a new workspace?

Check my I2C code for interfacing MSPf and MCP

u2c I’ll give the scope a try and compare to the LA though. I’m using port 2 but have tried port 1 as well – i. Does that LA show levels or just state? Amplifier Yamaha RX-V not turning on If I’m not mistaken, on the 1xx USART this first byte is kind of hardwired to the I2C hardware, in that you have to disable it put into reset state if you want to change the bits chip-address, not memory address on the control byte.

msp | I2C troubles

So if the first control byte is not ACKed, you have a problem with the control byte you’re sending so you can forget about the rest of the bytes. Part and Inventory Search. Dec 248: After sending the start bit i am getting NACK whats the problem i dont understand if anyone find any bugs in my code please told me.


I guess by ‘internal msp430f438 you i2x the I2C hardware and not an application included software I2C, right? I and a friend have gone over the data from the LA and compared it with the datasheet in agonizing detail and it looks right.

The meaning of the bytes after the first one depends on the Msp43f05438 slave you’re using. The time now is Ultrasonic transducer driver 1. There are pullups on the bus, it’s point-to-point, voltages are good, logic analyzer interprets the I2C protocol and everything looks fine address sent correctly, etc.

That’s the thing that NAKs.