HP firmware in the SFP module, so it could not be changed to Cisco or other compatible??

[palashgoyal]

Hi,

I am struggling with recoding a HP coded optic to Cisco optic. the module I have is J9150D-PO, it is with the HP firmware in the module, so it could not be changed to Cisco or other compatible ??
Are HP transceivers are special than others ?

I am attaching both hp and cisco code Please let me know if anyone has faced the similar issue and came to a solution. it will be very helpful and thanks in advance

Best ,
Palash Goyal
pgoyal [] pivotaloptics.com

[thankfly]

HP SFP+ SR is MORE special than Cisco.
HP SFP+ SR need HPidV2, that means something should wrote in MCUs.
Cisco only need to write SPECIAL hex contents in the EEPROM.
In a word: HP SFP+ SR can change to Cisco with wrote a special content.
Cisco SFP+ SR cannot change to HP SFP+ with wrote a special content.

[palashgoyal]

Thanks for your response, I was able to recode the the optic using password but still it does not work as it should be. I am sure now since you mentioned already, its definitely firmware on HP optics which makes it different then other platforms. If we need to change it we need to have the right firmware as well with the HP code. If anyone has or had similar issue and came to a conclusion please share your experience. It will be a great help. Thanks

[thankfly]

BTW: I dont think you can write the firmware to the modules.
The manufucture does not reserve the interface to communicate with MCUs.
All you can write in is EEPROM.
And, there is only a few guys have the firmware with HP.

[palashgoyal]

Hi, just catching up.
Is there a way we can write the MCU using Beagle I2C/SPI Protocol Analyzer??
Please advise, Thanks

[thankfly]

Hi, just catching up.
Is there a way we can write the MCU using Beagle I2C/SPI Protocol Analyzer??
Please advise, Thanks

There is no sense to write MCU, because you don't have HP firmware.

[ArT]

There are many differents MCUs in SFPs and they are all read protected, it can not be changed. All of them are simulating EEPROM in MSA standard and you can change areas in MSA standard. Memory map details are descibed in this post: https://forum.reveltronics.com/viewtopic.php?f=32&t=529

[dstachur]

This is a quite old topic, but it is related to HP SFPs, so I decided to refresh it and write about my HP related issue here...

A general goal is to clone HP J9151A SFP.
First of all I bought an original HP to get it's content and check what hardware is under J9151A SFP:

Clipboard01.jpg (53.76 KiB) Viewed 83743 times

As you can see it is Source Photonics hardware, so I bought a bunch of these hoping these are MSA standard with well known write password or in worst case scenario I will be able to brute force it. This is an untouched Source Photonics:

Clipboard02.jpg (54.76 KiB) Viewed 83743 times

HP J9151A is a bit different SFP model - SPP-10E-LR-CDFF (10km range) instead of my "clean" SPP-10E-LR-CDFP (2km range).
I have a 3rd party clone of J9151E, which content looks exactly as HP/Source Photonics, but hardware looks quite different:

Clipboard03.jpg (53.81 KiB) Viewed 83743 times

Clipboard04.jpg (41.61 KiB) Viewed 83743 times

Then I spent more than 2 weeks trying to brute force Source Photonics SFP (ASCII letters, number and special chars, A2h,7Bh). Unfortunately with no success.

So, I am looking for anyone with any experience for Source Photonics SFPs or any other hint. If you wanna try some tricks on your own, I can probably send you 1 or 2 Source Photonics SFP, I got a lot of these.

I am also wonder how 3rp party SFPs with HP's original content was prepared. I got an non OEM, regular Finisar LR FTLX1471D3BCL and tried to use it for cloning. I can write to this one (standard password), but HP switch did not accept my cloned SFP :-/

[thankfly]

This is a quite old topic, but it is related to HP SFPs, so I decided to refresh it and write about my HP related issue here...

A general goal is to clone HP J9151A SFP.
First of all I bought an original HP to get it's content and check what hardware is under J9151A SFP:

Clipboard01.jpg

As you can see it is Source Photonics hardware, so I bought a bunch of these hoping these are MSA standard with well known write password or in worst case scenario I will be able to brute force it. This is an untouched Source Photonics:

Clipboard02.jpg

HP J9151A is a bit different SFP model - SPP-10E-LR-CDFF (10km range) instead of my "clean" SPP-10E-LR-CDFP (2km range).
I have a 3rd party clone of J9151E, which content looks exactly as HP/Source Photonics, but hardware looks quite different:

Clipboard03.jpg

Clipboard04.jpg

Then I spent more than 2 weeks trying to brute force Source Photonics SFP (ASCII letters, number and special chars, A2h,7Bh). Unfortunately with no success.

So, I am looking for anyone with any experience for Source Photonics SFPs or any other hint. If you wanna try some tricks on your own, I can probably send you 1 or 2 Source Photonics SFP, I got a lot of these.

I am also wonder how 3rp party SFPs with HP's original content was prepared. I got an non OEM, regular Finisar LR FTLX1471D3BCL and tried to use it for cloning. I can write to this one (standard password), but HP switch did not accept my cloned SFP :-/

As I said below: A module wants to compatibal with HP, you need to write a special firmware into MCU. There is no sense to copy an eerpom from orginal module to a 3rd-pary module, even this module is the same brand.
Hope helpful.

[dstachur]

A module wants to compatibal with HP, you need to write a special firmware into MCU.

So why it works fine when you read an original HP SFP and then write this it's code into 3rd party, but does not work when you write it to exactly the same hardware?
By the way I do a lot of SFPs for Extreme Networks 10G on Finisar FTLX8571BCL (I found Extreme Networks uses FTLX8571BCL), I also did a few succesful writes on HP 40G QSFPs on Finisar FTL410QE4C. And these all works fine clonned that way.

There is no sense to copy an eerpom from orginal module to a 3rd-pary module, even this module is the same brand.

I don't understand your point - all the 3rd party's SFPs has the eeprom content from original HP. And that works, right?
Do you mean some different MCU code (not generic, but HP specific) + HP eeprom code?