Activity
From 09/08/2014 to 10/07/2014
10/01/2014
- MK 02:31 AM PCB Development: RE: Spurious Reboot Debug
- Yes. Where do I send it?
09/26/2014
- MW 09:11 PM PCB Development: RE: Spurious Reboot Debug
- Would you be willing to share (privately, not on the forum) your baseboard schematic?
-Mike - MK 08:19 PM PCB Development: RE: Spurious Reboot Debug
- Michael,
Thanks for the replay. No problem with the many questions.. I'm kind of at a loss tracking down the issue, so any tips can help.
_Are these MityARM-3359s? What is the model number? Do you also have a couple of serial num...
09/24/2014
- MW 05:59 PM PCB Development: RE: Spurious Reboot Debug
- Hi Mr. Karasoff,
Are these MityARM-3359s? What is the model number? Do you also have a couple of serial numbers of the modules that are exhibiting the problem?
Does the reboot issue track the SOM or the Carrier board? E.g., if y... - Hi,
I am having an intermittant issue with the MityARM on some (not all) of our custom carrier boards - The processor has spurious reboots. The processor will boot and run Linux fine, then it reboots on its own, starting at the bootl...
09/16/2014
- JC 08:49 AM PCB Development: RE: Pin mapping option for Carrier board design
- This depends on at which stage you want access to the pins. Both u-boot and the kernel make changes to the pin mux. If the device needs to be accessed while you in the u-boot bootloader then u-boot should set the pinmux. If not then t...
09/15/2014
- ZJ 04:29 PM PCB Development: RE: Pin mapping option for Carrier board design
- I see. Thank you.
And how am I be able to change them?
Zhe
09/10/2014
- JC 08:41 AM PCB Development: RE: Pin mapping option for Carrier board design
- Have you looked at this wiki page?
[[Pin Out]]
09/09/2014
- Hi,
I am now designing a carrier board for MitySOM335.
In the design guide, it mentions:
The I2C1 and I2C2 interface signals/mux options cannot be changed as they are used for dedicated functions on the MityARM-335x module.
Is ...