Messages

Does anyone have any thoughts on how to create and I2C monitor using an NXP 924/5/936 variant?  I want to create something that can just sit on the line transparently and record data to a GUI (which is already built and running).  The device would obviously be a slave, but the real problem is having it just read the bus and record the data and address being sent.  I figured using the I2C interrupt slave code would work here, but that requires a specific address.  Since the code architect code is interrupt driven, I figured this would be the smartest way to get the data stream instead of polling the lines and possibly missing data. 

I have a PIC MPU 18F4550 that is acting as a USB to I2C read/write interface to the GUI, and it can not seem to handle the USB stack and monitor the bus at the same time.   So I figured a slave I2C device that is dedicated to just listening and recording the data to a FIFO (thinking I2C EEPROM or RAM as a buffer in the NXP device) to transfer to the PIC to the GUI.

I know an fpga or cpld can do this probably faster and more efficient but I'd like to stay with an NXP device and dont' want to have to deal with a BGA device.  Google doesn't really have anything useful since the biggest hurdle is how to get the slave to record the devices address and data without having to be directly spoken too.  Any thoughts or direction? 

Andy,

I was using a wall wart to power the application board, with other devices consuming power, I believe it browned out during programming due to the lack of current from the wall wart (it was toasty when I realized what was going on).   I moved to a new house, so I couldn't find my power supply, after I did find it, it programs normally and both methods work.  So I believe the wall wart was the issue at hand and not the hardware.

This is more of a practical exercise for me to see if I can restore them and have a way to repair in the field if something like this arises again and have a solution to avoid shipping a board back.

LOL, it will let me do everything, get device sig, blank check etc etc.  It just won't communicate via ISP.  I have two board sets, one is an ICP programmer with PLCC socket for ICP programming, and then their is the application board that is purely ISP.  So I can put the chip into the ICP tool, and program it, put it in app board, and the program via ICP runs and does what it supposed to.  Try to put in into ISP mode, flashmagic times out and say it can communicate with it. 

Someone sent me a bootloader file, I'll disable protect ISP and program it via ICP with ISP protect off and if it does what I expect, that flash should restore the ISP bootloader??

Thats the theory anyway.  Hopefully will work as I expect it too.

that's odd, because I added the source to an existing working project, and it still came up as a brick in ISP mode.  I'll try to compile the asm solo and just flash that via ICP and see if that solves the problem......thanks

is it possible?  I have four chips that are bricked in ISP.  I can communicate with it via ICP with ISP protect active.  I believe the bootloader is damaged, where do I get the hex file to restore it?  The resource page only has asm file and needs to be compiled into a working project.  I'm just looking to restore the device to factory defaults and condition.  Is this possible via ICP?

Last post on this topic was 2006, so any new info on how to fix a dead ISP chip?

Thanks

I've modified the VDD switch application a bit more and now have 3.24 volts on the VDD pin.  I thought it could be a voltage threshold issue, but still stand with the same exact issue.....this shouldn't be this difficult.....

I have 20 or so on hand, swapped several so far, always the same result......is 3.1 volts enough on VDD??

I can't find a minimum programming spec.

Hi All, I'm trying to make my own programmer board, for the LPC932A1, and use it in ICP mode.

The board is very similar to the MCB900 from keil, I make it following all the recomendations that I found on the AN's and this forum.

Up today I'm able to make all the functions in ISP mode (read, write, erase & set device configuration).

When I trying to use it as ICP (with the ISP-ICP bridge device on it) I can only use it for read, blank check, erase, read device ID & set device configuration, but I can't program the device.

Is necesary connect some other pin on the LPC932 that I'm using as bridge. Because if I use the original MCB900 board with this device I'm able to make all the functions on ISP & ICP.

If I didn´t undestand wrong, for ICP only need to connect TXD RXD to the bridge device and the five pins to the target.
The circuit for control the target VDD pin on the AN10258 doesn´t work properly, I´m using a PNP & NPN transistor arrengement that works well.

Someone can advice me?

I am having the SAME EXACT problem as you are......did you get resolution to this yet??  Same thing, dropping bits, on program but all other functions to ICP working as it should via flashmagic.......

I'm going nuts trying to figure out what is wrong, and I built it just like the mcb900.

My ISP works flawlessly, my ICP all but programming.........

Please let me know, I'd really like to the have a solution!

thanks
chris

Joe, can you take a look at my thread, I'm having trouble with ISP to ICP bridge using the push pull design.  Its dropping random bytes from what I've been told.

Just wondering if you had any insight.

thanks
Chris

I now have it setup as an ISP to ICP bridge with code version 1.7 from flashmagic.

I can read everything from flashmagic like the ICP target device sig, security bits, I can do everything.....except it won't program the hex file in. I'm using the same lpc936 so size isn't the issue, and the bridge is obviously working. If I pull the ICP device, I get all FF for device sig, put it back in, I get normal readback of data and configuration info.

I don't understand why it won't program. The app note says ensure dtr and rts is checked and to protect ISP. All of that's done.

Any ideas what I could be missing here? Its 99.4% ready, just the pesky problem of doing what its designed for.....<laughing to myself>

Thanks

I have two of the older cable from radioshack part number 26-183, but now when I search for that there is a new catalog number 26-949.

They look exactly the same in shape, but older one is white, new one is black.  Not sure if the internals are identical or not.  But the two older ones if still can be found, work fine on the LPC 924 and 936.  I also use it for my home automation system Crestron.

Hope this helps some.

Read it, makes sense.  Thanks!

Is there one?  I see people talking about it.  How do i use it?  I currently use ISP and need to move to ICP for a project, can someone give me an FAQ I can read or give me a clue on how to use/implement it?

Thanks