• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 314 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM64: How to handle features limitation of Processor SDK Linux for AM64X?

Tim Cruise
Intellectual 988 points

Part Number: SK-AM64

Dear TI Engineers,

I am developing my Wi-SUN border router on a AM64x Starter Kit Board

www.ti.com/.../SK-AM64

I have installed the default image of Processor SDK AM64x + Wi-SUN stack on it.  The out of box demos work well as described.

Then, I download a MQTT Client bash script and run it from within AM64x Starter Kit Board console.  It seems that the default installation of processor SDK image lacks some features.  These are the warning shown in the console:

warning:	setlocale:	LC_COLLATE:	cannot	change	locale	(en_US.UTF-8):	No such file or directory
warning:	setlocale:	LC_CTYPE:	cannot	change	locale	(en_US.UTF-8):	No such file or directory
warning:	setlocale:	LC_MESSAGES:	cannot	change	locale	(en_US.UTF-8):	No such file or directory
warning:	setlocale:	LC_NUMERIC:	cannot	change	locale	(en_US.UTF-8):	No such file or directory
warning:	setlocale:	LC_TIME:	cannot	change	locale	(en_US.UTF-8):	No such file or directory

INFO:	Could not determine package manager for your system, located binaries may be incorrect

INFO:	Dependency	'sed'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'ls'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'sleep'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'rm'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'cat'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'base64'	for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'tr'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'awk'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'kill'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'grep'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'head'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'mv'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'ln'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'mkdir'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)
INFO:	Dependency	'rmdir'		for	packageManager	'Unknown'	not	in	any	known	.path	file	(or	internally)

Those executables should be standard in Linux.

Now, my questions are:

  1. How do I add the locale en_US.UTF-8 to the AM64 OS?
  2. How do I inform the scripts about those executables' locations?
  3. How do I add standard Linux software, for example Nano Editor, to AM64 OS?