Custom AT Command - Circumventing the 128 byte limit?
Posted: Wed Jan 22, 2020 11:12 amHi,
I am updating an older version of our custom firmware (SDK 1.4.0 with the older open source AT parser (0.92) with SDK v2.1.0 of the NONOS (AT).
I have noticed with the older AT parser, the "at_cmdLenMax " parameter was increased from 128 to 1024, hence the older version of our custom version was able to accept a longish custom AT command (specifically an AT command with a long argument).
However, the newer SDKs have a locked down AT parser, so I cannot access that LenMax parameter. Is there any way I can override that functionality to allow me to pass in a longer argument into the custom AT command?
I assume using a HEX editor to edit the libat.a file directly to change that parameter isnt a runner...
I am updating an older version of our custom firmware (SDK 1.4.0 with the older open source AT parser (0.92) with SDK v2.1.0 of the NONOS (AT).
I have noticed with the older AT parser, the "at_cmdLenMax " parameter was increased from 128 to 1024, hence the older version of our custom version was able to accept a longish custom AT command (specifically an AT command with a long argument).
However, the newer SDKs have a locked down AT parser, so I cannot access that LenMax parameter. Is there any way I can override that functionality to allow me to pass in a longer argument into the custom AT command?
I assume using a HEX editor to edit the libat.a file directly to change that parameter isnt a runner...