2022-08-19_weekly_report

# 2022-08-19_weekly_report ###### tags: `weekly report` --------------------------------------------------- ## 08-15 ~ 08-19 done list --------------------------------------------------- ## Please write 08-15 ~ 08-19 done list here ### CP WIFI6 LTE5G * devicecp-healthcheck_device 1. Modify testItem LteAntenna to support lte module EM9191 module (MAIN/AUX/MIMO1/MIMO2) for 4-antenna connection check (LTE channel RX Working/Sub6 5G LTE channel RX no work) * DB 1. Add V90,V90W/V91W,V91WC pcba "EB00557-104/EB00558-104" in database project. * Facotry 1. Deploy localDB to pcba ES for "EB00557-104/EB00558-104". ### NSM 1. B629 IPMI當字句用不須讀寫MAC * ES verify mac : add soltlist from db slotconfig for filter ipmi mac interface. * device healthCheck testItem MacCompare : add soltlist from db slotconfig for filter ipmi mac interface. ### ISDV 1. study qts package qpkg數位簽章(pending) ### Checkpoint v2/v3 1. Compiled latest SDK uboot/kernel. buildroot compilation is failed. 2. Create new branch for SDK and added new SDK folders 3. unzip subfolders and modify makefile/scripts to compile code from folders instead of tar file. 4. git cherry-pick few commits 5. added all old dts files ### wifi6 1. v0 - tested wifi on device having 4G DDR, it's not working 2. Request checkpoint to share their images to test wifi on 4G DDR v1 device. 3. Enabled debug of wifi6 in v1 device and APK error. Waiting for compex to share any debugging method or tool to further analyze the issue. ### iSDV windows installer 1. Support for installation 2. Tested API for the Display configuration using windows application 3. Add shortcut for restart the controlserver and pm2 4. Research and get requirements for the uploading package in microsoft store 5. try to convert EXE file to MSIX file using MSIX packaging tool and advancedinstaller, but i can convert it but couldnt install using MSIX because of unverified code signing certificate. 6. Research related to code signing certificate for windows application 7. Generate pfx file and self code signing certificate for testing MSIX 8. Using unvalid certificate MSIX not installing ### ILLUMINA 1. Build illumina V1.0.25 Image 2. RELEASE SDQV SUPPORT 完整版精簡版 3. 協助部屬illumina to SDQV 10.10.81.15 ### DQV EMI 1. 協助SDQV 複製NSM OS image TO NVME 提供其驗證 2. 協助處理B557 B558 生產 ES 與 prdtname ### B629 1. B629 RAMSIZE 新增devicecase = 12 RAMSIZE判斷16G共8條 2. 申請測試序號 3. 新增 DB Prdtname NSM-FX7MB-PVT-R10 4. 修正 BCAKPCIE.py 判斷是否有四張BEAR卡 5. Temperature 測項修正 6. 關閉FAN測項 7. Voltage 測項修正 8. 修正USB23測項 ### GV Card API 1. Add the upload report function of FT3, test the upload report to MES and check result. 2. Add the function that can get write image config data from MES, test with the MES fake data and run the test on GV board. 3. Add the function in the FT3 flow that will generate the wirte image config and integrate the function with get SN function together. 4. Add the function that will generate the FT3 test command of each test step and put the necessary parameter into the test command. 5. Add a timer function that will send through socket, provide the test time for operator. 6. Run the test of the FT3 actual write image flow, try on different image version and check with viya on write image status. 7. Do the UI and Viya's test flow and function adjustment base on UI and console command necessary. ### CP API 1. Try on add the clear config setting function of the machine in FT3. 2. Setup the project environment and add the test step into FT3 test flow. 3. Setup the machine hardware environment and recover the wire connection in order to run the test. ### factory_console 1. delete message in devAlive 1. finish cpDelPreset.py 1. Add cpDelPreset sample from cpForce.py ### factory_console_gv 1. Fix devAlive and readConfig to avoid GV device stuck in uboot 1. Update runTest.py comments ### gv_server-installation 1. Add tool/logRMtftpserverInfo.sh, replace about username/password in log file ### gv_testprogram 1. GV Factory Update T1: 300ppb change to 2000ppb 1. get from gv team: Version: 01.00.02 1. fixed writeImageCfg/npe010_image_KAac_v4.0.2.cfg emmc_rf_image_path_name 1. add write image config file setting for our PC 1. add new cfg for writeImage: writeImageCfg/npe010_image_KAac_v4.0.2.cfg and writeImageCfg/npe010_image_v3.0.25.cfg 1. get from gv team: Version: 01.00.01 ### sdvoeui 1. fixed JIRA ISSUE: IEININVO-337, In the Settings Popup windows, The changed Device name cannot be displayed. - Add nameIDmapping in src/components/TxSettingBox/TxSettingBox.js, and use ID mapping to show the name - Add TXDeviceName and RXDeivceNameList in src/pages/operationMode/components/mainArea/components/dragExample/MyBox.js and src/pages/operationMode/components/mainArea/components/layoutGrid/MyBox.js 1. fixed JIRA ISSUE: IEININVO-335, In the MultiView page,Tx Device couldn't re-name - let selector title use name not deviceID - let deviceReducer dragAroundList always use deviceID, not some function use name 1. fixed JIRA ISSUE: IEININVO-347, After Click on the "Device Setup" button, appear the Create Display Array Popup Windows - Modify navigateTo action in src/pages/configuration/components/GridView/components/leftSection/components/noContent/noContent.js ### Deployment document 1) Prepared deployment document for D-tool and deployed to DQV D-tool Server 10.10.81.250 2) [edgeServer_V2.108A6_DB_V1.0.16A7](https://hackmd.io/GXVjVaKARBed26oKtXO4cg?view) ### iSDV 1) Completed Jira issue IEININVO-300 : No logs are recorded for the any apply function error messages. 2) Solution: ) Added error log message for Configuration -> Display -> Device Info apply setting 3) Included Add log saga to send log data using api ### Database backup BTC database backup 08-07-2022 details [BTC Backup 18-08-2022](https://hackmd.io/TmdfDh2vSjC18vsvVus7iQ?view) > DB Statistic before Delete: > dtaDB Size: 4.7GB > realtimestatus size: 2.8GB > > DB statistic after delete: > dtaDB Size: 2.2GB > realtimestatus size: 0.04 GB ## GV 1. Assisting DQV and NPI testing the GV test application. 2. Hide the time out info in the status box. 3. Add runtime info into the test task box. (except BI test) 4. Let FT3 can get SN from the devices. 5. Get test task runtime info from ' timer ' socket channel. 6. Reset the runtime info when rerun the test. ## ISDVoE-FT 1. Checking the iSDV-FT Jira issues. 2. Build ISDVoE-FT Dev environment. 3. Fixing the issue Jira No.IEININVO-275: Scrollbars are not working effectively. ----------------------------------------------------- ## 08-22 ~ 08-26 to-do list ----------------------------------------------------- ## Please write 08-22 ~ 08-26 to-do list here ### Checkpoint - v2/v3 1. Continue pushing commits from old to new SDK. 2. Resolve compilation errors and test each funtionlity on device. ### Wifi6 1. Follow up with compex on wifi debugging methods. 2. Check checkpoint shared images on v1 device and confirm wifi6 functionality. ### iSDV windows installer 1. Signing with valid code signing certificate 2. Fix the requirements and upload packages in microsoft store ### gv_testprogram 1. support GV update code to factory use ### sdvoeui/api [iSDV] 1. support log request ### B629 1. 修正LAN測項 2. A-TEST 3. Build Image 4. Release SDQV ### PUZZLE M801 1. 各測項整合，A-TEST RELEASE SDQV ### CP 1. V0 V1R V2 V3 協助 ORT 並進行技轉系統 ### iSDV 1)Need to discuss Log functionality with PM and include logs accordingly. ## Following is last week report --------------------------------------------------- ## 08-08 ~ 08-12 done list --------------------------------------------------- ### CP WIFI6 LTE5G * devicecp-healthcheck_device 1. Modify testItem LteAntenna to support lte module EM9191 5G RX(MAIN/AUX/MIMO1/MIMO2) for 4-antenna connection check( power 沒收到? 需直接確認 UI) (pending) * BSP 1. Debug wifiAP can't connected issue. kernel && rootfs are the same. -uboot DDR4G (can't connected) -uboot DDR2G (work find) * DQV/EMI 1. RF外驗需求(Compex 還會再提供一版WIFI FW 切換頻道功能) -WIFI:AP mode/定頻 -定頻指令spec -AP mode conf 設定及執行指令 -LTE 5G SIM connection 指令 2. Lte sim slot switch test(切換100次) ### ISDV 1. isdv qpkg 數位簽章(pending) qnap 自己的 qpkg 是透過 code signing server 建立 & 保管 key 只有 3rd party 才需要自行購買目前不支援 self sign 只有上面兩種模式 ### Wifi6 1. V0 - Debug wifi drivers after adding dts node for wifi. Found DMA memory pool and qmi_handle_init functions are not called. Recheck dts node added, compare tools pushed reserved_memory node to alias_node. After adding reserved_memory node as separate node, cnss2 probe is success with qmi_handle_init and DMA memory pool created. Tested wifi functionality on V0. 2. V0 - tested txpower on wifi using qcatestcmd and shared results of 2.4G and 5G txpower test. 3. V1 - Verified wifi on modified rootfs for v1-2GB device on 3 devices. Same rootfs on 4GB DDR V1 device did not work. Did factory reset on 4GB V1 device, used old working bin/firmware/driver files still AP is authentication mobile device but not associated without any error message. 4. Study of AP authentication and association related issues online. But for qualcomm wifi what debug tools can be used to check authentication status between AP and mobile is requested to compex for support. ### iSDV windows application 1. Modify installation process for python. 2. Uninstall python and mongodb. 3. Modify Task scheduler to run immediately once create the scheduler. 4. Rename the uninstaller 5. Tested in different device and virtual machine 6. Build iSDV package 7. Research related to the firewall access for nodejs and controlserver 8. Test iSDV windows installer version 1.0.3 and write documentation ### PUZZLE-IN001 IN002 1. IN001 IN002MODIFY A-TEST REPORT && RELEASE SDQV ### PUZZLE-5030 1. 5030 Netcard 有異常,會卡住,重做IMAGE 重新RELEASE SDQV ### illumina 1. 申請序號ILLUMINA IMA-COMPUTER-00-R10 測試序號版階2組系統2組 2. DB 增加 IMA-COMPUTE-00-R10 Prdtname 3. 部屬illumina 10.10.80.98 4. Illumina 完整版新增第五顆硬碟 ssd.py進行修正 IMA-COMPUTE-01-R10 精簡版 SSD = 3 IMA-COMPUTE-00-R10 FULL版 SSD = 5 5. CPLD2 40->42 IPMIFW QR11 -> QR12 修正資料庫 6. 精簡版FT1 FT2 驗證完畢 7. 完整版燒機完成 ### NSMRDIMM 1. 部屬NSMRDIMM to 10.10.81.11 A-TEST RELEASE SDQV ### DQV EMI 1. 協助RUSS V1R安裝RS232測試程式提供驗證 ## GV 1. Disable the buttons that may affect test while doing the test. 2. Adjusting the element type of station test execute button from div to button. 3. Adjusting the action label of update report from 'biTestUpdateRepot' to 'updateTestReport'. 4. Adding the reset processing of testState and stationOnTest parameters into reset function. 5. Adding a filter for MES station parameter to match the api request parameter. 6. Adding a filter for report result. 7. Adjusting the FT station test update result way that get report result from API after getting test operation ID. 8. Adjust the processing of update report sn to avoid uploading the same sn repeatedly. 9. Adding a notification to notify the uploading processing is begin. 10. Removing the report sn that upload report already. 11. Adding back the getting application info function. 12. Let socket port match api socket port in release edition. 13. Build code for release. 14. Write the ATest report of GV V1.0.0. 15. Demo the processing of GV FT1A to FT2B test. 16. Assisting DQV and NPI testing the GV test application. ## ISDVoE 1. Checking the jira issues. 2. Removing Option '76800' from the RS-232 baud select. ### iSDV 1) IEININVO-271 - Update firmware version to firmware name + product ID FIRMWARE Version => 1.3.2.0-Product ID 2) IEININVO-368 Update no content aread layout provided by Lisa [Layout](http://10.5.11.105/DesignCenter/PM%E3%80%81RD%20%E8%AB%8B%E9%80%B2%E5%85%A5/WEB/Stations/A_SDVoE%20Controller/v3_20220802/guideline/index.html#s9) 3) Included log messages, log message format provided by PM Allen Huang ### Database backup BTC database backup 10-08-2022 details ``` DB Statistic before Delete: dtaDB Size: 4.6GB realtimestatus size: 2.8GB DB statistic after delete: dtaDB Size: GB realtimestatus size: GB ``` [BTC Backup 10-08-2022](https://hackmd.io/TmdfDh2vSjC18vsvVus7iQ?view) ### api (iSDV) 1. add checkListIDs parameter in ProgressCheck to mapping response 2. fixed error response in ProgressCheck 1. add mcu fw update status 1. add deviceName in return message(FWStatus) 1. fixed fw update full run then return in ProgressCheck and some modify in updateFirmware 2. add cache/fwStatusCache.js 3. add eventReadFwStatus in api/event/eventApi.js 4. add getFwStatus in controllers/event/eventController.js 5. add fwStatus Check in updateFirmware 6. add EVENT_READ_FW_SCHEMA ### gv_server-installation 1. update UI path: build to public/dist 1. removed encode mode 2. auto upload to NAS add MD5 file ### sdvoeui (iSDV) 1. add cloneDeep(devicelist) in firmwareForm.js and mcuFirmwareForm.js to avoid devicelist change 1. fixed fwUpdate and McuFwUpdate api input: deviceId from item.deviceID not item.name 1. add mcu fw update status: - add objectId in src/pages/configuration/components/DeviceSetup/components/mcuFirmware/mcuFirmwareForm.js - add action run firmwareStatusAction in src/redux/sagas/configurationSaga/mcuFirmwareSaga.js 2. combi closeFirmwareModelBox closeMcuFirmwareModelBox to use same function by type: closeFirmwareModelBox 3. fixed and add error update in src/redux/sagas/configurationSaga/firmwareSaga.js 1. update src/redux/sagas/configurationSaga/firmwareSaga.js for fail case 2. add firmwareMsgFlag for CONFIGURATION_ACTIONS.UPDATE_FIRMWARE_STATUS 1. add getFwStatusState in src/selectors/deviceSetup.state.selector.js 2. add action: CONFIGURATION_ACTIONS.INIT_FIRMWARE_STATUS 3. update CONFIGURATION_ACTIONS.UPDATE_FIRMWARE_STATUS 4. finish src/components/ListInfoForm/ListInfoForm.js 1. add ListInfoForm.js base from src/pages/configuration/components/DeviceSetup/components/confirmationPopup/ConfirmationForm.js 2. add checkFW at src/pages/configuration/components/DeviceSetup/DeviceSetup.js 1. add objectId for FWUpdateCheck 2. add api link: checkFirmware : () => `/event-info/fwStatus`, 3. add FWUpdateCheck in saga, reducer, action and component: firmwareStatusForm.js ### GV Card API 1. Run the test with MES station transition stage, check the when test completed, the MES station will do transition as well. 2. Run the Burn-In test with Burn-In time length from MES. 3. Check the read config test item will verify the read info or not. 4. Add the test steps of write image and check info into the API for FT3 test. 5. Check the console setting and do the adjustment in order to fit FT3 requirement. 6. Add the start test API entry for FT3. 7. Add the function that will generate test command for FT3. 8. Add the function that will generate the config setting that FT3 needed when run test. ----------------------------------------------------- ## 08-15 ~ 08-19 to-do list ----------------------------------------------------- ### Wifi6 1. Continue expoloring AP authentication and authentication steps and how to debug further. 2. Discuss with compex on possibilities of wifi issue. 3. Continue wifi functionality check on 4GB DDR V1 device ### illumian 1. Build Image 2. Release SDQV ### PUZZLE-M801 1. CHECK CODE Prepare release ### DQV EMI 1. Support V1 WIFI EMI 外驗 ### iSDV windows application 1. Fix the windows firware access automatically 2. Fix the restart proAVC ## GV 1. Assisting DQV and NPI testing the GV test application. ### Edge Server Log Backup (IT) ### GitLab Backup to offline PC ### Jenkins Backup to offline PC ### Jumper Server Backup to offline PC

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.