We follow Xavier AGX B03 schematic do a new board ,but it need to remove C543 4.7uF , the CARRIER_PWR_ON can be work, then the 3.3V and 1.8V is normal, but it still not signal at UART3_TX_DEBUG , we just change transistor
TWO PCS have debug message, but the same as the previous board
[image]
Please help to confirm fail at what device - Jetson & Embedded Systems / Jetson AGX Xavier - NVIDIA Developer Forums
Not sure about this. C543 is just a delay cap for switch mosfet. You can use oscilloscope to check signals before transistor to make sure if any output on UART3.
TWO PCS no debug message so no UART3 ,but the others two pcs has debug fail same as the previous board
Please help to confirm fail at what device - Jetson & Embedded Systems / Jetson AGX Xavier - NVIDIA Developer Forums
I guess it may be related to the sequence of these three signals SYS_VIN_HV,
SYS_VIN_MV,
VIN_PWR_BAD_N
But I can’t find the required interval in DATA SHEET
hello Tony_Li,
could you please confirm you’re using updated board configuration file to flash the target?
what’s the error messages shown, please collect them as single text file and attach to the thread for reference.
thanks
Hi Jerry,
What is the board configuration file ?
We use sdk manager to program Xavier module(32GB) with our EV board(version2),
I list our flash environment below
1.OS Ubuntu 16.04 x86_64
2.Kernel : 4.15.0-46-generic
3.SDK Manager : 1.6.0.8170
3.1. Jetson AGX Xavier modules
3.2. JetPack4.5.1
3.3. DeepStream 5.1
3.4. From the log, program by “flash.sh jetson-agx-xavier-devkit mmcblk0p1”
4.Carrier board : our EV2 board
5.Xavier module : Jetson AGX Xavier P2888-0004 (32 GB)
The last message from /dev/ttyUSB3 is “tag initialized”
For more detail log messages, please check the putty.log which is from /dev/ttyUSB3, and the zip file which is exported from sdk manager, thanks.
putty.log (9.4 KB)
SDKM_logs_JetPack_4.5.1_Linux_for_Jetson_AGX_Xavier_2021-07-08_14-56-36.zip (144.4 KB)
hello jb035.cheng,
sdkmanager only works with developer kits.
if your board schematic differs from that for Jetson AGX Xavier Developer Kit board, you must change the pinmux configuration applied by the software.
thanks
Our board Pin config is the same as the Xavier AGX B03 schematic, it is still must change the pinmux configuration or not request
Our Developer Kit board is B02
IS CYPD4226 need to download FW
Is there other IC that need to be updated? Except for CYPD4226 and MCU,
I have tried C543 and C66 use 1uF, the power on sequence is similar to the develop kit, but it is still stop at tag initialized , the next steps should be
emc initialized
clk_dt initialized
avfs_ccplex_platform initialized
tj_max: dt node not found
tj_init initialized
uphy_mrq_init: mrq handler registered
uphy_dt initialized
uphy initialized
we need help, we make two board (the second board all pindefine is same as B03) , but it is always stop at tag initialized
IF must change the pinmux configuration applied by the software ，can you give me the step by step SOP ,we don’t know how to do this ,at tx2 it isn’t need to do this and Taiwan Agent say they make the other board not request to do this, we need help, we make two board ,but it is always stop at tag initialized, we don’t confirm fail at software or hardware, please help us to solve this issue, do you have Remove PD controller schematic can be share ,we don’t sure this issue about PD or not
U5 or U54 need to download code or not
what about DVFS , I see the entries in the EMC DVFS table
Please reply me ,U5 or U54 need to download code or not
That’s the USB-C control circuit. Given that the flashing process uses the USB-C connector, I think that’s a fair bet that it’s needed …
I suggest that you try to flash your module on the original devkit. If that works, you know the module and flashing procedure is good.
Once you’ve done that, you can analyze which bits are used by the flashing process (mainly, USB C, power rails, Ethernet adapter, I think? but you should actually trace through all the process yourself!) and make sure that all of those bits are on your board.
One good way to test this theory, is to simply desolder the component you think won’t be needed from the original devkit board, and see if it will still work with flashing. If it doesn’t, the component was necessary!
You might want two devkit boards, one for desoldering, and one pristine that you can use for recovery when you get to the “doesn’t work” part.
The company should not allow me to dismantle the development kit， maybe I will be fired，I hate NVIDIA
If your company expects you to do engineering, but doesn’t give you the necessary equipment and resources to do the engineering, then I don’t understand how the company expects to ship a working product. Magic?