|
| 1 | +--------------- |
| 2 | +1. Usage Notes |
| 3 | +--------------- |
| 4 | +1.1. This sample project requires r_usb_basic v1.42 and r_usb_hcdc v1.42 as minimum version. |
| 5 | +After project generation, please confirm it as following steps: |
| 6 | + In Smart Configurator editor, go to Components tab |
| 7 | + - If you see r_usb_basic and r_usb_hcdc configuration are blue and can see its settings, |
| 8 | + it is okay, you don't need to do anything. |
| 9 | + - If you see r_usb_basic and r_usb_hcdc configuration are grey off, |
| 10 | + you can select grey component and click on the link to download missing module. |
| 11 | + After downloading completed, click Generate Code button to generate code for it. |
| 12 | + |
| 13 | +1.2. For more information about how to use this sample project, |
| 14 | +please refer to section 2.11 of r01an6455ej0200-rx-azure-rtos.pdf |
| 15 | + |
| 16 | +1.3. To keep 8 bytes size for double type |
| 17 | + "-dbl_size=8" compiler build option is set as default for CC-RX project |
| 18 | + Size of type 'double' is set to "64 bits" as default for IAR project |
| 19 | + "-m64bit-doubles" build option is set as default for GCC project |
| 20 | + |
| 21 | +1.4. Please also take note that the sample project is verified with C project. |
| 22 | +If you create new project with C++ option, please confirm its behavior by yourself. |
| 23 | +For example, if you create project with C++ option and CC-RX compiler, you will need to add abort() function manually. |
| 24 | + |
| 25 | +------------------------ |
| 26 | +2. Caution / Known Issue |
| 27 | +------------------------ |
| 28 | +2.1. When using GCC compiler, in case you set Optimization level as Optimize size(-Os), please set the linker option not to remove unused sections as following |
| 29 | +- in Project Explorer view, right-click on the project and select Properties |
| 30 | +- on Properties dialog select C/C++ Build -> Settings -> Tool Settings tab -> Linker -> Other |
| 31 | +- add "-Wl,--no-gc-sections" on User defined options |
| 32 | +- click Apply and Close" button |
| 33 | + |
| 34 | +2.2. When using GCC compiler, the "_end" section in src/linker_script.ld should be at the end. However, the default linker script may not meet this order, so please check linker_script.ld and move the section below to the end if needed, and build project again |
| 35 | +.bss : |
| 36 | +{ |
| 37 | + _bss = .; |
| 38 | + *(.bss) |
| 39 | + *(.bss.**) |
| 40 | + *(COMMON) |
| 41 | + *(B) |
| 42 | + *(B_1) |
| 43 | + *(B_2) |
| 44 | + _ebss = .; |
| 45 | + _end = .; |
| 46 | +} > RAM |
| 47 | + |
| 48 | +2.3. If you are using RSK board (RSK RX65N, RSK RX671), please do the pin assignment check for USB0_VBUSEN. |
| 49 | +In Smart Configurator editor (<projectname>.scfg) |
| 50 | +- go to Pins tab |
| 51 | +- at Pin Function, select USB0 on the left panel |
| 52 | +- on the right panel, check and change USB0_VBUSEN pin number if it is incorrect (there is a warning icon) |
| 53 | + |
| 54 | +This issue will be fixed at that next update of RSK board description file. |
| 55 | + |
| 56 | +2.4 When using RX microcontrollers with DPFPU |
| 57 | +Target projects (RX72N, RX671): |
| 58 | +- Projects with the double precision floating point instruction generation option (CC-RX: -dpfpu, GCC: --mdfpu=64, IAR: --fpu=64) enabled on RXv3 core devices |
| 59 | +Workaround: |
| 60 | +- Call tx_thread_fpu_enable() at the beginning of every task. |
0 commit comments