FAQ
- M051 Base Series(95)
- M0518 Series(97)
- M0519 Series(43)
- M0564 Series(1)
- Mini51 Base Series(90)
- Nano100/102 Base Series(101)
- Nano103 Base Series(10)
- Nano110/112 LCD Series(100)
- Nano120 USB Series(111)
- Nano130 Advanced Series(110)
- NUC029 Series(94)
- NUC100/200 Advanced Series(102)
- NUC120/122/123/220 USB Series(116)
- NUC121/125 Series(1)
- NUC126 USB Series(2)
- NUC130/230 CAN Series(103)
- NUC131/NUC1311 CAN Series(98)
- NUC140/240 Connectivity Series(114)
- M451 Base Series(118)
- M451M Series(117)
- M452 USB Series(130)
- M4521 USB Series(1)
- M453 CAN Series(128)
- M463 CAN FD/USB HS Series(1)
- M467 Ethernet/Crypto Series(1)
- M471 Series(1)
- M479 Motor Control Series(1)
- M481 Base Series(4)
- M482 USB FS OTG Series(4)
- M483 CAN Series(4)
- M484 USB HS OTG Series(4)
- M485 Crypto Series(4)
- M487 Ethernet Series(4)
- M4TK Touch Key Series(25)
- NUC442/472 Series(130)
- NUC472 Series(1)
- NUC505 Series(138)
FAQ
Why SPIM can be executed in debug mode, but cannot be executed in free run mode when the NUC505 SPIM is used? Issue Date:2018-01-16
The NUC505 uses the SPIM function to interface with the internal SPI Flash. Therefore, the SPIM function must be placed in the SRAM before it can be executed.
Since the SPIM sample code in the NUC505 BSP has the Initialization file being set, the code is executed on the SRAM in debug mode, as shown in the red triangle below, so that it can be executed normally. If a user wants to execute the SPIM function in the free run mode, the code must be put into SRAM before it can be executed. Please see MainOnSRAM sample code for how to put the code into SRAM, which is located in the following path: NUC505BSPV3.02.000\SampleCode\BootTemplate\MainOnSRAM
Products: | Microcontrollers ,Arm Cortex-M4 MCUs ,NUC505 Series |
---|---|
Applications: | |
Function: | Peripherals,Memory,SRAM |