We have a number of Rev A GigaBlox Nanos from an old order of same. Our newer designs use the Rev B successfully, but the Rev A limitation of a maximum MTU of 1536 bytes keeps them from working in that application.
I notice the subject two signals on its interface port (also as J7 on the connector board). Is there a way to set the MTU value via those? While I doubt that, it would be a shame to discard otherwise fine boards if it can be done.
Thank you for your terrific products!
You can’t be using GigaBlox Nano Rev B; it hasn’t been released yet.
Hello!
Thank you for the note. I was misinformed about the use of the Rev B in production. With its availability being only weeks away, is there any news about possible MTU value updates?
Thank you again, and my apologies for the confusion!
Sadly, no rev, B won’t bring the MTU size up to jumbo capability. We are adding the footprint for an EEPROM on rev B, to allow the jumbo firmware to be uploaded later, but so far we’ve had a lot of issues getting that to work without messing up other aspects of the switches behaviour.
And sadly the I2C pins can’t be used to dynamically program the chip, it doesn’t support that unfortunately.
I know this is an important one as you guys keep asking for it, sadly it’s not an easy one to hit so I don’t have a timeline on when we expect to implement it.
Hello,
Thank you again for your note. Fortunately for our designs, your other switches make it possible to bring our designs to production. And the Nano can still serve us well when we use it where it will work.
Having done embedded designs within the constraints of the parts involved, I understand your situation and commend you for what you have accomplished!
Best to the botblox team from ours
Thanks Jim. We love working with you folks too. Just so you know, our dev team is expanding, so we will have more resource to look at small (yet impactful) improvements like this in future.