Page 1 of 1

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

Posted: Thu Dec 02, 2021 6:52 am
by 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

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

Posted: Mon Dec 06, 2021 2:27 am
by 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.

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

Posted: Mon Dec 06, 2021 5:08 am
by 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

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

Posted: Mon Dec 06, 2021 8:36 am
by 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.

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

Posted: Thu Feb 03, 2022 9:44 pm
by palashgoyal
Hi, just catching up.
Is there a way we can write the MCU using Beagle I2C/SPI Protocol Analyzer??
Please advise, Thanks

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

Posted: Sat Feb 05, 2022 2:51 am
by thankfly
palashgoyal wrote: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.

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

Posted: Mon Feb 07, 2022 7:58 am
by 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: viewtopic.php?f=32&t=529