Download PDF version of this document.
The Trenz Electronic TE0813 is an industrial grade MPSoC SOM integrating an AMD ZynqTM UltraScale+TM, DDR4 SDRAM with 64-Bit width data bus connection, SPI Boot Flash memory for configuration and operation, transceivers and powerful switch-mode power supplies for all on-board voltages. A large number of configurable I/Os is provided via rugged high-speed stacking connections in a compact 5.2 cm x 7.6 cm form factor.
Refer to http://trenz.org/te0813-info for the current online version of this manual and other available documentation.
up to 204 PL IO
up to 65 PS MIO
Storage device name | Content | Notes |
---|---|---|
DDR4 SDRAM | not programmed | |
Quad SPI Flash | not programmed | |
EEPROM | not programmed besides factory programmed MAC address | |
Programmable Clock Generator | not programmed |
Connector Type | Designator | Interface | IO CNT 1) | Notes |
---|---|---|---|---|
B2B | JM1 | MGT PL | 4 x MGT (RX/TX) | |
B2B | JM1 | HP | 52 SE / 24 DIFF | |
B2B | JM2 | MGT PS | 2 x MGT CLK | |
B2B | JM2 | MGT PS | 4 x MGT (RX/TX) | |
B2B | JM2 | CFG | JTAG | |
B2B | JM2 | CFG | I2C | |
B2B | JM2 | CFG | MODE | |
B2B | JM3 | HD | 48 SE / 24 DIFF | |
B2B | JM3 | MGT PL | MGT CLK | |
B2B | JM3 | MIO | 65 GPIO | |
B2B | JM4 | HP | 104 SE / 48 DIFF |
1) IO CNT depends on assembly variant. E.g. the MGTs are not available for all FPGAs
Test Point | Signal | Notes1) |
---|---|---|
TP1 | PLL_SCL | pulled-up to PS_1V8 |
TP2 | PLL_SDA | pulled-up to PS_1V8 |
TP3 | DDR4-TEN | pulled-down to GND |
TP4 | DCDC_2V0 | |
TP5 | GND | |
TP6 | PL_1V8 | |
TP7 | GND | |
TP8 | GND | |
TP9 | PL_VCCINT_IO | |
TP10 | GND | |
TP11 | PL_VCCINT | |
TP12 | PL_VCU_0V9 | |
TP13 | FP_0V85 | |
TP14 | PS_1V8 | |
TP15 | GND | |
TP16 | DDR_2V5 | |
TP17 | DDR_PLL | |
TP18 | DDR_1V2 | |
TP19 | PS_GT_1V0 | |
TP20 | MGTAVTT | |
TP21 | VTT | |
TP22 | PL_GT_1V15 | was PL_GT_1V05 in REV01. |
TP23 | VREFA | |
TP24 | MGTVCCAUX | |
TP25 | MGTAVCC | |
TP26 | PL_GT_1V45 | |
TP27 | PS_PLL | |
TP28 | PS_AVTT | |
TP29 | LP_0V85 | |
TP30 | PS_AUX | |
TP31 | PS_AVCC | |
TP34 | POR_B | pulled-up to PS_1V8 |
1) Direction:
Chip/Interface | Designator | Connected To | Notes |
---|---|---|---|
DDR4 SDRAM | U2, U3, U9, U12 | SoC - PS | |
Quad SPI Flash | U7, U17 | SoC - PS | Booting. |
EEPROM | U28 | B2B - J2 | MAC address |
Clock Generator | U5 | SoC, B2B | |
Oscillator | U6 | Clock Generator | 25 MHz |
Oscillator | U32 | SoC | 33.333333 MHz |
Connector+Pin | Signal Name | Direction1) | Description |
---|---|---|---|
JM1.A45 | POR_OVERRIDE | IN | Override power-on reset delay 2). |
JM2.A31 | ERR_OUT | OUT | PS error indication 2). |
JM2.A34 | ERR_STATUS | OUT | PS error status 2). |
JM2.A35 | LP_GOOD | OUT | Low-power domain powered-up. Pulled up to 3.3VIN |
JM2.A36 | PLL_SCL | IN | I2C clock |
JM2.A37 | PLL_SDA | IN/OUT | I2C data |
JM2.A40 | PG_VCU | OUT | Programmable logic powered-up. |
JM2.A41 | EN_PSGT | IN | Enable GTR transceiver power-up. |
JM2.A44 / JM2.A45 / JM2.A46 / JM2.A47 | TCK / TDI / TDO / TMS | Signal-dependent | JTAG configuration and debugging interface. JTAG reference voltage: PS_1V8 |
JM2.B29 | PG_PSGT | OUT | GTR transceivers powered-up. |
JM2.B30 | PROG_B | IN/OUT | Power-on reset 2). Pulled-up to PS_1V8. |
JM2.B33 | SRST_B | IN | System reset 2). Pulled-up to PS_1V8. |
JM2.B34 | INIT_B | IN/OUT | Initialization completion indicator after POR 2). Pulled-up to PS_1V8. |
JM2.B37 | PG_PL | OUT | VCU powered-up. |
JM2.B38 | EN_FPD | IN | Enable full-power domain power-up. |
JM2.B41 | PG_FPD | OUT | Full-power domain powered-up. |
JM2.B42 | EN_LPD | IN | Enable low-power domain power-up. |
JM2.B45 | PG_DDR | OUT | DDR power supply powered-up. |
JM2.B46 | DONE | OUT | PS done signal 2). Pulled-up to PS_1V8. |
JM2.B47 | EN_DDR | IN | Enable DDR power-up. |
JM2.C31 | MR | IN | Manual reset. |
JM2.C35 | EN_PL | IN | Enable programable logic power-up. |
JM2.C36 | EN_GT_R | IN | Enable GTH/GTY transceiver power-up. |
JM2.C44 / JM2.C45 / JM2.C46 / JM2.C47 | MODE3..0 | IN | Boot mode selection 2):
Supported Modes depends also on used Carrier. |
JM2.D33 | PG_GT_R | OUT | GTH/GTY Transceivers powered-up. |
JM2.D37 | PSBATT | IN | PS RTC Battery supply voltage 2) 3). |
JM2.D38 | PUDC_B | IN | Enable/Disable internal pull-ups during configuration on all SelectIO pins. |
JM2.D45 / JM2.D46 | DX_P / DX_N | - | SoC temperatur sensing diode pins 2). |
1) Direction:
2) See UG1085 for additional information.
3) See Recommended Operating Conditions.
Power Rail Name/ Schematic Name | Connector.Pin | Direction1) | Notes |
---|---|---|---|
VCCO_66 | JM1.A32 / JM1.A33 | IN | |
VREF_66 | JM1.A41 | IN | |
3.3VIN | JM1.A54 / JM1.A55 / JM1.B55 / JM1.B56 | IN | |
PL_1V8 | JM1.C32 / JM1.C33 / JM1.D33 / JM1.D34 | OUT | |
PL_DCIN | JM1.C56 / JM1.C57 / JM1.C58 / JM1.C59 / JM1.C60 / JM1.D56 / JM1.D57 / JM1.D58 / JM1.D59 / JM1.D60 | IN | |
LP_DCDC | JM2.A50 / JM2.A51 / JM2.A52 / JM2.B50 / JM2.B51 / JM2.B52 / JM2.C50 / JM2.C51 / JM2.C52 / JM2.D50 / JM2.D51 / JM2.D52 | IN | |
DCDCIN | JM2.A57 / JM2.A58 / JM2.A59 / JM2.A60 / JM2.B57 / JM2.B58 / JM2.B59 / JM2.B60 / JM2.C57 / JM2.C58 / JM2.C59 / JM2.C60 / JM2.D57 / JM2.D58 / JM2.D59 / JM2.D60 / | IN | |
PS_BATT | JM2.D37 | IN | |
DDR_1V2 | JM2.D47 | OUT | |
PS_1V8 | JM2.C34 / JM2.D34 / JM3.A56 / JM3.B56 / JM3.C56 / JM3.D56 | OUT | |
GT_DCDC | JM3.A59 / JM3.A60 / JM3.B59 / JM3.B60 / JM3.C59 / JM3.C60 / JM3.D59 / JM3.D60 / | IN | |
VCCO_25 | JM3.C7 / JM3.C8 / JM3.D8 / JM3.D9 | IN | |
VCCO_26 | JM3.C19 / JM3.C20 / JM3.D20 / JM3.D21 | IN | |
VCCO_64 | JM4.B21 / JM4.B39 | IN | |
VREF_64 | JM4.B30 | IN | |
VCCO_65 | JM4.C21 / JM4.C39 | IN | |
VREF_65 | JM4.C30 | IN |
1) Direction:
The power up sequencing highly depends on the use case. In general, it should be possible to enable/disable the processing system (PS) / programmable logic (PL) independently. Furthermore, within the processing logic it should be possible to enable/disable only low-power domain and/or low-power and full-power domain. Additionally, usage of GTR for PS side and GTH/GTY for PL side should be possible. Because of this flexibility the needed parts of the following table needs to be selected individually. For detailed information take a look into schematics.
Sequence | Net name | Recommended Voltage Range | Pull-up/down | Description | Notes |
---|---|---|---|---|---|
0 | - | - | - | Configuration signal setup. | See Configuration and System Control Signals. |
1 1) | PSBATT | 1.2 V ... 1.5 V | - | Battery connection. | Battery Power Domain usage. When not used, tie to GND. |
1 2) | 3.3VIN | 3.3 V (± 5 %) | - | Management power supply. | Management module power supply. 0.5 A recommended. Consider note 2) for modules with VCU and/or low-power SoC. |
2 | Processing System (PS): | Procedure for PS starting. | |||
2.1 | Low-power domain: | Bring-up for low-power domain PS. | |||
2.1.1 | LP_DCDC | 3.3 V (± 3 %) 3) | - | Low-power domain power supply. | Main module power supply for low-power domain. 5.5 A recommended. Power consumption depends mainly on design and cooling solution. |
2.1.2 | EN_LPD | - | PU 4), 3.3 V | Low-power domain power enable. | |
2.1.3 | LP_GOOD | - | PU 4), 3.3 V | Low-power domain power good status. | Module power-on sequencing for low-power domain finished. |
2.2 | Full-power domain: | Bring-up for full-power domain PS. | Full-power PS domain needs powered low-power PS domain. | ||
2.2.1 | DCDCIN | 3.3 V (± 5 %) 3) | Full-power domain and GTR transceiver power supply. | Main module power supply for full-power domain. 7 A recommended. Power consumption depends mainly on design and cooling solution. | |
2.2.2 | EN_FPD | 3.3 V | - | Full-power domain power enable. | |
2.2.3 | PG_FPD | - | PU 4), 3.3 V | Full-power domain power good status. | Module power-on sequencing for full-power domain finished. |
2.2.4 | EN_DDR | 3.3 V | - | DDR memory power enable. | |
2.2.5 | PG_DDR | PU 4), 3.3 V | DDR memory power good status. | Module power-on sequencing for DDR memory finished. | |
2.3 | GTR Transceiver | Procedure for GTR transceiver starting. | PS transceiver usage needs powered PS (low- and full-power domain). | ||
2.3.1 | EN_PSGT | 3.3 V | - | GTR transceiver power enable. | |
2.3.2 | PG_PSGT | - | PU 4), 3.3 V | GTR transceiver power good status. | Module power-on sequencing for GTR transceiver finished. |
2 | Programmable Logic (PL) | Procedure for PL starting. | PS and PL can be started independently. | ||
2.1 | PL_DCIN | 3.3 V (± 5 %) 3) 5) | - | Programmable logic power supply. | Main module power supply for programmable logic. 12 A recommended. Power consumption depends mainly on design and cooling solution. |
2.2 | EN_PL | - | PU 4), 3.3 V | Programmable logic power enable. | |
2.3 | PG_PL | - | PU 4), 3.3 V | Programmable logic power good status. | Module power-on sequencing for programmable logic finished. Periphery and variable bank voltages can be enabled on carrier. |
2.4 | VCCO_25 / VCCO_26 / VCCO_64 / VCCO_65 / VCCO_66 | 6) | - | Module bank voltages. | Enable bank voltages after PG_PL deassertion. |
2.5 | PG_VCU | - | PU 4), 3.3 V | VCU power good status. | |
3 | GTH / GTY Transceiver | Procedure for GTH / GTY transceiver starting. | PL transceiver usage needs powered PL and low-power PS domain. | ||
3.1 | GT_DCDC | 3.3 V (± 3 %) 3) | - | GTH / GTY transceiver power supply. | Main module power supply for GTH / GTY transceiver. 3 A recommended. Power consumption depends mainly on design and cooling solution. |
3.2 | EN_GT_R | 3.3 V | - | GTH / GTY transceiver power enable. | |
3.3 | PG_GT_R | - | PU 4), 3.3 V | GTH / GTY transceiver power good status. |
1) (optional)
2) On TE0813 REV01 boards it is necessary for modules with VCU and/or low-power speedgrade to either connect signal EN_PL to voltage 3.3VIN or to enable EN_PL together with 3.3VIN. This should be changed in a newer revision.
3) Dependent on the assembly option a higher input voltage may be possible.
4) (on module)
5) This value depends highly on DCDC U4. Higher values may be possible with different DCDCs. For more information consult schematic and according datasheets.
6) See DS925 for additional information.
5.2 x 7.6 cm UltraSoM+ carrier use four Samtec AcceleRate HD High-Density Slim Body Arrays on top side.
When using the standard type on baseboard and module, the mating height is 5 mm.
Other mating heights are possible by using connectors with a different height:
Order number | REF number | Samtec Number | Type | Contribution to stacking height | Comment |
---|---|---|---|---|---|
30095 | REF-30095 | ADM6-60-01.5-L-4-2 | Module connector | 1.5 mm | Standard connector used on modules |
31137 | REF-31137 | ADF6-60-03.5-L-4-2 | Baseboard connector | 3.5 mm | Standard connector used on carrier |
The AcceleRate HD High-Density connector speed rating depends on the stacking height; please see the following table:
Stacking height | Speed rating |
---|---|
5 mm | 56 Gbps |
Current rating of Samtec AcceleRate HD High-Density B2B connectors is 1.34 A per pin (4 pins powered)
File | Modified | |
---|---|---|
PDF File 20200225_hsc_adm6-xx-01p5-xxx-4-a_adf6-xx-03p5-xxx-4-a.pdf | 10 01, 2022 by Martin Rohrmüller | |
Labels
|
||
PDF File adf6.pdf | 10 01, 2022 by Martin Rohrmüller | |
Labels
|
||
PDF File ADF6-XXX-XX.X-XXX-X-X-X-FOOTPRINT.PDF | 10 01, 2022 by Martin Rohrmüller | |
Labels
|
||
PDF File adf6-xxx-xx.x-xxx-x-x-x-xr-mkt.pdf | 10 01, 2022 by Martin Rohrmüller | |
Labels
|
||
PDF File adx6 mated document.pdf | 10 01, 2022 by Martin Rohrmüller | |
Labels
|
Power Rail Name/ Schematic Name | Description | Min | Max | Unit |
---|---|---|---|---|
LP_DCDC | Micromodule Power | -0.300 | 6.0 | V |
DCDCIN | Micromodule Power | -0.300 | 7.0 | V |
GT_DCDC | Micromodule Power | -0.300 | 6.0 | V |
PL_DCIN 1) | Micromodule Power | -0.300 | 4.5 | V |
3.3VIN | Micromodule Power | -0.300 | 3.600 | V |
PS_BATT | RTC / BBRAM | -0.500 | 2.000 | V |
VCCO_25 | HD IO Bank power supply | -0.500 | 3.400 | V |
VCCO_26 | HD IO Bank power supply | -0.500 | 3.400 | V |
VCCO_64 | HP IO Bank power supply | -0.500 | 2.000 | V |
VCCO_65 | HP IO Bank power supply | -0.500 | 2.000 | V |
VCCO_66 | HP IO Bank power supply | -0.500 | 2.000 | V |
VREF_64 | Bank input reference voltage | -0.500 | 2.000 | V |
VREF_65 | Bank input reference voltage | -0.500 | 2.000 | V |
VREF_66 | Bank input reference voltage | -0.500 | 2.000 | V |
1) This value depends on DCDC U4 circuit. If resistor R133 is fitted and R132 is not fitted (default) 7.0 V is allowed. If resistor R133 is not fitted and R132 is fitted only 4.5 V is allowed. For more information consult schematic and according datasheets.
*) Stresses beyond those listed under Absolute Maximum Ratings may cause permanent damage to the device. These are stress ratings only, which do not imply functional operation of the device at these
or any other conditions beyond those indicated under Recommended Operating Condition. Exposure to absolute-maximum rated conditions for extended periods may affect device reliability.
This TRM is generic for all variants. Temperature range can be different depending on assembly version. Voltage range is mostly the same during variants (exceptions are possible, depending on custom request)
Operating temperature range depends also on customer design and cooling solution. Please contact us for options.
Parameter | Min | Max | Units | Reference Document |
---|---|---|---|---|
LP_DCDC 1) | 3.201 | 3.399 | V | |
DCDCIN 1) | 3.135 | 3.465 | V | |
GT_DCDC 1) | 3.201 | 3.399 | V | |
PL_DCIN 1) 2) 3) | 3.135 | 3.465 | V | |
3.3VIN | 3.135 | 3.465 | V | |
PS_BATT | 1.2 | 1.5 | V | See FPGA datasheet. |
VCCO_25 | 1.140 | 3.400 | V | See FPGA datasheet. |
VCCO_26 | 1.140 | 3.400 | V | See FPGA datasheet. |
VCCO_64 | 0.95 | 1.900 | V | See FPGA datasheet. |
VCCO_65 | 0.95 | 1.900 | V | See FPGA datasheet. |
VCCO_66 | 0.95 | 1.900 | V | See FPGA datasheet. |
VREF_64 | 0.6 | 1.2 | V | See FPGA datasheet. |
VREF_65 | 0.6 | 1.2 | V | See FPGA datasheet. |
VREF_66 | 0.6 | 1.2 | V | See FPGA datasheet. |
1) Dependent on the assembly option a higher input voltage may be possible.
2) This value depends on DCDC U4 circuit. If resistor R133 is fitted and R132 is not fitted (default) 7.0 V are allowed. If resistor R133 is not fitted and R132 is fitted only 4.5 V are allowed. For more information consult schematic and according datasheets.
3) For U4 either TPS548A28RWWR or MPQ8633BGLE-Z is assembled which is up to Trenz Electronic GmbH.
Module size: 76 mm × 52 mm. Please download the assembly diagram for exact numbers.
Mating height with standard connectors: 5 mm.
PCB thickness: 1.74 mm (± 10 %).
Trenz shop TE0813 overview page | |
---|---|
English page | German page |
Date | Revision | Changes | Documentation Link |
---|---|---|---|
- | REV02 |
| REV02 |
- | REV01 | First Production Release | REV01 |
Hardware revision number can be found on the PCB board together with the module model number separated by the dash.
Date | Revision | Contributor | Description |
---|---|---|---|
Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] | Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] | Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] |
|
2023-03-02 | v.43 | Martin Rohrmüller |
|
2023-01-16 | v.41 | ED |
|
2023-01-13 | v.39 | ED |
|
-- | all | Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] |
|
Please also note our data protection declaration at https://www.trenz-electronic.de/en/Data-protection-Privacy
The material contained in this document is provided “as is” and is subject to being changed at any time without notice. Trenz Electronic does not warrant the accuracy and completeness of the materials in this document. Further, to the maximum extent permitted by applicable law, Trenz Electronic disclaims all warranties, either express or implied, with regard to this document and any information contained herein, including but not limited to the implied warranties of merchantability, fitness for a particular purpose or non infringement of intellectual property. Trenz Electronic shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein.
In no event will Trenz Electronic, its suppliers, or other third parties mentioned in this document be liable for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) arising out of the use, inability to use, or the results of use of this document, any documents linked to this document, or the materials or information contained at any or all such documents. If your use of the materials or information from this document results in the need for servicing, repair or correction of equipment or data, you assume all costs thereof.
No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Trenz Electronic.
The hardware / firmware / software described in this document are furnished under a license and may be used /modified / copied only in accordance with the terms of such license.
To confront directly with the responsibility toward the environment, the global community and eventually also oneself. Such a resolution should be integral part not only of everybody's life. Also enterprises shall be conscious of their social responsibility and contribute to the preservation of our common living space. That is why Trenz Electronic invests in the protection of our Environment.
REACH
Trenz Electronic is a manufacturer and a distributor of electronic products. It is therefore a so called downstream user in the sense of REACH. The products we supply to you are solely non-chemical products (goods). Moreover and under normal and reasonably foreseeable circumstances of application, the goods supplied to you shall not release any substance. For that, Trenz Electronic is obliged to neither register nor to provide safety data sheet. According to present knowledge and to best of our knowledge, no SVHC (Substances of Very High Concern) on the Candidate List are contained in our products. Furthermore, we will immediately and unsolicited inform our customers in compliance with REACH - Article 33 if any substance present in our goods (above a concentration of 0,1 % weight by weight) will be classified as SVHC by the European Chemicals Agency (ECHA).
RoHS
Trenz Electronic GmbH herewith declares that all its products are developed, manufactured and distributed RoHS compliant.
WEEE
Information for users within the European Union in accordance with Directive 2002/96/EC of the European Parliament and of the Council of 27 January 2003 on waste electrical and electronic equipment (WEEE).
Users of electrical and electronic equipment in private households are required not to dispose of waste electrical and electronic equipment as unsorted municipal waste and to collect such waste electrical and electronic equipment separately. By the 13 August 2005, Member States shall have ensured that systems are set up allowing final holders and distributors to return waste electrical and electronic equipment at least free of charge. Member States shall ensure the availability and accessibility of the necessary collection facilities. Separate collection is the precondition to ensure specific treatment and recycling of waste electrical and electronic equipment and is necessary to achieve the chosen level of protection of human health and the environment in the European Union. Consumers have to actively contribute to the success of such collection and the return of waste electrical and electronic equipment. Presence of hazardous substances in electrical and electronic equipment results in potential effects on the environment and human health. The symbol consisting of the crossed-out wheeled bin indicates separate collection for waste electrical and electronic equipment.
Trenz Electronic is registered under WEEE-Reg.-Nr. DE97922676.
Error rendering macro 'page-info'
Ambiguous method overloading for method jdk.proxy244.$Proxy3578#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]