diff --git a/configuration/samples/bare/README.md b/configuration/samples/bare/README.md index 5018efa..c5b4fa5 100644 --- a/configuration/samples/bare/README.md +++ b/configuration/samples/bare/README.md @@ -36,7 +36,7 @@ For example, if you create project with C++ option and CC-RX compiler, you will _end = .; } > RAM -2.3. When using RX microcontrollers with DPFPUs +2.3. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/boot_loader/README.md b/configuration/samples/boot_loader/README.md index b541441..663c945 100644 --- a/configuration/samples/boot_loader/README.md +++ b/configuration/samples/boot_loader/README.md @@ -61,7 +61,7 @@ This issue is fixed from e2 studio 2023-04 and Smart Configurator for RX 2.17. 2.3. If your e2 studio version is older than 2023-10, "CK-RX65N (DUAL)" will not be displayed on the Target Board when creating ADU sample project. Please use the latest version of e2 studio. -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/guix_8bpp/README.md b/configuration/samples/guix_8bpp/README.md index 307644d..7398d09 100644 --- a/configuration/samples/guix_8bpp/README.md +++ b/configuration/samples/guix_8bpp/README.md @@ -64,7 +64,7 @@ to quickly go to Change Device dialog and change target device to R5F572NN. This issue is fixed from board version v1.12. -2.5. When using RX microcontrollers with DPFPUs +2.5. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk/README.md b/configuration/samples/iot_sdk/README.md index 82535ea..8cec3b7 100644 --- a/configuration/samples/iot_sdk/README.md +++ b/configuration/samples/iot_sdk/README.md @@ -45,7 +45,7 @@ In Smart Configurator editor (.scfg) This issue is fixed from e2 studio 2023-04 and Smart Configurator for RX 2.17. -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk/rsk-rx671/README.md b/configuration/samples/iot_sdk/rsk-rx671/README.md index b57111e..d551aac 100644 --- a/configuration/samples/iot_sdk/rsk-rx671/README.md +++ b/configuration/samples/iot_sdk/rsk-rx671/README.md @@ -64,7 +64,7 @@ In Smart Configurator editor (.scfg) check "CTS2#/RTS2#/SS2# Pin" And [Generate Code] -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk/rx72n-envision-kit/README.md b/configuration/samples/iot_sdk/rx72n-envision-kit/README.md index 2983e1b..228b858 100644 --- a/configuration/samples/iot_sdk/rx72n-envision-kit/README.md +++ b/configuration/samples/iot_sdk/rx72n-envision-kit/README.md @@ -52,7 +52,7 @@ In Smart Configurator editor (.scfg) - on the right panel, check and change the pin function if it is incorrect: RXDx and TXDx should be used but the default setting could be SMISOx and SMOSIx -2.5. When using RX microcontrollers with DPFPUs +2.5. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk_pnp/README.md b/configuration/samples/iot_sdk_pnp/README.md index 2954863..db0ac0a 100644 --- a/configuration/samples/iot_sdk_pnp/README.md +++ b/configuration/samples/iot_sdk_pnp/README.md @@ -45,7 +45,7 @@ In Smart Configurator editor (.scfg) This issue is fixed from e2 studio 2023-04 and Smart Configurator for RX 2.17. -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk_pnp/rsk-rx671/README.md b/configuration/samples/iot_sdk_pnp/rsk-rx671/README.md index 22923c5..270da20 100644 --- a/configuration/samples/iot_sdk_pnp/rsk-rx671/README.md +++ b/configuration/samples/iot_sdk_pnp/rsk-rx671/README.md @@ -63,7 +63,7 @@ In Smart Configurator editor (.scfg) check "CTS2#/RTS2#/SS2# Pin" And [Generate Code] -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iot_sdk_pnp/rx72n-envision-kit/README.md b/configuration/samples/iot_sdk_pnp/rx72n-envision-kit/README.md index 936484c..d5a6318 100644 --- a/configuration/samples/iot_sdk_pnp/rx72n-envision-kit/README.md +++ b/configuration/samples/iot_sdk_pnp/rx72n-envision-kit/README.md @@ -52,7 +52,7 @@ In Smart Configurator editor (.scfg) - on the right panel, check and change the pin function if it is incorrect: RXDx and TXDx should be used but the default setting could be SMISOx and SMOSIx -2.5. When using RX microcontrollers with DPFPUs +2.5. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/iperf/README.md b/configuration/samples/iperf/README.md index 03dc853..f7a5cab 100644 --- a/configuration/samples/iperf/README.md +++ b/configuration/samples/iperf/README.md @@ -39,7 +39,7 @@ For example, if you create project with C++ option and CC-RX compiler, you will 2.3. Current Iperf sample project does not work well with JPerf. We will improve the sample at next version. -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/low_power/README.md b/configuration/samples/low_power/README.md index d078c25..2646382 100644 --- a/configuration/samples/low_power/README.md +++ b/configuration/samples/low_power/README.md @@ -42,7 +42,7 @@ In Smart Configurator editor (.scfg) - at Pin Function, select "Interrupt controller unit" - on the right panel, check and change the pin assignment for IRQ channel being used if it is incorrect -2.4. When using RX microcontrollers with DPFPUs +2.4. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/minimal/README.md b/configuration/samples/minimal/README.md index 23a0603..eee749e 100644 --- a/configuration/samples/minimal/README.md +++ b/configuration/samples/minimal/README.md @@ -43,7 +43,7 @@ In Smart Configurator editor (.scfg) - on the right panel, check and change the pin function if it is incorrect: RXDx and TXDx should be used but the default setting could be SMISOx and SMOSIx -2.4 When using RX microcontrollers with DPFPUs +2.4 When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/ping/README.md b/configuration/samples/ping/README.md index 46b1709..971337c 100644 --- a/configuration/samples/ping/README.md +++ b/configuration/samples/ping/README.md @@ -51,7 +51,7 @@ please open libs\netxduo_addons\addons\dns\nxd_dns.c and comment out _nxde_dns_h This issue is fixed from Smart Configurator for RX 2.17. -2.5 When using RX microcontrollers with DPFPUs +2.5 When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/ping/rsk-rx671/README.md b/configuration/samples/ping/rsk-rx671/README.md index 56f8e78..138d3d1 100644 --- a/configuration/samples/ping/rsk-rx671/README.md +++ b/configuration/samples/ping/rsk-rx671/README.md @@ -46,7 +46,7 @@ For example, if you create project with C++ option and CC-RX compiler, you will _end = .; } > RAM -2.3. When using RX microcontrollers with DPFPUs +2.3. When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/ramdisk/README.md b/configuration/samples/ramdisk/README.md index 10710f9..2e46df0 100644 --- a/configuration/samples/ramdisk/README.md +++ b/configuration/samples/ramdisk/README.md @@ -45,7 +45,7 @@ to quickly go to Change Device dialog and change target device to R5F572NN. This issue is fixed from board version v1.12. -2.3 When using RX microcontrollers with DPFPUs +2.3 When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/usbx_device_cdc_acm/README.md b/configuration/samples/usbx_device_cdc_acm/README.md index b4a3988..5526a10 100644 --- a/configuration/samples/usbx_device_cdc_acm/README.md +++ b/configuration/samples/usbx_device_cdc_acm/README.md @@ -40,7 +40,7 @@ When using GCC compiler, the "_end" section in src/linker_script.ld should be at When you connect RX65N Cloud Kit to your PC and get USB device not recognized message from Windows, please go to Clock page of Smart Configurator, enable SCKCR2 and set USB clock to 48MHz. -When using RX microcontrollers with DPFPUs +When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: diff --git a/configuration/samples/usbx_hmsc/README.md b/configuration/samples/usbx_hmsc/README.md index 11fa3d1..dd60711 100644 --- a/configuration/samples/usbx_hmsc/README.md +++ b/configuration/samples/usbx_hmsc/README.md @@ -44,7 +44,7 @@ In Smart Configurator editor (.scfg) This issue will be fixed at that next update of RSK board description file. -2.4 When using RX microcontrollers with DPFPUs +2.4 When using RX microcontrollers with DPFPU Target projects (RX72N, RX671): - Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices Workaround: