Search results for query: *

Unfortunately, I have no scope.

As I noted, there is signal voltage on Rx pin(-3.15V) and Tx pin(0.15V): does it mean that firmware has access to that console port?

I jumper pins TX and RX on the end of serial cable and tried type in Putty, it is echoed back correctly. So this show that FTDI cable is OK. I think I already tried to swap TX and RX pins.

I need to control the boot process on an embedded device, so I connected serial console port pins to Putty client, but can't get any output from serial port. I use FTDI TTL-232R-RPi (USB to TTL RS232) cable. I've measured signals on serial console pins, there is -3.15V on RX pin and 0.15V on TX...

Because it's expensive, and will use it only occasionally, just have very limited budget. Only wanted to figire out is it possible adopt it this way or not.

There is used USB2Wiggler device for OnCE interface, it has small internal daughter board labeled COP-OnCE that adapts it to a ONCE pinout. I wanna know is it possible to adopt this USB2Wiggler hardware for ARM and MIPS JTAG interfaces. Can this hardware be configured for JTAG debugging...

As I think that hardware design is not supposed to be in-circuit programmable as it's cheap mass product. I'm not going to reprogram the chip, I only want read flash and get dump (MX29LV160ATTC-70 flash). I have no flash programmer yet.

This CLIP is not JTAG connector, its for direct in-circuit flashing. As I said there is no JTAG pins.

No, the board don't have any JTAG pins. I wanna know in particular, can the other components of the PCB (connected to chip) affect the proper flash reading. I have no schematic diagram.

Is the Universal CLIP for 48Pin TSOP1 package IC reliable enough to connect programmer to chip and read memory on device, without desoldering flash from board? Has anybody used it?