copslock
copslock
Changing only the host code will not help anything,the modification to the NXP controller firmware is mandatory
the libusb0 in libusbk is an wrapper for libusbK
> @copslock > > Since libusb0, libusbk and libusbK are extensively overloaded terms, I unfortunately have no idea what you meant. > > Also, do you have a reference you...
I think it's a good idea to add an option for pyusb backend version force-selcetion.I had already seen **a lot** of complain caused by the libusb version selecting schema.
It's opensource software,you can help adding features to it
- UEContextReleaseCommand [NAS-cause=normal-release] protocolIEs: 2 items Item 0: id-UE-S1AP-IDs ProtocolIE-Field id: id-UE-S1AP-IDs (99) criticality: reject (0) value UE-S1AP-IDs: uE-S1AP-ID-pair (0) uE-S1AP-ID-pair mME-UE-S1AP-ID: 7 **eNB-UE-S1AP-ID: 10** Item 1: id-Cause ProtocolIE-Field id:...
I think I have found the root cause of NULL pointer in initial context attach accept now,but the S-MAC invaild problem needs more time to investigate
Beacuse of the famous IMSI 000000000000000 problem,the EPC context mangement is broken #588
@anilgurses Why UE reattach with **Service Request** faild?It shows in the EPC console log ---invalid S-MAC,this problem is even serious in early versions that can even happened in active state,I...
> Can you find an Android Linux image arm64 binary ? Or can you create a docker image for that with all the arm64 Linux and sdk tools like the...