Error in resetup():ChipconUsbTimeoutException() about rfcat HOT 8 CLOSED

File "/usr/local/bin/rfcat", line 56, in
interactive(ifo.index, DongleClass=RfCat, intro=intro)
File "/usr/local/lib/python2.7/dist-packages/rflib/init.py", line 207, in interactive
d.setModeRX() # this puts the dongle into receive mode
File "/usr/local/lib/python2.7/dist-packages/rflib/chipcon_nic.py", line 334, in setModeRX
self.setRfMode(RFST_SRX)
File "/usr/local/lib/python2.7/dist-packages/rflib/chipcon_nic.py", line 319, in setRfMode
r = self.send(APP_SYSTEM, SYS_CMD_RFMODE, "%c" % (self._rfmode) + parms)
File "/usr/local/lib/python2.7/dist-packages/rflib/chipcon_usb.py", line 705, in send
return self.recv(app, cmd, wait)
File "/usr/local/lib/python2.7/dist-packages/rflib/chipcon_usb.py", line 669, in recv
raise ChipconUsbTimeoutException
rflib.chipcon_usb.ChipconUsbTimeoutException: Timeout waiting for USB response.

from rfcat.

I found the problem.
t seems that the firmware update is broken with the new sdcc v3.8.0 compiler in Kali 2018 v2.
You got a compiler error.
Revert to sdcc 3.5.0 in Ubuntu and the problem was gone.

from rfcat.

thanks for updating this. if you have a chance, i'd be interested in what errors/problems you saw wrt SDCC v3.8, since that's going to be the norm at some point and i'd like RfCat code to be ready.

thanks!
@

from rfcat.

@atlas0fd00m: I see that this particular issue was closed, however, I think this still needs to be fixed (I saw some closed issues regarding same issue). I have tested out firmware installation with different versions of sdcc starting from 3.5.0 and noticed that firmware upgrade with latest (3.8.0) will cause this error (and device is rendered unusable) . Here are two samples of important stuff printed during installation between 3.5.0 and 3.8.0:

sdcc 3.5.0
[--- new serial number: 0000 ---]
chipcon_usb.c:681: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:765: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:1324: warning 230: label without statement
chipcon_usb.c:1302: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:1302: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
global.c:36: warning 94: comparison is always true due to limited range of data type
global.c:56: warning 126: unreachable code
global.c:57: warning 126: unreachable code
global.c:57: warning 126: unreachable code
packihx: read 617 lines, wrote 1187: OK.

sdcc 3.8.0
[--- new serial number: 0000 ---]
chipcon_usb.c:681: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:765: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:1324: warning 230: label without statement
chipcon_usb.c:1302: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
chipcon_usb.c:1302: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG
global.c:36: warning 94: comparison is always true due to limited range of data type
global.c:56: warning 126: unreachable code
global.c:57: warning 126: unreachable code
global.c:57: warning 126: unreachable code
packihx: read 618 lines, wrote 1188: OK.

As I don't have enough knowledge on how firmware data is generated, I cannot fix it. I can however, provide any information you need to get to the bottom of this.

P.S. packihx seems to read and write an extra line with sdcc 3.8.0 (might not be significant)

from rfcat.

Ran in the same issue today... I'm currently running Ubuntu 19.04 and thus installed sdcc version 3.9.0, which results in the same errors as #42. Version 3.5.0 of sdcc seems to work fine. You can get the YS1 in bootloader mode by grounding pin 7 and pin 9 (enter bootloader mode when the firmware isn't running).

from rfcat.

I am currently using version 3.5.0 but still get the rflib.chipcon_usb.ChipconUsbTimeoutException: Timeout waiting for USB response error when I run any listening command from a Python script and don't hear anything. Any ideas why this might be? I am an absolute noob so I may be missing something

from rfcat.

I too am running sdcc 3.5.0 but also getting this error constantly. Help would be very very appreciated. cheers

from rfcat.

ChipconUsbTimeoutException: Timeout waiting for USB response error when I run any listening command from a Python script and don't hear anything.

that's the normal behavior. you can adjust it, but it is necessary to avoid having to Ctrl-C while waiting for data. i never realized how confusing it may be to use the ChipconUsbTimeoutException for RF timeout. RFrecv() hands its timeout into ChipconUsb's recv() function, which throws ChipconUsbTimeoutException if it doesn't receive a message in the allotted time.

is there anything that doesn't jive with this explanation? if it's something else odd, i'd like to hear it.

from rfcat.