Its some nasty bugs in Sibabs NCP stack that have being fixed in EZSP 6.7.8.0 and the community have cocking firmware for most used modules that is being in use.
Then Elelabs dont have not released some updating for its legacy products then users is left with one product that is not working so well in there system (battery draining in some days with many sleeping end devices).
Can Elelabs providing the needed hardware configuration for the ELU012, ELR022, EZBPIS and EZBUSBA so we can requesting one updated firmware from one of our skilled firmware guru?
We is not interesting in "company secrets" that is being build in the original released software / firmware only the external hardware connections the hardware is using.
We need the RX, TX and if its gets one force boot loader pin with the associated port / pin on the chip.
Is the EZBPIS and EZBUSBA using the same hardware configuration as the Silab reference design (using the precompiled binary from Silab that was before distributed in the Silab SDK) ?
If yes we very likely is already have one working firmware but we dont like recommending our users testing it and braking there bellowed devices but if its being "standard" its shall not being any problems to using it.
Thanks in advance for supporting the community with great products and knowledge.
Its some nasty bugs in Sibabs NCP stack that have being fixed in EZSP 6.7.8.0 and the community have cocking firmware for most used modules that is being in use.
Then Elelabs dont have not released some updating for its legacy products then users is left with one product that is not working so well in there system (battery draining in some days with many sleeping end devices).
Can Elelabs providing the needed hardware configuration for the ELU012, ELR022, EZBPIS and EZBUSBA so we can requesting one updated firmware from one of our skilled firmware guru?
We is not interesting in "company secrets" that is being build in the original released software / firmware only the external hardware connections the hardware is using.
We need the RX, TX and if its gets one force boot loader pin with the associated port / pin on the chip.
Is the EZBPIS and EZBUSBA using the same hardware configuration as the Silab reference design (using the precompiled binary from Silab that was before distributed in the Silab SDK) ? If yes we very likely is already have one working firmware but we dont like recommending our users testing it and braking there bellowed devices but if its being "standard" its shall not being any problems to using it.
Thanks in advance for supporting the community with great products and knowledge.
Regards,
Mattias W