Page 1 of 1

List of Error Messages

Posted: Wed Oct 19, 2016 12:55 pm
by SpaceJelly
Hi there,

Is there a list of error messages in the software as we're getting QERR:W30 when trying to write to an SFP+

Thanks!

Re: List of Error Messages

Posted: Tue Oct 25, 2016 11:40 am
by sfptotal
Hello,

When programmer can't complete operation on the I2C bus, it returns a symbol code of operation, in which process appeared error, and HEX code of error. The MCU generate interrupt and return to software the code of problem. Here most popular codes and reasons of situation:

ERR:WXX or ERR:RXX
Symbol W or R says that problem appeared in progress of Write or Read operation.

Codes of errors

x00 Bus Fail
Critical error of bus line.

x20 - SLA+W+NACK -Programmer sent address byte with write bit and got NACK. Slave didn't answer.

x30 Byte+NACK - Programmer sent the data byte and didn't get a confirmation transfer by Slave.

x38 Collision - Another Master activity on the bus line.

x48 SLA+R+NACK - Programmer sent address byte with read bit and got NACK. Slave didn't answer.

Re: List of Error Messages

Posted: Tue Jan 16, 2018 4:35 am
by ksoufan
I am trying to write on Fiberstore OEM SFP+ and getting error PM > QERR:W20. is there a way to make it work??

Re: List of Error Messages

Posted: Tue Jan 23, 2018 8:23 am
by sfptotal
Try to set BPS=80 using command line (under log area) or I2CPAUSE=98

Re: List of Error Messages

Posted: Wed Mar 07, 2018 8:47 am
by Jaarek
Hi,

I am trying to read and write, but in some cases (other OEM manufacturer) I getting error QERR:SDA or QERR:SCL

With another type of programming board, these transceivers are programmed. What's the problem with?

Thanks.

9:41:28 > Read Table A0 add. 00, 128 byte(s) from 00
9:41:28 > R1A000007F
9:41:28 > QERR:SDA

9:14:48 > Write Table A0 add. 00, 128 byte(s) from 00
9:14:48 > W1A000007F030407800000000000000003670050FF000000004F454D20202020202020202020202020000090655346502B20313047204357444D20202020202020060E00D8061A0000444531353038303330303120202020203135303830332020689001750000000000000000000000000000000000000000000000000000000000000000
9:14:48 > QERR:SCL

9:35:47 > Write Table A0 add. 00, 128 byte(s) from 00
9:35:47 > W2A000007F03040700000000120001540155030A640000000044454C4C2020202020202020202020200000906546544C46313432385032424E562D464341202020051E00AF003A0000434C38474C5220202020202020202020313030323036202068FA03F40000000000000000000000000000000000000000000000000000000000000000
9:35:47 > QERR:SDA

Re: List of Error Messages

Posted: Tue Mar 27, 2018 8:06 pm
by sfptotal
These error appear because signal lines of I2C databus keep by transceiver side in low level. In this case a programmer (master) can not start data transfer because do not arise interruption events which should be handled for data transfer between a programming board and a transceiver (slave).

This situation can looks like return of errors QERR: I2C_BUSY, SDA or SCL. Or as a long freeze of command line interface on previous versions of SW.

As a rule, transceivers should not have an effect on databus lines when are connected.

We made an experiment with 15 SFP+ transceivers from different manufacturers to check they behaviour. We really trust in quality and use these modules for testing programming boards before sellings.
Normally transceivers keep I2C databus lines in high level, the databus is free for data transfer.

We got results with good reading of this group.

We repeated this experimen with removing jumpers on power supply plans to reproduce any possible electrical problems when transceivers is plugged on without power supply.

All transceivers from our group did not have an effect on databus. We got errors QERR:R20 which say that a slave device did not answer on address byte. That is normal.

We can not confirm that problem is linked with hardware of SFPTotal programmers. The reason could be in low quality of optical transceivers.

We would be very appreciated if you provide photos of transceivers called these errors.

For now we recommend plug-in these transceivers to programmer port before connection a programming board to PC to stabilize power supply of transceiver.