I am attempting to monitor the data that is being sent from an embedded linux device to a peripheral piece of equipment in a system.
Please see attached diagram I have made depicting the normal system connection and how I am thinking I can monitor the data using the bus pirate.
[attachment=0] My question is whether or not this would be a valid method for monitoring this data communication. I am only interested on what the peripheral device is receiving from the linux device. Assuming this physical monitoring setup is correct, am I correct to think that the UART live monitor macro should allow me to capture this traffic?
I am attempting to monitor the data that is being sent from an embedded linux device to a peripheral piece of equipment in a system.
Please see attached diagram I have made depicting the normal system connection and how I am thinking I can monitor the data using the bus pirate.
[attachment=0] My question is whether or not this would be a valid method for monitoring this data communication. I am only interested on what the peripheral device is receiving from the linux device. Assuming this physical monitoring setup is correct, am I correct to think that the UART live monitor macro should allow me to capture this traffic?
Hello everyone,, i'm a newby with pic and atmel based hardware and just started playing with the teensy 2.0 and a bunch of part from 4D system and sparkfun... however, i have a lot of experience with programming of embeed device (mostly sigma, motorola SoC based tv stb)... So please feel free to correct me in any of the assumption i'm going to make regarding the hardware interface are wrong, i want to learn that stuff.
Inspired by the computer-less adruino project (which is awesome btw!) i am building a computer-less serial console that i would like to use with the BP... I am trying to use the uLCD-32PT from 4D System as a serial console display for the serial text output and a blackberry keyboard connected directly to the uLCD-32PT GPIO (still have to figure out the keyboard part, will probably code an onscreen kb for now).
I would like to connect the serial ttl port of the inteligent lcd display module to the BP v3 in this configuration; host: uLCD-32PT slave: BP v3
I was wondering why the tap between the pic and ftdi chip had been removed in v3? i believe this is where i need to connect the ttl interface of the host. (only have BP v3 in hand for now)
ftdi chip documentation show that by default it is configured for rs232 application, if i follow the pin used on the BP v3, this seem to be accurate.
uLCD documentation show -Easy 5 pin interface to any host device: VCC, TX, RX, GND, RESET. -Asynchronous hardware serial port, TTL interface, with 300 baud to 256K baud.
Am I missing anything? i believe i just have to tap the tx, rx pin of the ftdi chip and plug straight into the uLCD serial ttl?? or do i need a max232 chip in between?
Any help will be appreciated, also, are you planning to make a portable device like the dso nano oscilloscope but for logic and protocol analyzer? i would be happy to help with the coding or share my serial console display library
Hello everyone,, I tried upgrading my BP v3a to the latest firmware (v6) and it is somehow bricked. The BP had never been upgraded before so the bootloader had to be upgraded. These are the steps I followed.
- downloaded firmware pack V6 - downloaded v2 to v4 bootloader upgrader - put a jumper on ICSP header - started BP - mode led went on - started P24QP.exe - connection to BP at 115200 ok - erased the chip - wrote the firmware file BPv3-v2blupdaterVa3-v4.1.hex - clicked on Normal Exec Mode - removed the jumper - turned BP on - connected to it with Putty - typed yes - saw the success message - put the jumper back - started DS30 loader - connection to BP ok - loaded file BPv3-frimware-v6.hex - pressed download
DS30 showed "looking for bootloader" for a few seconds, then "failed"...
Since then, I have no connection to the BP, either from terminal (putty), bootloader upgrader or DS 30, at any speed. When I put the jumper, the mode led is on. USB COM port is ok (from windows manager).
I have no idea what could have gone wrong. I don't have much equipment for testing. I have a AVRISP, but no PIC programmer. I work on a Windows 7 system.
