BOOT_ON in the resistor constant name does indeed mean the BOOT pin is on, so the BOOT signal from the FSA9480 will be high for 619K and 301K resistors on the ID pin, no other external inputs required
The MANUALSW2 I2C register that we were playing with earlier does indeed set the BOOT pin high and low.
So, the BOOT pin from the FSA9480 is not directly connected to the OM[5] pin. If it does affect it at all, as was hinted at by the BOOT_MODE signal on the block diagram, then there is some additional logic involved somewhere.
The phone boots up automatically with the 523k (BOOT_OFF) and 619k (BOOT_ON) resistors. So the BOOT signal, if it is used at all, doesn't tell the application processor to boot up.
BOOT_ON in the resistor constant name does indeed mean the BOOT pin is on, so the BOOT signal from the FSA9480 will be high for 619K and 301K resistors on the ID pin, no other external inputs required
The MANUALSW2 I2C register that we were playing with earlier does indeed set the BOOT pin high and low.
So, the BOOT pin from the FSA9480 is not directly connected to the OM[5] pin. If it does affect it at all, as was hinted at by the BOOT_MODE signal on the block diagram, then there is some additional logic involved somewhere.
The phone boots up automatically with the 523k (BOOT_OFF) and 619k (BOOT_ON) resistors. So the BOOT signal, if it is used at all, doesn't tell the application processor to boot up.
True. I think the boot signal is a signal for the kernel to start battery charging display, or actually boot Android.
Quote:
Originally Posted by jrloper
Windows is a finicky, needy, hormonal pain in the .... You get the point.
It loads the battery charging kernel if the JIG signal is off and the power switch is off, and it has power on the USB socket (VBUS_IN). It's the JIG signal that switches on the phone automatically in the factory modes, we know this from the circuit diagrams in the service manual. So the BOOT signal goes somewhere else.
It loads the battery charging kernel if the JIG signal is off and the power switch is off, and it has power on the USB socket (VBUS_IN). It's the JIG signal that switches on the phone automatically in the factory modes, we know this from the circuit diagrams in the service manual. So the BOOT signal goes somewhere else.
Then why do the "boot off" resistors only activate charging mode and not boot?
The kernel loads up whenever power is applied. The boot on resistors actually turn the phone on.
Quote:
Originally Posted by jrloper
Windows is a finicky, needy, hormonal pain in the .... You get the point.
Then why do the "boot off" resistors only activate charging mode and not boot?
The kernel loads up whenever power is applied. The boot on resistors actually turn the phone on.
Yes, I should say the JIG signal switches it on when there's no USB power. If there's no USB power then the BOOT_OFF resistors still switch the phone on. But after the SBL is loaded all the decisions are made by reading the resistor value through I2C, so there's no need for the BOOT signal at that point. So it must be doing something else.
I'm still exploring for i2c, it's cheaper then JTAG, and, according to Google IO, its supported by the Android Open Accessory Standard ( which is an Arduino mega + usb shield + extra crap.. the extra crap brings the price to $400). So, it still makes sense to explore that.
Since the chip has a maximum i2c speed of 400khz, and the processor has a maximum i2c speed of 3mhz, 400khz would be the logical i2c bus speed on the platform. The following modification is required for Arduino to communicate at this speed:
under linux:
1. edit the twi.h in the wire library
If you’re a Sony device owner running a stock Android Jelly Bean firmware and … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?