RW612-GPIO Pin Conflicts

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

RW612-GPIO Pin Conflicts

1,758 Views
wima88
Contributor III
Hello,

While running the SCTimer example, I noticed some duplicated GPIOs in the quick start guide:

Connector Pin # GPIO #
J2452
J4552
J543
J133

It appears that for the example, J5 pin 4 should correctly correspond to GPIO 3. Is there a resource where I can find the accurate pinout information?

Labels (1)
Tags (1)
0 Kudos
Reply
3 Replies

977 Views
AndrewChuang
Contributor I

They are not conflicted -- one is for GPIO_2_FC0_I2S_DATA and the other is for GPIO_2_FC0_UART_RXD_ME, as shown in the FRDM-RW612-SCH.pdf. Thanks to your post, I spotted the difference. I've spent almost a week trying to figure out why my usart had no output... 

0 Kudos
Reply

1,674 Views
wima88
Contributor III

Yes

0 Kudos
Reply

1,733 Views
DanielRuvalcaba
NXP TechSupport
NXP TechSupport

Hi,

Are you using the FRDM-RW612?

Regards,

Daniel.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-1992113%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERW612-GPIO%20Pin%20Conflicts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992113%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CSPAN%3EHello%2C%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CP%3EWhile%20running%20the%20SCTimer%20example%2C%20I%20noticed%20some%20duplicated%20GPIOs%20in%20the%20quick%20start%20guide%3A%3C%2FP%3EConnector%20Pin%20%23%20GPIO%20%23%20%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EJ2%3C%2FTD%3E%3CTD%3E4%3C%2FTD%3E%3CTD%3E52%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EJ4%3C%2FTD%3E%3CTD%3E5%3C%2FTD%3E%3CTD%3E52%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EJ5%3C%2FTD%3E%3CTD%3E4%3C%2FTD%3E%3CTD%3E3%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EJ1%3C%2FTD%3E%3CTD%3E3%3C%2FTD%3E%3CTD%3E3%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3EIt%20appears%20that%20for%20the%20example%2C%20J5%20pin%204%20should%20correctly%20correspond%20to%20GPIO%203.%20Is%20there%20a%20resource%20where%20I%20can%20find%20the%20accurate%20pinout%20information%3F%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1992113%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EEvaluation%20Board%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2151475%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20RW612-GPIO%20Pin%20Conflicts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2151475%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EThey%20are%20not%20conflicted%20--%20one%20is%20for%26nbsp%3BGPIO_2_FC0_I2S_DATA%20and%20the%20other%20is%20for%26nbsp%3BGPIO_2_FC0_UART_RXD_ME%2C%20as%20shown%20in%20the%20FRDM-RW612-SCH.pdf.%20Thanks%20to%20your%20post%2C%20I%20spotted%20the%20difference.%20I've%20spent%20almost%20a%20week%20trying%20to%20figure%20out%20why%20my%20usart%20had%20no%20output...%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1997436%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20RW612-GPIO%20Pin%20Conflicts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1997436%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EYes%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1992236%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20RW612-GPIO%20Pin%20Conflicts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992236%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EAre%20you%20using%20the%20FRDM-RW612%3F%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3C%2FP%3E%0A%3CP%3EDaniel.%3C%2FP%3E%3C%2FLINGO-BODY%3E