How to run shell script after boot

#9

Please see attached console log.
Teraterm.log: Run customer application and wakeup_app
Teraterm2.log: Run only wakeup_app
Procedure

  1. Add wakeup_app and customer application
  2. send “update –g” command
  3. Power OFF → ON at 5 times
    Please see last line. It is described as “’wakeup_app’ is not installed”.
    Note: Yes, customer is checking this issue using mangOH green board.
    teraterm.log (108.1 KB)
    teraterm2.log (101.9 KB)
#10

Why does the module keep resetting?
If it reboots too much, it will regard as unstable environment and rollback to previous image.


Open I2C Bus at, '/dev/i2c/4'
Try open I2C Bus at, '/dev/i2c-4'
Open I2C Bus at, '/dev/i2c/4'
Try open I2C Bus at, '/dev/i2c-4'
	Register Addr 0x11: 0x1b...

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00094
#11

Thanks. To check it, customer added the following power off code.
system("/sbin/poweroff -f");

But Customer think that WP76xx module do not go to power off sequence.
When customer send “/sbin/poweroff –f” command in linux console, WP76xx module go to power off sequence.
Is there any limitation to perform “system("/sbin/poweroff -f");” command in application?

#12

how about send AT!POWERDOWN to /dev/ttyAT channel

#13

To send AT command, I tried to open /dev/ttyAT channel but I cannot open it from application.
Of course, I succeeded to send AT command from consol window for WP76xx module using microcosm application.

Please advise how to send AT command in application.

#14

you can see this document on how to send AT command in unsandboxed legato application:

Sending AT command in Legato application.docx (215.2 KB)

#15

Thanks.

Customer did not see application deleting issue after adding power down sequence.

But there is possibility that end user will cut power supply in their system without power down sequence. If module delete their application, it is impact for their system.

After deleting their application, SWI default application is still keeping in WP76 module. Can customer set their application as default application?

#16

you can see here on modifying the wifi.sdef to add your application as default application in legato.cwe:

#17

This meaning is that customer need to build “Build your custom Device Image” in https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-13,-d-,1-components/?

#18

Yes, you are correct

#19

Customer tried to build their application based on “Build your custom Device Image”. But Customer do not understand which timing / how to implement their application.
If possible, please let us know how to implement “Hello World” as default application?

#20

Can they build the legato.cwe?
Have they modified wifi.sdef?

#21

Customer and I do not know how to make kConfig file. I checked kconfig options (Legato KConfig Options - Legato Docs) but I cannot explain it to customer because I am not the expert for Linux.

#22

You don’t need to make kconfig file

#23

What timing and how should customer add their application to cwe file?

#24

Customer is using leaf tool and build their application by .adef file.
To create their application as default application, customer need to create sdef or other to kernel. I need to explain these procedure to customer but I am not the expert for Linux. Could you please prepare sample procedure for Hello world or anything?

#25

What do you mean by timing

#26

This is how you make legato.cwe

Leaf shell
Go to the corresponding legato framweork folder
make clean
make wp76xx

#27

Customer cannot succeed to create any file with their application as default application.

Maybe, I think that we cannot work it because we did not understand final goal.

Please advise the following question.

Q1. WP76xx module is configured as follows. Is my understand correct?

Modem Firmware: modemFW.spk

Linux Distribution: boot-yocto.cwe

Base Legato System: legatoz.cwe

Customer application: custom-firmware.spk

Q2. To add custom application as default application, should customer create .spk file. Is my understanding correct?

If not, please let us know which file should customer add their application.

Q3. Customer sent “make wp76xx”. But there is not selection menu for their application and created spk file. How do customer add their application in this process?

#28

First of all, can they build the legato.cwe ?

Q1:
There is no such thing:
Customer application: custom-firmware.spk

If you want to build your application as default application, you need to build to legato.cwe

Q2: No, there is no such thing called “custom-firmware.spk”
As said before, you need to first successfully build the legato.cwe, and then add your application to wifi.sdef as default application.

Q3: “make wp76xx” is to build the legato.cwe in “build” folder, not generating the spk file.