#160 Conflicting GCLK0 is used for LSE tests

クローズ
Michael Schloh von Bennewitz4年前に作成 · 2件のコメント

Conflicting GCLK0 is used for LSE tests

Problem environment

A MCU GPIO pin is used to output the LSE crystal frequency to the GCLK0 timer, which is used by default to set the general controller speed.

Steps to reproduce

  1. Refer to the schematic
  2. Refer to the MCU datasheet
  3. Locate documentation regarding clock output

Expected result

A MCU GPIO pin is chosen and routed according to the ability to duplicate the LSE frewquency output to a timer other than GCLK0.

Actual result

The LSE frequency output is duplicated to a MCU GPIO pin that is only able to use the GCLK0 timer circuit.

Workaround

Reprogram the I²C data pin to carry the LSE frequency crystal's output signal, and remove the pull up resistor and other parts connected to the I²C data pin. Measure LSE output at the new hacked pin circuit, after programming the chip to route the signal to GCLK3.

Severity level

This is low priority because crystal tuning and clock hacking are not one of the use cases supported.

# Conflicting GCLK0 is used for LSE tests ## Problem environment A MCU GPIO pin is used to output the LSE crystal frequency to the GCLK0 timer, which is used by default to set the general controller speed. ## Steps to reproduce 1. Refer to the schematic 1. Refer to the MCU datasheet 1. Locate documentation regarding clock output ## Expected result A MCU GPIO pin is chosen and routed according to the ability to duplicate the LSE frewquency output to a timer other than GCLK0. ## Actual result The LSE frequency output is duplicated to a MCU GPIO pin that is only able to use the GCLK0 timer circuit. ## Workaround Reprogram the I²C data pin to carry the LSE frequency crystal's output signal, and remove the pull up resistor and other parts connected to the I²C data pin. Measure LSE output at the new hacked pin circuit, after programming the chip to route the signal to GCLK3. ## Severity level This is **low priority** because crystal tuning and clock hacking are not one of the use cases supported.
Michael Schloh von Bennewitz がラベル
enhancement
を追加 4年前
Michael Schloh von Bennewitz がラベル
help wanted
を追加 4年前
Michael Schloh von Bennewitz がマイルストーン Final schematic and layout design に追加 4年前
Michael Schloh von Bennewitz4年前 にコメント
オーナー
Pin Clock-ID I/O In-use
G8 GCLK_IO[1] PA15 CRYOUT
F7 GCLK_IO[2] PA16 I²C-SDA
E6 GCLK_IO[3] PA17 I²C-SCL
D8 GCLK_IO[6] PA22 202101
D7 GCLK_IO[7] PA23 No
C7 GCLK_IO[1] PB23 No
E5 GCLK_IO[0] PB22 202012

All other GCLK compatible pins support GCLK_IO[0] only, according to the SAM R34/R35 datasheet page 14.

| Pin | Clock-ID | I/O | In-use | | ---- | ---- | ---- | ---- | | G8 | GCLK_IO[1] | PA15 | CRYOUT | | F7 | GCLK_IO[2] | PA16 | I²C-SDA | | E6 | GCLK_IO[3] | PA17 | I²C-SCL | | D8 | GCLK_IO[6] | PA22 | 202101 | | D7 | GCLK_IO[7] | PA23 | No | | C7 | GCLK_IO[1] | PB23 | No | | E5 | GCLK_IO[0] | PB22 | 202012 | All other GCLK compatible pins support GCLK_IO[0] only, according to the [SAM R34/R35 datasheet](https://ww1.microchip.com/downloads/en/DeviceDoc/SAM-R34-R35-Low-Power-LoRa-Sub-GHz-SiP-Data-Sheet-DS70005356C.pdf) page 14.
Michael Schloh von Bennewitz4年前 にコメント
オーナー

Solved in fb71af7 by rerouting testpoint TP13 from E5 (PB22/GCLK0) to D8 (PA22/GCLK6) and modifying firmware sample files respectively.

Solved in fb71af7 by rerouting testpoint TP13 from E5 (PB22/GCLK0) to D8 (PA22/GCLK6) and modifying firmware sample files respectively.
サインインしてこの会話に参加。
マイルストーンなし
担当者なし
1 人の参加者
期日

期日は未設定です。

依存関係

この課題に依存関係はありません。

読み込み中…
キャンセル
保存
まだ内容がありません