This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| faq [2020/12/21 20:10] – [Questions Related to the Development Environment] ursgraf | faq [2022/11/24 16:30] (current) – [Questions Related to the Development Environment] ursgraf | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ===== Questions Related to the Development Environment ===== | ===== Questions Related to the Development Environment ===== | ||
| <box 100% | **Question: | <box 100% | **Question: | ||
| - | Press the button " | + | Press the button " |
| </ | </ | ||
| Line 28: | Line 28: | ||
| </ | </ | ||
| - | <box 100% | **Question: | + | <box 100% | **Question: |
| - | This can have several causes. At boot time, the code section is checked for proper content. If this check fails, the LED starts blinking and the program execution stops. \\ | + | This can have several causes, see [[runtime_library: |
| - | Later on when a stack check fails, the LED blinks with a different blink pattern. The blinking can also indicate that a java exception | + | Later on when a stack check fails, the LED blinks with a different blink pattern. The blinking can also indicate that a java exception |
| </ | </ | ||
| Line 37: | Line 37: | ||
| </ | </ | ||
| - | <box 100% | **Question: | + | <box 100% | **Question: |
| The inputs Int5, Int6 and Int7 must not be tied to Gnd at startup. If so, the processor will choose a wrong mode and the PLL cannot lock. Debugging is possible, but the processor runs in limp mode. | The inputs Int5, Int6 and Int7 must not be tied to Gnd at startup. If so, the processor will choose a wrong mode and the PLL cannot lock. Debugging is possible, but the processor runs in limp mode. | ||
| </ | </ | ||