MCUXpresso Secure Provisioning error while configuring flash boot memory

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUXpresso Secure Provisioning error while configuring flash boot memory

Jump to solution
1,626 Views
piOverThree
Contributor II

Hello people. So, while using the secure provisioning software to flash a image to my EVKBIMXRT105 dev board I encountered this error in the Boot config menu:

 

 

 

Status of the operation: SUCCESS: Settings loaded successfully; workspace: `/home/user/source/imxExamples/usb_device_video_virtual_camera/bm/provisioning`
Executing script /home/user/source/imxExamples/usb_device_video_virtual_camera/bm/provisioning/ext_memory_setup.sh
ERROR: Script failed with return code: [2]ERROR
### SCRIPT: Initialize external memory: /home/user/source/imxExamples/usb_device_video_virtual_camera/bm/provisioning/ext_memory_setup.sh
/bin/bash: symbol lookup error: /bin/bash: undefined symbol: rl_trim_arg_from_keyseq

### RESULT of the script `Initialize external memory`: FAILURE (return code = [2]ERROR)
Status of the operation: FAILURE: Initialize external memory

 

 

 

Seems like there is an error related to the libreadline. Any help diagnosing this problem would be nice!

My setup:

  • OS: Archlinux, Kernel 6.10
  • librealine: readline 8.2
  • MCUXpresso Secure Provisioning: v8.0
  • Board:  EVKBIMXRT105
Labels (1)
0 Kudos
Reply
1 Solution
1,622 Views
piOverThree
Contributor II

After a little digging, I've come up with an idea, that the provisioning software is using another version of the library, probably being distributed alongside it.

So, after searching in my file system, I found a libreadline.so.8 binary under /opt/nxp/MCUX_Provi_v8/bin/_internal/. After removing it, the tool could load the system installed libreadline.so.8.2 and the ext_memory_setup.sh script worked as intended.

Seens that a litte version bump in the provisiong tool libreadline to 8.2 would resolve the problem for linux users. 

View solution in original post

0 Kudos
Reply
1 Reply
1,623 Views
piOverThree
Contributor II

After a little digging, I've come up with an idea, that the provisioning software is using another version of the library, probably being distributed alongside it.

So, after searching in my file system, I found a libreadline.so.8 binary under /opt/nxp/MCUX_Provi_v8/bin/_internal/. After removing it, the tool could load the system installed libreadline.so.8.2 and the ext_memory_setup.sh script worked as intended.

Seens that a litte version bump in the provisiong tool libreadline to 8.2 would resolve the problem for linux users. 

0 Kudos
Reply