Dear Rocky:
1)is it charge automatically at A50 pin use MS621 ?
Hi, are you planning to use MS621 instead of super cap? It is workable, but the current typical charge voltage is 2.5V, you might need to change the output charge voltage to 3V. Please check the datasheet of PMIC (MAX77620) for detail info.
Dear Rocky:
Please support as flow:
1)change the output charge voltage to 3V------is this software set and please support MAX77620 datasheet(Email: wbin12@grgbanking.com)
2)How does USB work in device mode for Jetson TX2, software or hardware, Please introduction
3)There are several ways to start Jetson TX2 in except USB0 for update software, and several ways to start of narmally power-on except eMMC.
Hi, please contact vendor for datasheet. For this kind of general USB design/programming problem, please check the OEM DG and TRM, also you can use search tool to search the USB related topics in forum, there are many similar topics. Such as below ones:
[url]How to set TX2 otg usb as device mode? - Jetson TX2 - NVIDIA Developer Forums
[url]https://devtalk.nvidia.com/default/topic/1001771/jetson-tx2/no-usb-support-on-custom-base-carrier-board/[/url]
Dear Rocky:
Please support as flow;
1）For the USB update program time is too long and it takes more than 30 minutes. It is a big problem in production, and if there are other faster update methods.Can the update time of production be shortened greatly, and there are several modules of TX2 update at the same time?
2)How many milliampere is the normal power consumption current of RTC？
3）Because the peripheral circuit does not monitor the power circuit through the I2C, this will affect the TX2 boot startup. which part of the code needs to be modified？
One consideration is that during a normal flash the rootfs file system is generated via the rootfs subdirectory (plus some boot files copied in based on options). This creates a loopback-mountable system.img.raw which is around 30GB in size. If you already have this file, then you can use the “-r” option to flash.sh to tell it to re-use the existing system.img and not generate a new one each time…this would significantly cut down time.
You can also replace the image with a clone you have updated from a working system. I normally prefer to deal with raw partition images (loopback mountable and editable) and not sparse images (never again to be anything but read-only in a way only Jetson flash understands). You can use the mksparse utility to convert your cloned raw image into a sparse image…flash.sh works with either format so long as it is at “bootloader/system.img”.
I’m not sure how this works with simultaneous flash of multiple Jetsons, but likely it is the same (you’d have to watch out for customizations of the unit the image was cloned from…for example, if a udev rule puts a MAC address in originally scanned from hardware, then the unit the clone is sent to would also assume that MAC address…all units could end up trying to use the same MAC address).
Dear Rocky:
thanks your reply,but please support as flows two question:
1）How many microampere is the normal using of TX2 module RTC？
2) Because the peripheral circuit does not monitor the power circuit through the I2C, this will affect the TX2 boot startup. which part of the code needs to be modified？
Dear Rocky:
1)At present, TX2 development board memory is full, how to use software to optimize the memory of TX2 module?
2)Whether TX2 development board can add extra memory,if possible,which interface is passed？
3）How additional memory works at the same time with module memory,Do need hardware or software settings or other?
Hi, what do you mean the memory is full? Is it eMMC or DDR? If you mean the DDR, then it is impossible to add another one. If mean the eMMC, there is a SDCARD slot on carrier board for storage.
1）How many microampere is the normal using of TX2 module RTC？
It is typical 2uA
-
Because the peripheral circuit does not monitor the power circuit through the I2C, this will affect the TX2 boot startup. which part of the code needs to be modified？
Not sure what you mean, the power up sequence should not be changed.