Home/Support/Support Forum/XCTU vs API pin configuration

XCTU vs API pin configuration

0 votes
I just want to make sure I'm doing this correctly. Let's say I am programming the S3B 900HP Pro, Programmable version, and am using CodeWarrior/SDK to deploy code to it. Here's my pinout:

* XPIN1 = VCC
* XPIN2 = uart0 [TX Pin]
* XPIN3 = uart0 [RX Pin]
* XPIN4 = <<UNUSED>>
* XPIN5 = special0 [Reset Pin]
* XPIN6 = ord_1 [GPIO Pin]
* XPIN7 = <<UNUSED>>
* XPIN8 = special0 [BKGD Pin]
* XPIN9 = <<UNUSED>>
* XPIN10 = GND
* XPIN11 = <<UNUSED>>
* XPIN12 = <<UNUSED>>
* XPIN13 = <<UNUSED>>
* XPIN14 = VCC REF
* XPIN15 = special0 [Association Pin]
* XPIN16 = <<UNUSED>>
* XPIN17 = <<UNUSED>>
* XPIN18 = ord_ai1
* XPIN19 = <<UNUSED>>
* XPIN20 = <<UNUSED>>

What should this look like if I decide to open it up in XCTU and configure it some? Does how it look in XCTU even matter if I always intend to run it in API mode using the code I deploy?

If it does matter, are they usually configured as pull-ups for RTS/CTS/DIN/DOUT/DTR?

Thanks
asked Jul 27 in DigiMesh Proprietary Mesh Networking by D2K New to the Community (10 points)

Please log in or register to answer this question.

1 Answer

0 votes
The pins will be the same connection to talk to XCTU. You just needs to understand the XCTU will want to talk to the RF processor via the FreeScale processor.

Even if you want to interface with the API, be it from an external processor, XCTU or the internal processor, API mode would have to be enabled.
answered Jul 27 by mvut Veteran of the Digi Community (12,791 points)
...