[Solved] Build red_WP76xx fails

#4

Thanks, but did you mean comment these lines?

They are not commented and the build fails. If I comment the lines out the build finishes, but location is probably the most important part for me so that wouldn’t work for me.

Regards

0 Likes

#5

Yes you need to coment the line sorry…

Sorry I not use the locationService app. You need to see with the mangoh developper to fix this issue. It seems a component missing on the repo.

0 Likes

#6

we have updated the sdef and this shouldnt be a problem anymore.
anyways, thanks @Francis.duhaut

0 Likes

#7

OK, thanks. I can confirm that the make completes without error now. After building the distro I use the update command which finishes with “SUCCESS Done”

But that’s where the good news ends :frowning:

Following the next steps in the Getting Started guide I run the command:

~/mangOH$ update ~/mangOH/build/update_files/red/mangOH.wp76xx.update 192.168.2.2

The update causes the Red to reboot and when it finally comes back I can SSH to it at 192.168.2.2 but the app status command doesn’t include redSensorToCloud

So according to the docs it looks like the update failed. But if I now try running “app info” I get the output at the bottom of this post. I notice 2 things now:

  1. The legato version is very recent
  2. Some of the apps don’t have any version info

So I have no idea if the update worked correctly???

root@swi-mdm9x28-wp:~# app info
atAirVantage
status: running
running processes:
atAirVantage[928] (928)
app.name: atAirVantage
app.md5: c7ab641a63159d6958149236b1c8bfd7
app.version:
legato.version: 18.10.3

atQmiLinker
status: running
running processes:
atQmiLinker[937] (937, 1106, 1108, 1190, 1251, 1252)
app.name: atQmiLinker
app.md5: 21a0b2404307e8fbf3022e3404191983
app.version:
legato.version: 18.10.3

atService
status: running
running processes:
atClientDaemon[946] (946)
atServerDaemon[947] (947)
app.name: atService
app.md5: d8171cac090280b6453eb78ea0c48609
app.version:
legato.version: 18.10.3

audioService
status: running
running processes:
audioDaemon[956] (956, 1101, 1102, 1103, 1176, 1200)
app.name: audioService
app.md5: 5474ea4d3fe4dace6940fc9eeb271942
app.version:
legato.version: 18.10.3

avcService
status: running
running processes:
avcDaemon[966] (966)
app.name: avcService
app.md5: c74616fc87106738419e848ce70a956b
app.version:
legato.version: 18.10.3

cellNetService
status: running
running processes:
cellNetService[975] (975)
app.name: cellNetService
app.md5: 24dcb5ef994c92d34d5719bef6370da4
app.version:
legato.version: 18.10.3

dataConnectionService
status: running
running processes:
dcsDaemon[984] (984)
app.name: dataConnectionService
app.md5: 1e84d480c8ff3f87cfea68321adfeb1e
app.version:
legato.version: 18.10.3

fwupdateService
status: running
running processes:
fwupdateDaemon[993] (993, 1111, 1112, 1201, 1202)
app.name: fwupdateService
app.md5: a1e1e8714ed336b477977f88628edb59
app.version:
legato.version: 18.10.3

gpioService
status: running
running processes:
gpioService[1003] (1003)
app.name: gpioService
app.md5: 1fbc134f517a869ff44b21cb08802d3d
app.version:
legato.version: 18.10.3

modemService
status: running
running processes:
rSimDaemon[1013] (1013)
modemDaemon[1012] (1012, 1118, 1119, 1179, 1203, 1204, 1205, 1209, 1211, 1248, 1267, 1271, 1274, 1275, 1277, 1279, 1281, 1283, 1285)
app.name: modemService
app.md5: 818e975eb43092dd7fc1bb13a35a012b
app.version:
legato.version: 18.10.3

portService
status: running
running processes:
portDaemon[1022] (1022)
app.name: portService
app.md5: dab1b66d64b96b9663717e9830e3fc66
app.version:
legato.version: 18.10.3

positioningService
status: running
running processes:
posDaemon[1031] (1031, 1163, 1164, 1238, 1239, 1240)
app.name: positioningService
app.md5: c3115248c80fb17d33b7266fb32c1222
app.version:
legato.version: 18.10.3

powerMgr
status: running
running processes:
powerManagerService[1040] (1040)
app.name: powerMgr
app.md5: 817706913a543f0faae3efb21b6eb5e0
app.version:
legato.version: 18.10.3

qmiAirVantage
status: running
running processes:
qmiAirVantage[1049] (1049, 1365, 1367, 1369, 1371)
app.name: qmiAirVantage
app.md5: f8c4892220f1c09083e0b325e8a3c0d3
app.version:
legato.version: 18.10.3

secStore
status: running
running processes:
secStore[1059] (1059, 1128, 1130, 1139)
app.name: secStore
app.md5: e56a3b079f11879524feb8215fd59eb1
app.version:
legato.version: 18.10.3

smsInboxService
status: stopped
app.name: smsInboxService
app.md5: e517a83ae13cb27bb2c4d1cf69ae8bcc
app.version:
legato.version: 18.10.3

spiService
status: stopped
app.name: spiService
app.md5: 895090cf054200b44a3a6a61484fa8ae
app.version: 0.1.0
legato.version: 18.10.3

tools
status: stopped
app.name: tools
app.md5: fddace15fcd7eae43fb6b81182b4013d
app.version:
legato.version: 18.10.3

voiceCallService
status: stopped
app.name: voiceCallService
app.md5: b6245200b14d3c6f7920802f436153c7
app.version:
legato.version: 18.10.3

wifi
status: stopped
app.name: wifi
app.md5: f12e3302d0f6af3df5e65998ec879419
app.version: 18.10.0
legato.version: 18.10.3

wifiApTest
status: stopped
app.name: wifiApTest
app.md5: ee113867ac3ef7db399784483f74ff1b
app.version: 18.10.0
legato.version: 18.10.3

wifiClientTest
status: stopped
app.name: wifiClientTest
app.md5: ee6b2a27e840139a342e41a52d3f5a26
app.version: 18.10.0
legato.version: 18.10.3

wifiService
status: running
running processes:
wifiService[1069] (1069)
app.name: wifiService
app.md5: 290c1db653b416f37ef6746eb2462c30
app.version: 18.10.0
legato.version: 18.10.3

wifiWebAp
status: stopped
app.name: wifiWebAp
app.md5: a67621da1bd5da2195cae43276ee8673
app.version:
legato.version: 18.10.3

0 Likes

#8

Hey, I’m having this exact series of problems.

If you don’t mind, I’m going to start a new thread here about the second problem, since we’ve both gotten past the one described in the title of this one…

I’ve posted on the SierraWireless forum (WP7601 update fails - no redSensorToCloud), but this forum is probably the better choice.

-Nick

P.S. New topic here: WP7601 update fails - no redSensorToCloud

0 Likes

#9

Hello what is the firmware used with the WP76?

Don’t forget to use the same toolchain used to build the firmware.

I have moved to firmware R12 and legato 19.01.0 on WP7607/WP7603. I have installed the new toolchain and update the sim link to build the Mangoh update build. I not see any issue…

The VM use actually toolchain for firmware R9 in case of WP76xx. Use this firmware if you don’t want to update the toolchain.

Francis

0 Likes

#10

I’m trying to step through this guide where there is a big, shouty warning

Important: You MUST do the following step! The mangOH Distribution that you are going to install in this procedure requires you to have the correct (latest) firmware installed on your CF3 module. The distribution applications may not install or work correctly if you do not have the correct firmware.

I downloaded & ran the 1-click R12 firmware update. The output of a cm info is thus

Firmware Version: SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
Bootloader Version: SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05

…I was hoping to see a “R12” in there so I’m not even sure if that worked!! I’m assuming by the file date it is the latest.

I don’t understand what you mean by “toolchain”, do you mean Legato? I thought the whole point of this process was to make everything the latest version.

In summary - as a virgin user all I am doing is trying to get the board to a working state by going through the “getting started” guides, and everything seems to be broken. I’m not the only one experiencing this by the looks of it.

0 Likes

#11

This a little bit more complex.
For each firmware You can find the toolchain used to build.
You must use this toolchain to build the mangoh update file (include legato).

The latest VM is base on the R9 firmware for the WP76xx module.

If you want to use it without update the toolchain you need to download and flash the R9 firmware in your module. Otherwise the system will crash and roll back to original firmware without the mangoh update apps ( redSendorToCloud etc…).

If you want to use the latest firmware R12 you can install the R12 toolchain and update the sym link in the VM (have a look to readme file on the home folder).

0 Likes

#12

Sorry I’ve been away for a couple of days and haven’t had chance to look.

So OK, I downloaded and flashed R9 firmware back on to the module. Then followed the steps in the getting started guide again. It still crashes.

I don’t get the firmware thing though. Part of the getting started process involves a git pull, so doesn’t this get the latest code which should then need the latest firmware?

I took a VM snapshot when I first installed it. Just for fun I restored the snapshot and run make with the code which was included in the VM i.e. didn’t do the git pull. Same crash :frowning:

I was initially quite pleased when I first saw that the development was done in VM because it 100% guarantees the build environment so I was expecting things to work pretty much out of the box. But all I have working so far is the power LED…

cm info output

Device: WP7607
IMEI: 359779080103373
IMEISV: 4
FSN: VN811485590410
Firmware Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
Bootloader Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
MCU Version: 002.009
PRI Part Number (PN): 9907327
PRI Revision: 001.003
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.032_000
SKU: 1103511
Last Reset Cause: Reset, User Requested
Resets Count: Expected: 47 Unexpected: 1

logread output (end of file with error messages)

Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module cp2130.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module led.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module ltc294x.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module mangoh_red.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module mt7697q.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module mt7697serial.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ModuleGetParams() 524 | Module spisvc.ko uses no parameters.
Jan 6 00:12:56 swi-mdm9x28 user.info Legato: INFO | supervisor[2468]/supervisor T=main | kernelModules.c ExecuteCommand() 211 | Execute ‘/sbin/insmod /legato/systems/current/modules/bmi160.ko’
Jan 6 00:12:56 swi-mdm9x28 user.alert kernel: [ 521.027399] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Jan 6 00:12:56 swi-mdm9x28 user.alert kernel: [ 521.034646] pgd = cca98000
Jan 6 00:12:57 swi-mdm9x28 user.alert kernel: [ 521.037148] [0000000c] *pgd=8ca6c835, *pte=00000000, *ppte=00000000
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.043406] Internal error: Oops: 17 [#1] PREEMPT ARM
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.048432] Modules linked in: bmi160(O+)
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.052429] CPU: 0 PID: 2486 Comm: insmod Tainted: G O 3.18.44 #2
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.059547] task: cb090000 ti: ccb0a000 task.ti: ccb0a000
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.064931] PC is at load_module+0x1854/0x1cfc
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.069358] LR is at __mutex_lock_slowpath+0x254/0x2e0
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.074476] pc : [] lr : [] psr: a00f0013
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.074476] sp : ccb0be90 ip : 00000000 fp : 00000000
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.085932] r10: ccad7ca8 r9 : bf000e08 r8 : c07ee42c
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.091142] r7 : fffffff8 r6 : ccb0a000 r5 : ccb0bf54 r4 : bf000dc0
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.097650] r3 : 00000000 r2 : bf000f18 r1 : 00000000 r0 : 00000000
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.104167] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.111282] Control: 10c53c7d Table: 8ca98059 DAC: 00000051
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.117011] Process insmod (pid: 2486, stack limit = 0xccb0a208)
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.123000] Stack: (0xccb0be90 to 0xccb0c000)
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.127340] be80: bf000dcc 00007fff 00000000 c0076058
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.135502] bea0: bf000dcc 00000000 c07ee408 00000067 d2c95f88 00000067 bf000f18 000c6008
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.143665] bec0: d2c79000 0001cfd8 bf0006d0 00000001 bf0006d8 00000002 00000000 00000000
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.151821] bee0: 6e72656b 00006c65 00000000 00000000 00000000 00000000 00000000 00000000
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.159983] bf00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 eb4c6af0
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.168139] bf20: 00000000 000c6058 000c6008 00000051 00000080 c000e8a4 ccb0a000 00000000
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.176302] bf40: 00000000 c0078994 cc828f00 c00fa4c4 ccb0a000 d2c79000 0001cfd8 d2c959e8
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.184458] bf60: d2c95878 d2c8f19c 00000f10 00001230 00000000 00000000 00000000 00000b14
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.192621] bf80: 00000024 00000025 00000010 00000000 0000000a 00000000 0001cfd8 beee0e70
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.200778] bfa0: 000001c3 c000e6e0 0001cfd8 beee0e70 000c6058 0001cfd8 000c6008 000b476c
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.208941] bfc0: 0001cfd8 beee0e70 000001c3 00000080 beee0e70 00000002 000b4794 00000000
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.217098] bfe0: beee0ba8 beee0b98 00024698 4ff8cda0 200f0010 000c6058 00000000 00000000
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.225274] [] (load_module) from [] (SyS_init_module+0x120/0x12c)
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.233163] [] (SyS_init_module) from [] (ret_fast_syscall+0x0/0x44)
Jan 6 00:12:57 swi-mdm9x28 user.emerg kernel: [ 521.241236] Code: e5933000 e1520003 0a000128 ebfea02e (e5973014)
Jan 6 00:12:57 swi-mdm9x28 user.crit Legato: CRT | supervisor[2468]/supervisor T=main | kernelModules.c ExecuteCommand() 243 | /sbin/insmod was killed by a signal 11.
Jan 6 00:12:57 swi-mdm9x28 user.err Legato: =ERR= | supervisor[2468]/supervisor T=main | kernelModules.c installModules() 1074 | Error in installing module bmi160.ko. Restarting system …
Jan 6 00:12:57 swi-mdm9x28 user.emerg Legato: EMR | supervisor[2468]/supervisor T=main | supervisor.c framework_Reboot() 696 | Supervisor going down to trigger reboot.
Jan 6 00:12:57 swi-mdm9x28 user.warn kernel: [ 521.262738] —[ end trace abbb12b69ad98975 ]—
Jan 6 00:12:58 swi-mdm9x28 user.emerg Legato: EMR | UNKNOWN[648]/framework T=main | LE_FILENAME RunCurrentSystem() 1484 | System will reboot now !
Jan 6 00:12:58 swi-mdm9x28 daemon.info init: starting pid 2501, tty ‘’: ‘/etc/init.d/rcK’
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: subsystem_control_shutdown
Jan 6 00:12:58 swi-mdm9x28 user.err qmi_shutdown_modem: QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-6
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: Initialize QMI DMS Client
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: Current Modem status - 0
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: Move modem status to LPM
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: Wait for modem LPM complete
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: DMS indication id - 1
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: Modem in LPM state… proceed with rest of shutdown procedure
Jan 6 00:12:58 swi-mdm9x28 user.info qmi_shutdown_modem: In the shutdown path
Jan 6 00:12:58 swi-mdm9x28 user.warn kernel: [ 522.924377] PSM: Modem oprt mode - 1
Jan 6 00:12:59 swi-mdm9x28 user.info qmi_shutdown_modem: Received subsystem shutdown complete in 4 second(s)
Jan 6 00:12:59 swi-mdm9x28 user.info qmi_shutdown_modem: Success.
Jan 6 00:12:59 swi-mdm9x28 user.info qmi_shutdown_modem: Modem shutdown complete
Jan 6 00:12:59 swi-mdm9x28 user.warn kernel: [ 523.543238] Stopping QCMAP_ConnectionManager:
Jan 6 00:12:59 swi-mdm9x28 user.warn kernel: [ 523.614730] Stopping qti: done

0 Likes

#13

How do I correlate the latest release of mangOH (red) to the legato_framework versions. I can see no versioning information on the mangOH platform sources. As such the latest mangOH release cannot completely build with a wide number of legato releases - I’ve gone through this exercise with many permutations and cannot find the “magic” correlating versions. (ie for wp77xx R9.1, legato 18.06.1 through 19.02.0 with latest mangOH sources and always get a make red_wp77xx failure). It’s a moving target.
…have I overlooked something?
HELP!

0 Likes

#14

I have build failure too with legato 19.02.0.
19.01.0 works with latest mangoh source.

I think you can update the legato to 19.01.0 and rebuild the update for the wp77

0 Likes

#15

When updating mangOH sources the resulting failure with each legato release changes. I’ve tried every version from 18.06.1 through 19.02.0 and each has it’s own failure (some are the same). …literally cleaned and rebuilt 10 times to try find the matching legato release. All to no avail.

We need a correlation between mangOH sources and with which Legato it will fully build - even if it’s only one release (ie mangOH version from 4/05/2019 builds with legato 18.10.3 or whatever).

0 Likes

#16

Do you believe that we should provide one a.spk for you to download ? Just to prove that the board is working.
We will provide all information related to tool chain and firmware release with that. One .spk for Wp85,76,77

0 Likes

#17

Asyal,

I think that’s an excellent idea.

FYI: Ryan Kirk commented on the Sierra Forum that there’s a stability bug in R9.1 - but others I’ve spoken with haven’t seen it yet. Ryan noted in the Forum that it is expected to be resolved in R11.

It should I’ve had a solid 5hr run w/o modem fault - a week or so ago I was able to obtain a complete build with 18.10.3 - which is whereupon I encounter the Modem stability issue. Since then mangOH sources have changed
and I cannot get a clean build with any of the Legato Releases. …and there is no way to return to a previous iteration of mangOH sources (nor even know what version you’re building).

These build issues are a second concern. That combinations of legato_frameworks (including the most recent) do not build with the latest/current mangOH sources.

Anything to move hte ball forward and pinch off some unknowns are a great idea!

Thanks,

Mike

0 Likes

#18

What mangoh sources are you talking about? Please note you can always experiment with the sdef file and troubleshoot what might be wrong. I dont think any change we did should have affected you. We usually test with a mangoh red before making changes. We will start mentioning the legato release against which we have tested

0 Likes

#19

@mpetersen

I will receive sample of WP7702 end of next week. I will test it with my mangoh build and get back to you.

Actually I use only WP76xx.

0 Likes

#20

Regarding Asyal’s suggestion above about providing a download: It seems a bit strange to me that someone (or the collective community) has taken the time and effort to set up and build a full Ubuntu VM which provides a perfect controlled environment for the Getting Started process. But then the documentation / firmware / software all fall outside that control and potentially become out of date pretty quickly.

I would say that it would be better to contain as much as possible within the VM so a known working set of source, documentation and whatever else necessary to provide a working baseline. OK, it may not be feasible to include module(s) firmware but at least specify a version to work with.

1 Like

#21

The documentation, VM and everything else provided on mangoh.io, is done by the mangoh team and some parts by the community. Yes, in theory your suggestion is right .
However, there are people in the community, who also like to see something working first and then follow the documentation.

Couple of items that should help with documentation going forward:.
a. module firmware releases are not happening at the same frequency as before so should reduce toolchain issues we had.
b. we will experiment with Leaf next month to see if that helps with the variations that come around with monthly legato releases

Ashish Syal

,

0 Likes

#22

OK just for reference - I tried a couple of different firmware versions and R10.1 worked with the current git pull.

That’s enough for me for now, I can get on with evaluating the platform and check the individual parts that I need. I’ve established a data connection, got gnss data, played some audio so looking good so far. (Note I’m not a software developer so once I’m happy I’ll pass it over to someone for actual application development).

0 Likes

#23

FYI: Late yesterday I too was able to successfully build red_wp77xx with Legato 19.01.0 and the mangOH release (update) as of 3:35pm CDT. (I’m no longer going to risk any ‘init updates’ to mangOH).

1 Like