do you need gstreamer?
i am not sure why adding gstreamer will have problem, maybe it is too big.
You can try on R9 and see if it can compile successfully
Hi @jyijyi
I need gstreamer to take picture or you can give me another method ?
did you test in R9 which has been validated?
BTW, how about using IMAGE_INSTALL_append instead of IMAGE_INSTALL in ./meta-swi/meta-swi-mdm9x28/recipes-core/images/mdm9x28-image.inc
IMAGE_INSTALL_append = " gstreamer1.0"
IMAGE_INSTALL_append = " gstreamer1.0-plugins-base"
IMAGE_INSTALL_append = " gstreamer1.0-plugins-good"
Hi @jyijyi ,
I don’t know why it cannot update.
-rw-r--r-- 1 root root 0 Jan 6 08:03 tmpfdbtable.txt
-rw-r--r-- 1 root root 42248736 Jan 6 08:02 yocto_wp76xx.4k.cwe
root@swi-mdm9x28-wp:/tmp# fwupdate download ./yocto_wp76xx.4k.cwe
Connecting to service ...
Can't open file './yocto_wp76xx.4k.cwe' : No such file or directory
root@swi-mdm9x28-wp:/tmp#
maybe you can use absolute path /tmp/yocto_wp76xx.4k.cwe
or you can use fdt tool
Hi @jyijyi ,
Thanks! it worked.
Hi @jyijyi ,
I have a question that I cannot find uvcvide.ko in rootfs after I update the image, but I can find the ko in build folder
test@test-UN62:~/workspace/yocto/build_bin$ find -name "uvcvideo.ko"
./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/linux-quic/3.18.131-r1/packages-split/kernel-module-uvcvideo-3.18.131/lib/modules/3.18.131/kernel/drivers/media/usb/uvc/uvcvideo.ko
./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/linux-quic/3.18.131-r1/image/lib/modules/3.18.131/kernel/drivers/media/usb/uvc/uvcvideo.ko
./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/linux-quic/3.18.131-r1/build/drivers/media/usb/uvc/uvcvideo.ko
./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/linux-quic/3.18.131-r1/package/lib/modules/3.18.131/kernel/drivers/media/usb/uvc/uvcvideo.ko
./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/mdm9x28-image-minimal/1.0-r0.0/rootfs/lib/modules/3.18.131/kernel/drivers/media/usb/uvc/uvcvideo.ko
How could I check it in image?
can you do “modprobe uvcvideo”?
Hi @jyijyi ,
I do modporbe uvcvideo
root@swi-mdm9x28:~# modprobe uvcvideo
modprobe: module uvcvideo not found in modules.dep
So I do find ko and the result is cannot find the ko.
i remember at that time in R9, I directly added those flags in./kernel/arch/arm/configs/mdm9607_defconfig
CONFIG_MEDIA_SUPPORT=m
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_USB_SUPPORT=y
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_V4L_PLATFORM_DRIVERS=y
Hi @jyijyi ,
Why add it in “swi-mdm9x28.conf”.
I added in camera.cfg and add it into defconfig then I can see the ko in build folder.
i did not do it in this way, I remember I directly add it to ./kernel/arch/arm/configs/mdm9607_defconfig, and it works for me
But I did it in R9 at that time…
You can revert back and see if it helps
BTW, have you directly modprobe the ko in ./tmp/work/swi_mdm9x28_wp-poky-linux-gnueabi/linux-quic/3.18.131-r1/image/lib/modules/3.18.131/kernel/drivers/media/usb/uvc/uvcvideo.ko
Also have you checked ati8 and see if you have really updated your yocto image?
Hi @jyijyi,
I will use R9 then compiled it again !
ok
I still advise you to double check
- ati8 to see if you really download the yocto image with correct date
- transfer the uvcvideo.ko and see if you can make it work by modprobe
I just tried with to add those flags in./kernel/arch/arm/configs/mdm9607_defconfig and build in FW16.0.1, no problem is found to do “modprobe uvcvideo”
That means the driver has been embedded in the image.
root@fx30:~# microcom /dev/ttyAT
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7609
Revision: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
IMEI: 359782080112345
IMEI SV: 14
FSN: WA803370312345
+GCAP: +CGSM
OK
ati8
Legato Ver: 19.11.5.86c98a88_535cbe294c2b528b4fc38a47809866e9
Yocto Ver: SWI9X07Y_02.37.10.02 2023-05-10_14:59:02
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed May 10 14:41:02 UTC 2023
LK Ver: 1.3.0_e8dee1d404
RootFS Ver: SWI9X07Y_02.37.10.02 2023-05-10_14:59:02
UserFS Ver: unknown
MCU Ver: 002.015
OK
root@fx30:~# modprobe uvcvideo
root@fx30:~#
Hi @jyijyi ,
Could you tell me how to do it?
Could you give me your linux-quic_git.bb and mdm9x28-image.inc ?
In R16 when I modify then it will compile error in the “#include <…/sierra/api/ssmemudefs.h>”
Hi @jyijyi
I think I update failed.
ati8
Legato Ver: 18.03.0_b463e04cf08fb8d8f1ea5ee00d7894c0
Yocto Ver: SWI9X07Y_02.16.02.00 2018-04-19_22:03:13
OS Ver: Linux version 3.18.44 (jenkins@jenkins) (gcc version 6.2.0 (GCC) ) #2 PREEMPT Thu Apr 19 22:05:25 UTC 2018
LK Ver: SWI9X07Y_02.16.02.00
RootFS Ver: SWI9X07Y_02.16.02.00 2018-04-19_22:03:13
UserFS Ver: unknown
MCU Ver: 002.009
How to do update ?
I use scp upload image to tmp then use fwupdate to update image.
BTW I use “WP7607-1”
My update log is below:
[ 854.630354] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data7
Sent SIGKILL to all processes
Requesting system reboot
[ 855.920825] reboot: Restarting system
[ 855.924415] Failed to disable secure wdog debug: -4
[ 855.928349] Calling SCM to disable SPMI PMIÿ
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-00081
S - IMAGE_VARIANT_STRING=LAATANAZA
S - OEM_IMAGE_VERSION_STRING=jenkins
S - Boot Config, 0x000002e1
B - 1216 - PBL, Start
B - 3720 - bootable_media_detect_entry, Start
B - 5024 - bootable_media_detect_success, Start
B - 5028 - elf_loader_entry, Start
B - 8484 - auth_hash_seg_entry, Start
B - 32146 - auth_hash_seg_exit, Start
B - 82733 - elf_segs_hash_verify_entry, Start
B - 129576 - PBL, End
B - 137951 - SBL1, Start
B - 195718 - pm_device_init, Start
B - 215879 - PM_SET_VAL:Skip
D - 18452 - pm_device_init, Delta
B - 217221 - boot_config_data_table_init, Start
D - 0 - boot_config_data_table_init, Delta - (0 Bytes)
B - 225974 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:129
B - 232867 - sbl1_ddr_set_params, Start
B - 236680 - Pre_DDR_clock_init, Start
D - 213 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 249398 - pm_driver_init, Start
D - 4483 - pm_driver_init, Delta
B - 255681 - cpr_init, Start
D - 122 - cpr_init, Delta
B - 260256 - cpr_cx_mx_apc_vol_update, Start
D - 91 - cpr_cx_mx_apc_vol_update, Delta
B - 275506 - clock_init, Start
D - 183 - clock_init, Delta
B - 275750 - boot_flash_init, Start
D - 39924 - boot_flash_init, Delta
B - 776713 - boot_flash_swi_ddr_init, Start
D - 27724 - boot_flash_swi_ddr_init, Delta
B - 959164 - hw_family:5, hw_type:19, hw_rev:40
B - 960353 - SSMEM init OK
B - 984021 - opening partition 0:SWIFOTA
B - 20203993 - smart recovery counter cleared
B - 30148945 - VERSION=Wed May 10 08:27:10 UTC 2023,SIZE 0x284aa20, IMG_TYPE=0x8,NON-SPKG/FOTA IMG,AUTH_SKIPPED=SYST,SUBIMAGE=SYST,ERROR=Flash write failed: Flash write error (0X2),STATUS=FAIL
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-00081
S - IMAGE_VARIANT_STRING=LAATANAZA
S - OEM_IMAGE_VERSION_STRING=jenkins
S - Boot Config, 0x000002e1
B - 1216 - PBL, Start
Does it mean download fail ?
Now the module will crash how could I solve this status?
ubiattach: error!: cannot attach mtd13
error 22 (Invalid argument)
Unable to attach mtd13 to UBI logical device 0
It is not dual system logic
System error!
[ 1.650536] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 1.650536]
[ 1.658673] CPU: 0 PID: 1 Comm: init Not tainted 3.18.44 #2
[ 1.664216] [<c001486c>] (unwind_backtrace) from [<c00126e8>] (show_stack+0x10/0x14)
[ 1.671926] [<c00126e8>] (show_stack) from [<c07e0c3c>] (panic+0x108/0x2ec)
[ 1.678870] [<c07e0c3c>] (panic) from [<c0022618>] (do_exit+0x480/0x924)
[ 1.685551] [<c0022618>] (do_exit) from [<c0022b98>] (SyS_exit_group+0x0/0x10)
[ 1.692757] [<c0022b98>] (SyS_exit_group) from [<00000004>] (0x4)
[ 2.704778] cpr_panic_callback: apc_corner: [corner:7, fuse_corner:3] = 1212500 uV
[ 2.711429] Rebooting in 5 seconds..
Then it will enter DM port. How could I use DM port to update FW or rootfs ?
you can use fdt tool.
BTW, you can try my yocto image:
Can you give me your modify, because my R16 is alway failed when I add camera.
And what command I should use ?