profile
viewpoint
Chris Liang cyliangtw Nuvoton Taiwan

cyliangtw/amazon-freertos 1

amazon-FreeRTOS

OpenNuvoton/NuMaker-afr-docs 1

NuMaker amazon-freertos documentations

cyliangtw/aws-freertos 0

IoT operating system for microcontrollers.

cyliangtw/aws-iot-device-sdk-embedded-C 0

SDK for connecting to AWS IoT from a device using embedded C.

cyliangtw/azure-getting-started 0

This Getting Started guide is a series of tutorials that shows device developers how to start working with Azure RTOS.

cyliangtw/cmsis-core 0

CMSIS Core Headers

cyliangtw/esp8266-driver 0

The driver for the ESP8266 WiFi module

cyliangtw/mbed-hal 0

mbed low-level HAL API

cyliangtw/mbed-ls 0

mbedls detects Mbed Enabled devices connected to your computer

MemberEvent

created repositoryOpenNuvoton/OpenNuvoton-NuMaker-mbed-Azure-IoT-CSDK-DPS-example

Example for connection with Azure DPS and IoT Hub on Nuvoton's Mbed Enabled boards

created time in 11 hours

MemberEvent

push eventOpenNuvoton/mbed-os-example-for-azure

Anna Bridge

commit sha 5c51c06b5eefdc10b433e5b211bdd94bf6b95530

Update issue templates

view details

cyliangtw

commit sha ac3b8dd099e13c99721c0d9ae503b86ac0e99706

Support NuMaker M487, M263 & NUC472 platforms

view details

cyliangtw

commit sha 8ea6bdf0dd75efee65462f48a013c42ee71aa1cd

Update mbed-client-for-azure

view details

push time in a day

created repositoryOpenNuvoton/NuMaker-mbed-Azure-IoT-CSDK-DPS-example

Example for connection with Azure DPS and IoT Hub on Nuvoton's Mbed Enabled boards

created time in 2 days

MemberEvent

issue commentARMmbed/mbed-client-for-azure

Smaller ROM size

@ciarmcom , I updated this issue header with target, tool chain, OS version & how to reproduce info. .

cyliangtw

comment created time in 2 days

issue commentARMmbed/mbed-os-example-for-aws

Example breaks when using Mbed OS 6.3.0

What versions are newer than 6.2.1 ? The capture above shows feature-wisun (it's 5.15 based, it won't work with this example, same as 5.15). There's just 6.3.0 and now 6.4.0rc1 in preparation.

I tried to switch 4 tags as aa70f68, 0db72d0c(mbed-os-6.3.0), c6d65fe and 8ef0a435b(mbed-os-6.4.0-rc1), all of these 4 tags got the same compile error "No matching member" in Mbed on-line compiler.

Use only official releases (mbed-os-6.x.x tags) in the online compiler, same as you would do with mbed-cli .

Where to report this kind issue to notify no-line compiler team ?

COTASPAR

comment created time in 7 days

issue commentARMmbed/mbed-os-example-for-aws

Example breaks when using Mbed OS 6.3.0

Yes, it did working thru CLI on OS 6.3.0 . However, I tried all of newer versions than OS v6.2.1 in on-line compiler, still got the same compiler error. Is there any way to reflect this symptom to on-line compiler team ? image

COTASPAR

comment created time in 8 days

issue commentARMmbed/mbed-os-example-for-aws

Example breaks when using Mbed OS 6.3.0

Also build failed in on-line compiler. It seems relative to threadRoutine(pArgument); in iot_thread.cpp .

image

COTASPAR

comment created time in 8 days

issue commentARMmbed/mbed-client-for-azure

Smaller ROM size

@ciarmcom , Sorry for late update We forked & ported mbed-os-example-for-azure on NUMKAER_IOT_M487 in this repo , it could work but ROM size is too big. So, I cross check with azure-iot-preview based on azure-sdk-for-c, this M487 azure-iot-preview repo is ROM size as small as 131 KB. I used the same toolchain to build these 2 examples for Azure connection and the key factor is azure azure-iot-sdk-c v.s azure-sdk-for-c.

  • Target : NUMKAER_IOT_M487
  • Toolchain: ARMCC6 (Keil)
  • Mbed OS: both of v6.3.0
  • How to reproduce:
  1. import https://github.com/OpenNuvoton/mbed-os-example-for-azure, then build by $ mbed compile -m NUMAKER_IOT_M487 -t ARM
  2. Clone https://github.com/OpenNuvoton/azure-getting-started/, then git update sub modules. After that, to open Keil project to build https://github.com/OpenNuvoton/azure-getting-started/tree/nuvoton_azure_rtos/Nuvoton/M480/samples/demo_azure_iot/keil
cyliangtw

comment created time in 9 days

issue commentaws/aws-iot-device-sdk-embedded-C

AWS C-SDK OTA on Mbed OS?

Hi @tgsong, Thanks a lot. This OTA with backward compatibility of FreeRTOS OTA job is very much useful for existing AFR customers.

ccli8

comment created time in 13 days

issue commentaws/aws-iot-device-sdk-embedded-C

AWS C-SDK OTA on Mbed OS?

Hi @tgsong , Yes, I mean client side. The customer current system is client side running "AmazonFreeRTOS OTA-Agent" and utilize "Create a FreeRTOS OTA update job" in server side. They want to keep current AWS-IoT server code/setting and only migrate device/client side. According to your C-SDK OTA, could it accept the job document of "FreeRTOS OTA update job" ?

image

ccli8

comment created time in 14 days

issue commentaws/aws-iot-device-sdk-embedded-C

AWS C-SDK OTA on Mbed OS?

Hi @tgsong , Appreciate your OTA plan. Some of our customers applied AmazonFreeRTOS OTA-Agent 1 year ago and now is blocking in the compatibility issue of server side in the migration into Linux platform. Will this OTA cover the features of AmazonFreeRTOS OTA-Agent ? https://docs.aws.amazon.com/freertos/latest/userguide/ota-agent-library.html

ccli8

comment created time in 14 days

PublicEvent

push eventOpenNuvoton/NuMaker-mbed-TZ-secure-example

cyliangtw

commit sha c4bb37cd90455f6a4ec8bb55eb49eee12d02de26

Enable MBED_FAULT_HANDLER

view details

push time in 20 days

push eventOpenNuvoton/NuMaker-mbed-TZ-nonsecure-example

cyliangtw

commit sha 29188dde9c617aa195dc04508ee584ddadf656b8

Enable MBED_FAULT_HANDLER

view details

push time in 20 days

push eventOpenNuvoton/NuMaker-mbed-TZ-secure-example

cyliangtw

commit sha e15b894c003380e3c331bd255b6eadf9944833c2

Sync mbed_app_custom with master branch

view details

push time in 21 days

create barnchOpenNuvoton/NuMaker-mbed-TZ-nonsecure-example

branch : workshop_1013

created branch time in 21 days

create barnchOpenNuvoton/NuMaker-mbed-TZ-secure-example

branch : workshop_1013

created branch time in 21 days

push eventOpenNuvoton/NuMaker-mbed-TZ-nonsecure-example

Chris Liang

commit sha ccbf3991be333d7d0b4d6481e46bb2995aa11293

Update README.md

view details

push time in 22 days

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 ESP_WIFI_Status_t ESP_IO_Recv( ESP_WIFI_Object_t * pxObj, uint8_t pucRxBuf[], ui                     pcPtr = strtok(NULL, pcDelim);                     ucIpdLinkID = (uint8_t)atoi(pcPtr);                 }+                /* Get the IPD length */                 pcPtr = strtok(NULL, pcDelim);                 usIpdLength = (uint16_t)atoi(pcPtr);-                if (xWifiIpd[ucIpdLinkID].DataLength + usIpdLength > sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                    if (xWifiIpd[ucIpdLinkID].DataLength < sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                        configPRINTF(("ERROR: [%s] Get ipd %d bytes reach the maximum size !!\n", __func__, usIpdLength));-                    }++                if (ucIpdLinkID >= wificonfigMAX_SOCKETS || !xWifiIpd[ucIpdLinkID].IsOpen) {

@aggarw13 , My test log show it could pass all of your wifi unit tests. I guess your M487 board on hand maybe older version. Mine is NuMaker-IoT--M487 v1.3, if yours is v1.2 or previous version, the AT firmware of wifi module is too old and maybe unstable in some connection use case.

My test log: 0 0 [None] FreeRTOS_IPInit 1 0 [None] Write certificate... 2 0 [None] vTaskStartScheduler 3 318 [Tmr Svc] Wi-Fi module initialized. Connecting to AP... 4 318 [Tmr Svc] current task name is "Tmr Svc" 5 625 [Tmr Svc] Try to connect to AP "HUAWEI-F2C9" ... 6 5703 [Tmr Svc] Wi-Fi Connected to AP. Creating tasks which use network... 7 5703 [Tmr Svc] IP Address acquired 192.168.8.106 ---------STARTING TESTS--------- 8 8653 [TestRunner] WiFi Networks and strength: 9 8653 [TestRunner] NTCWLAN-N: -32 10 8653 [TestRunner] NTGuest: -33 11 8653 [TestRunner] WECWLAN_11n: -33 12 8653 [TestRunner] git_server: -43 13 8653 [TestRunner] NTGuest: -58 14 8653 [TestRunner] NTGuest: -75 15 8653 [TestRunner] WECWLAN_11n: -58 16 8653 [TestRunner] WECWLAN_11n: -74 17 8653 [TestRunner] likelike: -46 18 8655 [TestRunner] WECWLAN_11n: -40 19 8655 [TestRunner] End of WiFi Networks TEST(Full_WiFi, AFQP_WIFI_Scan) PASS TEST(Full_WiFi, AFQP_WIFI_GetMode_NullParameters) PASS 20 10879 [TestRunner] current task name is "TestRunner" 21 11186 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_GetIP_NullParameters) PASS 22 18376 [TestRunner] current task name is "TestRunner" 23 18683 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_GetMAC_NullParameters) PASS 24 31873 [TestRunner] current task name is "TestRunner" 25 32179 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_GetHostIP_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_Scan_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_NetworkAdd_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_NetworkGet_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_SetPMMode_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_GetPMMode_NullParameters) PASS 26 39930 [TestRunner] current task name is "TestRunner" 27 40236 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_Ping_NullParameters) PASS 28 47427 [TestRunner] current task name is "TestRunner" 29 47733 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 30 62892 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 31 77261 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_ConnectAP_NullParameters) PASS TEST(Full_WiFi, AFQP_WIFI_SetMode_InvalidMode) PASS 32 91551 [TestRunner] current task name is "TestRunner" 33 91857 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_GetHostIP_InvalidDomainName) PASS 34 112994 [TestRunner] current task name is "TestRunner" 35 113301 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_GetHostIP_DomainNameLengthExceeded) PASS TEST(Full_WiFi, AFQP_WIFI_NetworkDelete_DeleteNonExistingNetwork) PASS TEST(Full_WiFi, AFQP_WIFI_NetworkGetNonExistingNetwork) PASS TEST(Full_WiFi, AFQP_WIFI_SetPMMode_InvalidPMMode) PASS 36 134710 [TestRunner] current task name is "TestRunner" 37 135016 [TestRunner] Try to connect to AP "invalid ssid" ... 38 149389 [TestRunner] Try to connect to AP "invalid ssid" ... 39 163762 [TestRunner] Try to connect to AP "invalid ssid" ... TEST(Full_WiFi, AFQP_WIFI_ConnectAP_InvalidSSID) PASS 40 177941 [TestRunner] current task name is "TestRunner" 41 178247 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 42 193405 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 43 207776 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_ConnectAP_InvalidPassword) PASS 44 221953 [TestRunner] current task name is "TestRunner" 45 222259 [TestRunner] Try to connect to AP "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"46 222579 [TestRunner] Try to connect to AP "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"47 222899 [TestRunner] Try to connect to AP "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"TEST(Full_WiFi, AFQP_WIFI_ConnectAP_MaxSSIDLengthExceeded) PASS 48 223026 [TestRunner] current task name is "TestRunner" 49 223332 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 50 238495 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 51 252867 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... TEST(Full_WiFi, AFQP_WIFI_ConnectAP_MaxPasswordLengthExceeded) PASS 52 269376 [TestRunner] current task name is "TestRunner" 53 269682 [TestRunner] Try to connect to AP "HUAWEI-F2C9" ... 54 279550 [TestRunner] Wi-Fi reconnected following tests finished. TEST(Quarantine_WiFi, AFQP_WiFiOnOff) PASS TEST(Quarantine_WiFi, AFQP_WiFiMode) PASS

cyliangtw

comment created time in 23 days

PullRequestReviewEvent

push eventOpenNuvoton/mbed

cyliangtw

commit sha 39e2f311763da88fe2cb06fb24580e3634ce40f7

Apply the same NuMaker I2C timeout measurement to M2354

view details

push time in 24 days

PR opened ARMmbed/mbed-os

mbed-os-5.15: Nuvoton: Fix NuMaker I2C timeout

<!-- For more information on the requirements for pull requests, please see the contributing guidelines.

NOTE: Do not remove any of the template headings (even for optional sections) as this template is automatically parsed. -->

Summary of changes <!-- Required -->

This PR is to fix I2C timeout measurement for NuMaker platforms instead of hardcode max timer count on OS-5.15 branch. The same commit got approval in PR #13679 on OS-6.x master branch.

<!-- Please provide the following information:

Description of the the change (what is this fixing / adding / removing?).

Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Impact of changes <!-- Optional -->

<!-- If there are any implications for users taking this change then they must be provided here. For Major PR types this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Migration actions required <!-- Optional -->

<!-- This should only be applicable in Major PR types for which this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Documentation <!-- Required -->

<!-- Please provide details of any document updates required, including links to any related PRs against the docs repository. If no document updates are required please specify 'None', this at least tells us that this has been considered. -->


Pull request type <!-- Required -->

<!-- Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise). Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. --> [x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor) [] Feature update (New feature / Functionality change / New API) [] Major update (Breaking change E.g. Return code change / API behaviour change)


Test results <!-- Required -->

<!-- Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers. --> [] No Tests required for this change (E.g docs only update) [x] Covered by existing mbed-os tests (Greentea or Unittest) [] Tests / results supplied as part of this PR


Reviewers <!-- Optional -->

<!-- Request additional reviewers with @username or @team -->


@0xc0170 @andypowers

+49 -14

0 comment

7 changed files

pr created time in 24 days

create barnchOpenNuvoton/mbed

branch : nvt_i2c_timeout_5.15

created branch time in 24 days

delete branch OpenNuvoton/mbed

delete branch : nvt_iot_m252_target

delete time in 24 days

delete branch OpenNuvoton/mbed

delete branch : nvt_m263_button

delete time in 24 days

pull request commentARMmbed/mbed-os

Nuvoton: Fix NuMaker I2C timeout

One thought: shouldn't we use us_timestamp_t ticker_read_us(const ticker_data_t *const ticker); instead of us ticker?

@0xc0170 , ticker_read_us() is upper layer API and need critical section overhead. us_ticker_read() is low level API and could get more efficiency. Anyway, these 2 ways could achieve the same goal.

cyliangtw

comment created time in a month

MemberEvent

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 ESP_WIFI_Status_t ESP_IO_Recv( ESP_WIFI_Object_t * pxObj, uint8_t pucRxBuf[], ui                     pcPtr = strtok(NULL, pcDelim);                     ucIpdLinkID = (uint8_t)atoi(pcPtr);                 }+                /* Get the IPD length */                 pcPtr = strtok(NULL, pcDelim);                 usIpdLength = (uint16_t)atoi(pcPtr);-                if (xWifiIpd[ucIpdLinkID].DataLength + usIpdLength > sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                    if (xWifiIpd[ucIpdLinkID].DataLength < sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                        configPRINTF(("ERROR: [%s] Get ipd %d bytes reach the maximum size !!\n", __func__, usIpdLength));-                    }++                if (ucIpdLinkID >= wificonfigMAX_SOCKETS || !xWifiIpd[ucIpdLinkID].IsOpen) {

@sarenameas , We fixed the WiFi unit test failure by commit 381e87d, the last update will not block CPU to avoid unit-test failure.

cyliangtw

comment created time in a month

PullRequestReviewEvent

pull request commentARMmbed/mbed-os

Nuvoton: Fix NuMaker I2C timeout

@0xc0170 , Resolved gitattributetest issue by commit 3916026 and it already passed travis-ci/gitattributestest.

cyliangtw

comment created time in a month

push eventOpenNuvoton/mbed

cyliangtw

commit sha 3916026dd77af8cadc2a6fd95fab398caee5bdf8

Commit M451/NANO100 i2c_api again to resolve abnormal gitattribute

view details

push time in a month

pull request commentARMmbed/mbed-os

Nuvoton: Fix NuMaker I2C timeout

Please add details to the commit message how is this fixing (was 0xffffff causing an issue on the bus , what was it?)

@0xc0170 , I added more details to this commit message. As while H/W timer counting overflow, it will encounter i2c fake time out and impact i2c application.

cyliangtw

comment created time in a month

push eventOpenNuvoton/mbed

cyliangtw

commit sha ffee35a5c8e035324f4a70022b5c845fe3bac270

Fix NuMaker I2C timeout, some H/W timer count is 24 bits only, hardcode 0xffffffff causing wrong judgement of timeout as while H/W timer counting overflow.

view details

push time in a month

PR opened ARMmbed/mbed-os

Nuvoton: Fix NuMaker I2C timeout

<!-- For more information on the requirements for pull requests, please see the contributing guidelines.

NOTE: Do not remove any of the template headings (even for optional sections) as this template is automatically parsed. -->

Summary of changes <!-- Required -->

This PR is to fix I2C timeout measurement for NuMaker platforms instead of hardcode max timer count. <!-- Please provide the following information:

Description of the the change (what is this fixing / adding / removing?).

Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Impact of changes <!-- Optional -->

<!-- If there are any implications for users taking this change then they must be provided here. For Major PR types this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Migration actions required <!-- Optional -->

<!-- This should only be applicable in Major PR types for which this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Documentation <!-- Required -->

<!-- Please provide details of any document updates required, including links to any related PRs against the docs repository. If no document updates are required please specify 'None', this at least tells us that this has been considered. -->


Pull request type <!-- Required -->

<!-- Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise). Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. --> [x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor) [] Feature update (New feature / Functionality change / New API) [] Major update (Breaking change E.g. Return code change / API behaviour change)


Test results <!-- Required -->

<!-- Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers. --> [] No Tests required for this change (E.g docs only update) [x] Covered by existing mbed-os tests (Greentea or Unittest) [] Tests / results supplied as part of this PR


Reviewers <!-- Optional -->

<!-- Request additional reviewers with @username or @team -->


+49 -14

0 comment

7 changed files

pr created time in a month

create barnchOpenNuvoton/mbed

branch : nvt_i2c_timeout

created branch time in a month

issue openedARMmbed/mbed-client-for-azure

Smaller ROM size

According to my evaluation based on the same NUMAKER_IOT_M487 platform:

  • azure-iot-preview: ROM size is 131 KB without using heap.

  • mbed-os-example-for-azure: ROM size is 368 KB

In my consideration, the key factor is azure-sdk, azure-iot-sdk-c seems too big for MCU level IoT device, in the other way azure-sdk-for-c is Azure SDK for Embedded C, it's designed to allow small embedded (IoT) devices. So, is there any plan to apply azure-sdk-for-c to fulfill memory footprint of MCU level ?

created time in a month

push eventOpenNuvoton/mbed-os-example-for-azure

cyliangtw

commit sha 7f6eaad23300a79884632b0c5c2eb0a84c10b37a

Update mbed-client-for-azure

view details

push time in a month

push eventcyliangtw/mbed-client-for-azure

Chun-Chieh Li

commit sha d5865bd644b414effaa25d92098701fe6076757d

Fix socket send block error On send error NSAPI_ERROR_WOULD_BLOCK properly, we need to retry instead of error out.

view details

cyliangtw

commit sha 0ece1ca73d361e615880a2f0af3582046f508f83

Fixed tick overflow for different bit-width

view details

push time in a month

create barnchcyliangtw/mbed-client-for-azure

branch : nvt_tick_cnt

created branch time in a month

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 ESP_WIFI_Status_t ESP_IO_Recv( ESP_WIFI_Object_t * pxObj, uint8_t pucRxBuf[], ui                     pcPtr = strtok(NULL, pcDelim);                     ucIpdLinkID = (uint8_t)atoi(pcPtr);                 }+                /* Get the IPD length */                 pcPtr = strtok(NULL, pcDelim);                 usIpdLength = (uint16_t)atoi(pcPtr);-                if (xWifiIpd[ucIpdLinkID].DataLength + usIpdLength > sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                    if (xWifiIpd[ucIpdLinkID].DataLength < sizeof(xWifiIpd[ucIpdLinkID].Data)) {-                        configPRINTF(("ERROR: [%s] Get ipd %d bytes reach the maximum size !!\n", __func__, usIpdLength));-                    }++                if (ucIpdLinkID >= wificonfigMAX_SOCKETS || !xWifiIpd[ucIpdLinkID].IsOpen) {

@sarenameas, After cross checking, it could pass the previous version of wifi test code but fail in the current version of test code. At least, the old wifi driver without flow control could pass the current test code. So, it's not too difficult and we will fix it.

cyliangtw

comment created time in a month

PullRequestReviewEvent

push eventOpenNuvoton/mbed-os-example-for-azure

cyliangtw

commit sha 669bd76007681066285e3cbca0b0dede8320f36b

Support NuMaker M487, M263 & NUC472 platforms

view details

push time in a month

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 void vAssertCalled( const char * pcFile,  void vApplicationIdleHook( void ) {-    const uint32_t ulMSToSleep = 1;+//    const uint32_t ulMSToSleep = 1;

Yes, it's done in commit in eefce60 .

cyliangtw

comment created time in a month

PullRequestReviewEvent

push eventcyliangtw/aws-freertos

cyliangtw

commit sha eefce60a139e6dc43406c7ee912705621209630c

Removed the commented out code of M487 demo main.c & pkcs11_pal.c

view details

push time in a month

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 void vAssertCalled( const char * pcFile,  void vApplicationIdleHook( void ) {-    const uint32_t ulMSToSleep = 1;+//    const uint32_t ulMSToSleep = 1;

@sarenameas , Yes, it's till in progress and in waiting the approval of reviewers. The last added 3 commits could resolve warnings relative to this PR.

cyliangtw

comment created time in a month

PullRequestReviewEvent

push eventOpenNuvoton/mbed-os-example-for-aws

cyliangtw

commit sha 526c04d810fba549ed663b8d7cf1e772581dc98b

Add Nuvoton platform's entropy for OS 5.x & 6.x

view details

cyliangtw

commit sha 786b1acf2295d134304cc364b2694863b3efac01

Config json file for NuMaker M487, M263 & NUC472 platforms

view details

cyliangtw

commit sha cf9fc52b36e11eb7fbe66ff3c5e5e237b66dd6ce

Move wifi-ism43362 into STM target folder

view details

push time in a month

PR opened aws/amazon-freertos

Nuvoton: Fix M487 Keil project syntax error issue

<!--- Title -->

Description

This PR is to fix "can't change compiler options in Keil IDE" issue. The root cause is the wrong delimiter ';' in the user defined macro list in Keil project file, if user change any compiler options in Keil IDE environment, it will prompt "Syntax error in 'Define'". <!--- Describe your changes in detail -->

Checklist:

<!--- Go over all the following points, and put an x in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

  • [x] I have tested my changes. No regression in existing tests.
  • [ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+2 -2

0 comment

2 changed files

pr created time in 2 months

create barnchcyliangtw/aws-freertos

branch : nuvoton_keil_prj

created branch time in 2 months

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 /* Wi-Fi driver includes. */ #include "esp8266_wifi.h" +#define ESP8266_ALL_SOCKET_IDS      0xFF

Hi @muneebahmed10, I removed unused variable warnings #177-D in commit 208c3b4 & c3912ef. Other #177-D are in 3rd-party lib or free-rtos kernel, it could be suppressed by "--diag_suppress=" in Keil IDE.

cyliangtw

comment created time in 2 months

PullRequestReviewEvent

push eventcyliangtw/aws-freertos

cyliangtw

commit sha c3912ef529edd72c5fc7a5271bf0fc64dee028a2

Fix unsued variable in M487 demo main.c & pkcs11_pal.c

view details

push time in 2 months

push eventcyliangtw/aws-freertos

cyliangtw

commit sha 208c3b4e691523cab4b832286f9952767c874e50

Remove esp8266_wifi.c unused variables

view details

push time in 2 months

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 /* Wi-Fi driver includes. */ #include "esp8266_wifi.h" +#define ESP8266_ALL_SOCKET_IDS      0xFF

Hi @muneebahmed10,

I adjust the default max sockets as 5 to fulfill current wifi module and avoid the warnings #175-D in commit #175-D.

cyliangtw

comment created time in 2 months

PullRequestReviewEvent

push eventcyliangtw/aws-freertos

cyliangtw

commit sha 9a80a409826e9edfe163cb2c03e7b11759fcee6f

Adjust M487 wifi max sockets as 5

view details

push time in 2 months

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 /* Wi-Fi driver includes. */ #include "esp8266_wifi.h" +#define ESP8266_ALL_SOCKET_IDS      0xFF

Hi @muneebahmed10 , I built by Keil IDE, there are only 2 warnings:

compiling aws_dev_mode_key_provisioning.c...
compiling esp8266_wifi.c...
../../../../../vendors/nuvoton/sdk/middleware/wifi_esp8266/esp8266_wifi.c(404): warning:  #1293-D: assignment in condition
              if (pcRecv = strstr(pcPtr, 
T_PASSIVE_STRING)) {
../../../../../vendors/nuvoton/sdk/middleware/wifi_esp8266/esp8266_wifi.c(441): warning:  #1293-D: assignment in condition
              } else if (pcRecv = strstr(pcPtr, 
T_RECV_STRING)) {
../../../../../vendors/nuvoton/sdk/middleware/wifi_esp8266/esp8266_wifi.c: 2 warnings, 0 errors
cyliangtw

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentaws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

 void vLoggingPrintf( const char * pcFormat,                      ... );  /* Map the FreeRTOS printf() to the logging task printf. */-#define configPRINTF( x )          vLoggingPrintf x-+//#define configPRINTF( x )          vLoggingPrintf x+#define configPRINTF( x )            printf x /* Non-format version thread-safe print */-#define configPRINT( X )                  vLoggingPrint( X )+//#define configPRINT( X )                  vLoggingPrint( X )

@muneebahmed10 , it's done to enable vLogging message after drop the last commit of FreeRTOSConfig.h .

cyliangtw

comment created time in 2 months

PullRequestReviewEvent

push eventcyliangtw/aws-freertos

push time in 2 months

PR opened aws/amazon-freertos

Nuvoton: M487 WiFi Enhancement

<!--- Title -->

Description

This PR is to enhance M487 WiFi driver, including:

  • Add Socket Link ID validation including the check of each Link ID's state & the max sockets, it could avoid some risk of crash
  • Dynamic memory allocation for better memory footprint
  • Add IP reset & wait ESP AT ready for better WiFi stability
  • Support higher baud rate by flow control

<!--- Describe your changes in detail -->

Checklist:

<!--- Go over all the following points, and put an x in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

  • [x] I have tested my changes. No regression in existing tests.
  • [ ] My code is Linted.

@qiutongs @sarenameas

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+518 -137

0 comment

11 changed files

pr created time in 2 months

push eventcyliangtw/aws-freertos

cyliangtw

commit sha 88ad951201f1869742dfe2c51268369b433403e4

For simplicity, set printf as default stdout in demo code

view details

push time in 2 months

create barnchcyliangtw/aws-freertos

branch : nuvoton_wifi_enhance

created branch time in 2 months

PR opened ARMmbed/mbed-os

Nuvoton: Fixed NUC472 SD buffer alignment

<!-- For more information on the requirements for pull requests, please see the contributing guidelines.

NOTE: Do not remove any of the template headings (even for optional sections) as this template is automatically parsed. -->

Summary of changes <!-- Required -->

<!-- Please provide the following information:

Description of the the change (what is this fixing / adding / removing?).

Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

--> This PR is to correct NUC472 SD buffer alignment. According to NUC472 SD H/W spec, to change the alignment as 4 bytes instead of original 4KB, it could avoid the most wasting of PAD of SD buffer.

Impact of changes <!-- Optional -->

<!-- If there are any implications for users taking this change then they must be provided here. For Major PR types this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Migration actions required <!-- Optional -->

<!-- This should only be applicable in Major PR types for which this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Documentation <!-- Required -->

<!-- Please provide details of any document updates required, including links to any related PRs against the docs repository. If no document updates are required please specify 'None', this at least tells us that this has been considered. -->


Pull request type <!-- Required -->

<!-- Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise). Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. --> [x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor) [] Feature update (New feature / Functionality change / New API) [] Major update (Breaking change E.g. Return code change / API behaviour change)


Test results <!-- Required -->

<!-- Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers. --> [] No Tests required for this change (E.g docs only update) [x] Covered by existing mbed-os tests (Greentea or Unittest) [] Tests / results supplied as part of this PR


Reviewers <!-- Optional -->

<!-- Request additional reviewers with @username or @team -->


+3 -3

0 comment

1 changed file

pr created time in 2 months

create barnchOpenNuvoton/mbed

branch : nvt_nuc472_sd

created branch time in 2 months

PR opened ARMmbed/mbed-os

Nuvoton: Set M252 Flash internal size for kv store test

<!-- For more information on the requirements for pull requests, please see the contributing guidelines.

NOTE: Do not remove any of the template headings (even for optional sections) as this template is automatically parsed. --> The kvstore test uses last two sectors of flash for its test, but M252’s sector size is only 512 bytes and is too small for this test. Thus, to set M252 Flash internal default size as 8KB for kv store test in /tdb_internal/mbed_lib.json .

Summary of changes <!-- Required -->

<!-- Please provide the following information:

Description of the the change (what is this fixing / adding / removing?).

Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Impact of changes <!-- Optional -->

<!-- If there are any implications for users taking this change then they must be provided here. For Major PR types this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Migration actions required <!-- Optional -->

<!-- This should only be applicable in Major PR types for which this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Documentation <!-- Required -->

<!-- Please provide details of any document updates required, including links to any related PRs against the docs repository. If no document updates are required please specify 'None', this at least tells us that this has been considered. -->


Pull request type <!-- Required -->

<!-- Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise). Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. --> [x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor) [] Feature update (New feature / Functionality change / New API) [] Major update (Breaking change E.g. Return code change / API behaviour change)


Test results <!-- Required -->

<!-- Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers. --> [] No Tests required for this change (E.g docs only update) [x] Covered by existing mbed-os tests (Greentea or Unittest) [] Tests / results supplied as part of this PR


Reviewers <!-- Optional -->

<!-- Request additional reviewers with @username or @team --> @MarceloSalazar

+3 -0

0 comment

1 changed file

pr created time in 2 months

create barnchOpenNuvoton/mbed

branch : nvt_m252_kv

created branch time in 2 months

push eventOpenNuvoton/N9H_emWin_Template

cyliangtw

commit sha ee41067d218f822c1f7e29ee8644cdfc16b5031d

Create Thermostat_N9H30_Linux folder

view details

push time in 2 months

pull request commentARMmbed/mbed-os

[mbed-os-5.15] Nuvoton: Fixed NUC472 SD buffer alignment

@ciarmcom CI build can't complete due to "arm-none-eabi-gcc is currently not installed" in your build-machine. Please help to check it.

cyliangtw

comment created time in 2 months

pull request commentARMmbed/mbed-os-example-pelion

Update to Mbed OS 5.15.5

@teetak01, @MarceloSalazar NUMAKER_PFM_NUC472-GCC_ARM build fail issue could be resolved by fixing NUC472 SD buffer alignment issue in mbed-os PR #13512

teetak01

comment created time in 2 months

PR opened ARMmbed/mbed-os

[mbed-os-5.15] Nuvoton: Fixed NUC472 SD buffer alignment

<!-- For more information on the requirements for pull requests, please see the contributing guidelines.

NOTE: Do not remove any of the template headings (even for optional sections) as this template is automatically parsed. -->

Summary of changes <!-- Required -->

<!-- Please provide the following information:

Description of the the change (what is this fixing / adding / removing?).

Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

--> This PR is to correct NUC472 SD buffer alignment as 4 bytes instead of original 4K, it could resolve the issue of mbed-os-example-pelion NUC472 GCC build failed in Pelion PR #147

Impact of changes <!-- Optional -->

<!-- If there are any implications for users taking this change then they must be provided here. For Major PR types this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Migration actions required <!-- Optional -->

<!-- This should only be applicable in Major PR types for which this field is MANDATORY.

NOTE: This section is automatically written to release notes for Feature and 
Major releases and should contain enough details for a user.

-->

Documentation <!-- Required -->

<!-- Please provide details of any document updates required, including links to any related PRs against the docs repository. If no document updates are required please specify 'None', this at least tells us that this has been considered. -->


Pull request type <!-- Required -->

<!-- Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise). Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. --> [x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor) [] Feature update (New feature / Functionality change / New API) [] Major update (Breaking change E.g. Return code change / API behaviour change)


Test results <!-- Required -->

<!-- Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers. --> [] No Tests required for this change (E.g docs only update) [x] Covered by existing mbed-os tests (Greentea or Unittest) [] Tests / results supplied as part of this PR


Reviewers <!-- Optional -->

<!-- Request additional reviewers with @username or @team --> @MarceloSalazar @teetak01

+3 -3

0 comment

1 changed file

pr created time in 2 months

create barnchOpenNuvoton/mbed

branch : nvt_nuc472_sd_5.15

created branch time in 2 months

pull request commentARMmbed/mbed-os-example-pelion

Update to Mbed OS 5.15.5

It seems the path of MBEDTLS_ENTROPY_NV_SEED encounter overflow of internal-SRAM. If I use MBEDTLS_ENTROPY_HARDWARE_ALT, it's fine to build in GCC tool-chain. ( https://os.mbed.com/teams/Nuvoton/code/mbed-os-example-pelion//file/d147172e94b5/mbed_app.json/)

teetak01

comment created time in 2 months

push eventOpenNuvoton/amazon-freertos

cyliangtw

commit sha 5581590d48465349bb027a6db7361d71afdef203

Fixed wifi fail in cpu-reset case

view details

push time in 3 months

push eventcyliangtw/amazon-freertos

cyliangtw

commit sha 5581590d48465349bb027a6db7361d71afdef203

Fixed wifi fail in cpu-reset case

view details

push time in 3 months

push eventOpenNuvoton/Mbed-to-Azure-IoT-Hub

cyliangtw

commit sha 1df206684ebe3ec28f5c7b3704972a9bfe8e5058

Define user-button and correct M263 keypad

view details

push time in 3 months

push eventOpenNuvoton/Mbed-to-Azure-IoT-Hub

cyliangtw

commit sha 6f3943fbef801c8391f6bd3a2d5ebdb8e20f83aa

Upgrade OS to v5.15.4 and support M263/NUC472/M2351 targets

view details

push time in 3 months

push eventOpenNuvoton/Mbed-to-Azure-IoT-Hub

cyliangtw

commit sha d2d9c854e3ae06fe8b3bfe80a2ff3c015e2f359b

Verify Azure IoT Hub on M487

view details

push time in 3 months

push eventOpenNuvoton/N9H_emWin_Template

cyliangtw

commit sha 7c60489da2b88c7fefd13cc2dd32633b46a604eb

Create Cooking_N9H26_Linux

view details

push time in 3 months

push eventOpenNuvoton/amazon-freertos

Chih-Chiang Chang

commit sha 81fee29a1f8e6c49e0725e948f52000bad31df69

M487 WiFi driver modifications. 1. Use dynamic allocate buffer instead of static array 2. Support TCP passive mode 3. Support Serial RTS/CTS 4. Support H/W reset

view details

Chih-Chiang Chang

commit sha 12addddb779933f0adb32abc1a0032e45a9f58ae

M487 demos and tests support new WiFi driver

view details

Chih-Chiang Chang

commit sha f48152f45bfc14348f6e73542ea2e58b29b47425

M487 WiFi driver supports high baudrate

view details

Chih-Chiang Chang

commit sha 3cb6fe032d075500aa918fce23e283d9372316d7

M487 tests add WiFi baudrate setting

view details

push time in 3 months

issue closedcoisme/Mbed-to-Azure-IoT-Hub

Could not set ca cert! Returned -3003

TLS-socket can't set the 4 root certificates,it failed at ret = socket->set_root_ca_cert(SSL_CA_PEM);. Mbed trace show crt_parse() failure as below:

Time is now Mon Jul 27 11:21:09 2020
Connecting to host nvt001.azure-devices.net:8883 ...
[ERR ][TLSW]: mbedtls_x509_crt_parse() failed: -0xffffffff (1): UNKNOWN ERROR CODE (0001)
Could not set ca cert! Returned -3003

closed time in 3 months

cyliangtw

issue commentcoisme/Mbed-to-Azure-IoT-Hub

Could not set ca cert! Returned -3003

After apply the last Root CA certificates, it's resolved.

cyliangtw

comment created time in 3 months

push eventOpenNuvoton/Mbed-to-Azure-IoT-Hub

ksaye

commit sha 926e10ab9f445e1e2a2d5e4eb2e4585abfb5cbfe

updating the latest Microsoft certificates I believe they have changed.

view details

Osamu Koizumi

commit sha 666f7225b324ae7d77ed10b2d36652417fe7aa6d

Merge pull request #5 from ksaye/patch-1 updating the latest Microsoft certificates

view details

Osamu Koizumi

commit sha 23fab671a18a2eadb840c9bf9aca2e15c3f3b87b

Update mbed-mqtt.lib

view details

cyliangtw

commit sha 704c20a750febb73e452888eb8d90e546996b4ce

Support NuMaker-IoT-M487 on Mbed OS v5.15

view details

cyliangtw

commit sha 3e12b3b145058ffd160907701f83e7bc5d3926e6

Set OS lib v5.15

view details

cyliangtw

commit sha 71ae53f79d315679a09f77865765c71711e9d6ab

Support NUMAKER_PFM_M487

view details

push time in 3 months

more