Skip to main content

Topics

This section allows you to view all Topics made by this member. Note that you can only see Topics made in areas you currently have access to.

Topics - rhyde

1
Open Bench Logic Sniffer / OLS upgrade issue [solved]
[quote author="ian"]
OLS-loader bitstream loader utility for Windows, Mac, Linux.
[/quote]
Ian I tried to do a upgrade to your experimental latest release on my mac and failed.  The instructions left me confused.  It is not a case of a bricking of a board, but I don't get how it is supposed to work.  To do a PIC upgrade it appears that I can not use ols-loader which appears to be the latest loader software.  It requires a serial interface to exist which does happen when a in bootloader mode for the pic.  The existing fw-update on my system does not work with either mechanism.  I also note the ols-loader is not in your source tree in google code, or it is but marked finished so it will not check out???

Which tools am I supposed to use this time?

I am able to compile the latest fw_update sources on Jack's site, but it fails with

PIC-firmware rich$  fw_update -e -w -m flash -vid 0x04D8 -pid 0xFC90 -ix OLSv1.firmware.v2.2.hex
U2IO flash erasing: FAILED.
Device is not found.
Operation aborted.

it also fails to print the version with a U2IO BootLoader Version reading: FAILED
Segmentation fault.

ols-loader can read the version, if I get out of PIC bootloader and into rom loading mode

PIC-firmware rich$ ols-loader -status -p:/dev/tty.usbmodem411
Logic Sniffer ROM loader v0.2 (September 10, 2010)
Opening serial port '/dev/tty.usbmodem411' @ 921600 ... OK
Found OLS HW: 1, FW: 2.1, Boot: 2
Found flash: ATMEL AT45DB021D
OLS status: 94

Clues would be appreciated.  (The board is a new one Seeed just shipped me, but the pc board claims to be version 1.01, so I guess this is a new batch of older boards, or some other part was the reason my order was delayed a bit.)
2
USB Infrared Toy / Fixing 1st batch IRtoy from Seeed
I have a first back unit, which from the discussion it appears several construction issues.  It is receiving strong signals, but I would like to get the transmit functions working properly.  Is there a complete list of the changes I need to make?  And any pictures or other aids?
3
Web platform / boot loader not working for me
I am doing something wrong, but if anyone could point out my issue I would appreciate it.  I am trying to load a new image, trying to get the sd version up and working, but the bootloader keeps tell me nothing to do.  The write program option is grayed out.  What step am I missing?  I select the device, dsPIC33FJ and the sub device field 128GP204, and the comm port which is fdti.  I load the nex file I made.  I get a complaint in the ds30loader that that Unknown data found 16 bytes at 0xf80010
then in blue The hex file contains code that will overwrite the bootloader.

Hexfile successfully pared
44032 program words found in 688 rows
0 Eeprom words found
8 config words found.
4
Bus Pirate Support / BlinkM I2C help
Having gotten lost in 1-wire land I decided to move over to I2C.  The setup is bp connected to a blinkm maxm.  The problem is the same one reported here.  With on board pullups enabled and showing ~5 volts, I either see everything or nothing.  The blinkm ignores me. :-(  I guess it is time for more external resisters

I tried moving the power to 3.3 and the pull ups shifted, but no joy.  Still poking around.
5
Bus Pirate Support / Getting BP working with SUMP
Well now I can sometimes get sump running with the OLS, was trying to figure out how to get it working with a BP.  I poked around a bit, but I am missing something.  Which versions can/should work?  How do I get the sump client to notice it exist?  Is there an fpga equivalent set of host side software I need to put in place?  If some kind soul could point out where I went wrong I would greatly appreciate it.
6
Bus Pirate Development / issues using 1-wire mode (newterm)
So I found a bit more time to work on things, and as usual I get more confused.  I connected up a couple DS18S20 therm devices.  The are in small proto board so the temps should be real close.  Unfortunately they don't appear to be.

So I do a (240) to scan the bus and I find them both
1-WIRE> (240)
SEARCH (0xF0)
Macro     1WIRE address
 1.0x28 0x60 0x54 0x02 0x02 0x00 0x00 0x1F
   *DS18B20 Prog Res Dig Therm
 2.0x28 0xC8 0x88 0x8F 0x02 0x00 0x00 0xD9
   *DS18B20 Prog Res Dig Therm
Device IDs are available by MACRO, see (0).

1-WIRE>

So far so good.  Then I tell each to convert the current temp and read back the scratch pad.
This appears to me to be the right sequence
{ 0x55 (1) 0x44 %:1000 { 0x55 (1) 0xbe r:9
or
{ 0x55 (2) 0x44 %:1000 { 0x55 (2) 0xbe r:9

But the temps I get back seem way to far apart, device (2) gives me 0x7 0xff , and device (1) gives me 0x5 0x50 that is a huge difference as I read the spec.  Can anyone point out what I am doing wrong, or where I should look?

1-WIRE> { 0x55 (2) 0x44 %:1000 { 0x55 (2) 0xbe r:9
BUS RESET OKWRITE: 0x55
ADDRESS MACRO 2: 0x28 0xC8 0x88 0x8F 0x02 0x00 0x00 0xD9

WRITE: 0x44
DELAY 232ms
BUS RESET OKWRITE: 0x55
ADDRESS MACRO 2: 0x28 0xC8 0x88 0x8F 0x02 0x00 0x00 0xD9

WRITE: 0xBE
READ: 0xFF 0x07 0x4B 0x46 0x7F 0xFF 0x01 0x10 0x2F
1-WIRE> { 0x55 (1) 0x44 %:1000 { 0x55 (1) 0xbe r:9
BUS RESET OKWRITE: 0x55
ADDRESS MACRO 1: 0x28 0x60 0x54 0x02 0x02 0x00 0x00 0x1F

WRITE: 0x44
DELAY 232ms
BUS RESET OKWRITE: 0x55
ADDRESS MACRO 1: 0x28 0x60 0x54 0x02 0x02 0x00 0x00 0x1F

WRITE: 0xBE
READ: 0x50 0x05 0x4B 0x46 0x7F 0xFF 0x0C 0x10 0x1C
1-WIRE>
7
Open Bench Logic Sniffer / Mac OS RXTX
Is anyone having any luck getting RXTX up with OLS on Macos snow leopard?  I have tried numerous version and compiles that don't work, but I am hoping someone has one that works.  All the ones I have tried segv in the kernel serial code.  Although they all segv, they do it at different times.  I have spent several hours comparing the various source modules, but no enlightenment has been coming from this path.  I was sick today so I had time to focus, but it is not cooperating.