Is there any command line parameters for the camera.exe PPC 2003 2003SE & 2005.
Need to do the following if poss
Call up the camera ensure it is set to photo
set resolution
Auto save file in (my Documents)
Auto close camera.exe without preview
Is there a hack to get activesync4 to sync pocket access tables.
I can connect a 2003SE machine and sync okay with ver 4. Maybe there a way to hack the registry to ignore checking the OS version
Cheers
SteveW
Xda Camera command line parameters (some of them...)
Hi - been messing around calling camera.exe from pocketC / command line
(an ancient and obsolete virtual machine language for windows2003!)
So far I've managed to start the camera and change modes using these
parameters:
exec("open","/Windows/camera.exe","-i");
these are the parameters i've discovered so far:
-i =photo mode
-v =video mode
-p =contact photo mode
-m =mms video mode (also switches screen to landscape !?)
Hope these are of some use!
If amyone finds out the the argument to press the shutter button
PLEASE tell me!!
I think it might be some kind of hexadecimal code - but I am not
very bright with this stuff...
Cheers,
Chris.
Is there any command line parameters for the camera.exe PPC 2003 2003SE & 2005.
Need to do the following if poss
Call up the camera ensure it is set to photo
set resolution
Auto save file in (my Documents)
Auto close camera.exe without preview
Is there a hack to get activesync4 to sync pocket access tables.
I can connect a 2003SE machine and sync okay with ver 4. Maybe there a way to hack the registry to ignore checking the OS version
Cheers
SteveW
Click to expand...
Click to collapse
Has this been figured out yet plaese?
Hi,
got some Problem with pdocread. I loaded the latest Version available, extracted the archive to somewhere on drive c:, started dos box , changed to extracted archive path and wrote:
C:> pdocread
(just to read the parameters of pdocread)
... and nothing happens, it just hangs and doesn't come back to prompt.
Using windows XP SP 2, Active Sync 4.50 (Build 5096).
Anyone with this problem got an solution?
you mean when you are dumping the file... it takes a long time mine almost took around 30-40 mins for the whole thing to be dumped
But shouldn't it display it's parameters/options when i start the program without any of them? (I looked through the cpp code of it and it should display them!!)
Mhhh, strange..
thats not the default thing to do for an console application
in linux it's
applicationname |More
dos it's
applicationname /?
it's not general behavior to list parameter options when no parameters are given
Rudegar said:
thats not the default thing to do for an console application
in linux it's
applicationname |More
dos it's
applicationname /?
it's not general behavior to list parameter options when no parameters are given
Click to expand...
Click to collapse
Yeah, that's true. Because of that I looked into the c++ sourcecode (pdocread.cpp) and found that when no option's/parameter's are given the programm prints out it's parameters.
Now it works, under ActiveSync 4.3 and without closing the wcescomm thread.
I am getting
Can't find PInvoke DLL 'ril.dll'
error in Windows Mobile 6 and
failed to initialize RIL
error in Windows Mobile 6.5.
What can be the problem in using RIL (Radio Interface Library)?
How to check whether Radio Interface Library is intalled on my computer or not?
Never tried to use this stuff from C#, I've only ever called it directly from Win32 C++.
'RIL.DLL' exists in the \Windows directory of your device. You will have to use 'Show all files' in File Explorer to see it.
It also exists in the same place in the Emulator images.
When you call RIL_Initialise() you have to pass it addresses to call back routines that you supply.
Doing all this in a managed code environment could be a bit of nightmare.
in C++ this works:-
Code:
HRESULT hrRetVal= RIL_Initialize(1, ResultCallback, NotifyCallback, RIL_NCLASS_ALL, 0, &g_hril);
if hrRetVal is not returned as 'S_OK ' it didn't work!
The functions in the call are defined as :-
Code:
void CALLBACK ResultCallback(DWORD dwCode,HRESULT hrCmdID,const void *lpData,DWORD cbData,DWORD dwParam);
void CALLBACK NotifyCallback(DWORD dwCode,const void *lpData,DWORD cbData, DWORD dwParam);
I finally found some time to inspect the NST board for a spare UART and the search was successful!
The serial port can be accessed on U2713, pin 2 is RX, pin 3 is TX, device node is /dev/ttyS1.
I use it with a 3.3V USB-to-UART adapter, but any voltage between 1.2 and 3.6 should be fine, thanks to the TI voltage-level translator TXB0104.
There is also a second uart connected to J151 (ttyS0), but that one has no voltage-level-translator and runs with 2V. (TX is on pin 9 of J151, no idea where RX is).
I'm still trying to redirect the boot console to ttyS1, i think i have to recompile uboot.
/edit:
Patching u-boot worked, I have the boot console on ttyS1.
Good job!
I wanted to look for this sometime, but you beat me to it.
ttyS0 is for the (cell phone) radio
ttyS1 is for the Bluetooth.
Could the connector place there be for JTAG?
Renate NST said:
Good job!
I wanted to look for this sometime, but you beat me to it.
Click to expand...
Click to collapse
I wanted to do this since my last failed kernel porting attempt. I hope it helps me debugging non succesfully booting configurations.
ttyS0 is for the (cell phone) radio
ttyS1 is for the Bluetooth.
Click to expand...
Click to collapse
Is that an actual android standard, or just some leftovers from the reference platform the nst and nook color are based on (the remains in the init.rc)?
Could the connector place there be for JTAG?
Click to expand...
Click to collapse
I think the JTAG is more probably on J151 together with ttyS0, than on U2713.
ttyS0 was the standard console, and it would make more sense that the J151 was used as debug-port.
mali100 said:
The serial port can be accessed on U2713, pin 2 is RX, pin 3 is TX, device node is /dev/ttyS1.
I use it with a 3.3V USB-to-UART adapter, but any voltage between 1.2 and 3.6 should be fine, thanks to the TI voltage-level translator TXB0104.
Click to expand...
Click to collapse
Mali,
My USB-to-UART adapter needs 3.3V (to set “upper voltage” level)
Could you help, where can I get in on Nook board?
Renate NST said:
ttyS0 is for the (cell phone) radio
ttyS1 is for the Bluetooth.
Click to expand...
Click to collapse
Do you know any devices that can be connected to this ports? It would be great to enable only Bluetooth or even cell phone.
ApokrifX said:
Mali,
My USB-to-UART adapter needs 3.3V (to set “upper voltage” level)
Could you help, where can I get in on Nook board?
Click to expand...
Click to collapse
You can use pin 1 of U2713, it's connected to VCCb on the TXB0104. Altough the voltage is disabled when the nook sleeps, but that shouldn't be a problem.
mali100 said:
You can use pin 1 of U2713, it's connected to VCCb on the TXB0104. Altough the voltage is disabled when the nook sleeps, but that shouldn't be a problem.
Click to expand...
Click to collapse
Ok... But it's gotta be 3.3V somewhere, right?
ApokrifX said:
Ok... But it's gotta be 3.3V somewhere, right?
Click to expand...
Click to collapse
Quick! Break the laws of physics and pull power from a penny!
I haven't had a driving need to use this until I tried an upgrade to 1.2 and got a boot loop.
There are various versions of u-boot.bin.
The easiest way to patch it is to simply search for ttyS0 and replace the two occurrences with ttyS1.
ttyS0 appears also in env.txt inside uRamdisk (and uRecRam).
I found a old fax that has the 10 pin connector that fits on the Nook.
I might try to put it on. For now I have the soldered wires.
In any case, the 1.2 boot loops and the last message is:
Code:
binder: 988:1039 transaction failed 29189
I've screwed with a lot of things on my Nook, but the "update" should have wiped about everything.
Just a short update:
I soldered in the connector successfully. It looks nice.
The level converter to standard 9 pin "RS-232" is simple and cheesy, 2 resistors and a transistor.
It works fine though. I can see the boot up.
After that I can switch to logcat over ADB over USB.
Here's a really poor photo of my setup.
My next cell phone must have auto-focus and macro mode.
Excellent setup, especially for the ribbon cable! It seems something nice its going to happen in the next days
Just a bit of an update.
If you want to do your own level shifting you've got access to two UARTs.
The MSP stuff is I2C to the MSP430 microprocessor that handles the touch screen.
You could eavesdrop on that and have a little multitouch pad.
I'm still trying to see which of the rest of the pins are for JTAG on U151.
The other 4 pins on U2713 are 3.3 level but don't come from the TXB0104 level shifter.
The JTAG stuff is apparently on the 22 pin, 0.5 mm pitch CON6.
The four side buttons are on CON6 too.
I've looked at this a bit and I've determined that using UART2 is a dead end.
The TXB0104 is neither powered nor enabled until late in the boot sequence.
Using the default UART1 is a much better choice.
Yes, you could modify things to use UART2 over UART1 but it's an uphill battle.
u-boot has a nice command interface where you can do lots of stuff (edited a bit):
Code:
Texas Instruments X-Loader 1.41 (Dec 7 2012 - 14:34:26)
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4-carbon1.2_1.2.1.24^{} (Dec 7 2012 - 14:34:22)
OMAP3630-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3621-Gossamer 1.2 Version + mDDR (Boot NAND)
DRAM: 256 MB
In: serial
Out: serial
Err: serial
Hardware arch: GOSSAMER rev: EVT3
Power button is not pressed
pmic watchdog time 0
Power Button Active
gossamer charger init
Booting from eMMC
OMAP36XX GOSSAMER # help
? - alias for 'help'
autoscr - run script from memory
base - print or set address offset
battery - gas gauge BQ27520 info
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
calc - perform mathematical operation
charger - charger BQ24073 info
clock - Manage system clocks
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
echo - echo args to console
epd tests dspon dspoff image1 image2
exit - exit script
fastboot- use USB Fastboot protocol
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatsave - save binary file to a dos filesystem
ggflash - flash bq27500 from .dffs script
go - start application at address 'addr'
gpio - set/display gpio pins
help - print online help
ibatck - used to track battery id
ibus - Select i2c Bus
icrc32 - checksum calculation
iloop - infinite loop on address range
imd - i2c memory display
iminfo - print header information for application image
imm - i2c memory modify (auto-incrementing)
imw - memory write (fill)
inm - memory modify (constant address)
iprobe - probe to discover valid I2C chip addresses
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mm - memory modify (auto-incrementing)
mmcinit - initialize mmc
mmc - Read/write/Erase mmc
mspflash- used to flash a new msp430 firmware file
mtest - simple RAM test
mw - memory write (fill)
nm - memory modify (constant address)
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
setenvmem - set environment variable from memory
sleep - delay execution for some time
test - minimal test like /bin/sh
version - print monitor version
OMAP36XX GOSSAMER #
Just adding the battery pinout to the diagram for completeness.
Excellent! I recently bought a JTAG (http://www.ebay.co.uk/itm/Altera-FP...al_Components_Supplies_ET&hash=item257fc5c582)
I will give it a go... is there anything you'd like me to do?
Cheers
Heres a quick hack to talk to uboot over UART2
Edit: all that's different is enabling the TXB0104 by setting gpio 37 high instead of low.
and redefining the uarts so 2 is used instead of 1.
includes the OP's patch so kernel logs show after boot also.
this second version fixes autoboot. UART2 gets a spurious byte which needs to be cleared otherwise autoboot never works.
This patch is meant to be applied without the first one, i put the uart numbers back to normal and just changed the index of which gets used for console.
I also enabled ^C checking for the case where bootdelay is zero, you can't lock yourself out of u-boot by messing with the env variables. ( Guess why I decided to do this?
NB: There is a third uart, uart3. one of the sets of pins it can be muxed onto are the usbhs0_data0 and 1 pins.
these go to the tps65921, which also has a uart mode , whereby we could have uart access over the usb pins without cracking the case.
droid phones had something similar, called emu-uart. i will look into this more when i get a nook with a working usb port.
Anyone able to help? Thanks to Apachas and few other users I was able to boot my crashed Asus vivotab tf600t and almost got it up and running.. Almost.
I believe I have done everything according to instructions, installed Apachas' image and configured what I can but bcdboot gives me an error when doing the installation: failed to open handle to fwbootmgr, status c0000034 . Everything seems to go ok except this error which apparently is fatal.. Windows will not start but gives 0xc0000001.
Can Someone who owns the same (working ) device print their "bcdboot /enum all" command output here? I don't seem to have the fwbootmgr and something else is probably wrong, when I run the bcdboot /enum all, but I don't have a clue what to do now.
Here is the output from mine.. can anyone tell what is wrong with it? Should I have the fwbootmgr? How to add it? Don´t seem to find any information online..
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=S:
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {default}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device partition=W:
path \Windows\system32\winload.efi
description Windows RT
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=W:
systemroot \Windows
nx AlwaysOn
bootmenupolicy Standard
detecthal Yes
EMS Settings
------------
identifier {emssettings}
bootems No
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Thanks a lot..!!
Lellek said:
Anyone able to help? Thanks to Apachas and few other users I was able to boot my crashed Asus vivotab tf600t and almost got it up and running.. Almost.
I believe I have done everything according to instructions, installed Apachas' image and configured what I can but bcdboot gives me an error when doing the installation: failed to open handle to fwbootmgr, status c0000034 . Everything seems to go ok except this error which apparently is fatal.. Windows will not start but gives 0xc0000001.
Can Someone who owns the same (working ) device print their "bcdboot /enum all" command output here? I don't seem to have the fwbootmgr and something else is probably wrong, when I run the bcdboot /enum all, but I don't have a clue what to do now.
Here is the output from mine.. can anyone tell what is wrong with it? Should I have the fwbootmgr? How to add it? Don´t seem to find any information online..
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=S:
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {default}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device partition=W:
path \Windows\system32\winload.efi
description Windows RT
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=W:
systemroot \Windows
nx AlwaysOn
bootmenupolicy Standard
detecthal Yes
EMS Settings
------------
identifier {emssettings}
bootems No
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Thanks a lot..!!
Click to expand...
Click to collapse
I searched a lot and found this:
I was deploying a W2K8 R2 image on a ML350 G5 some time ago and was unable to make the system partition bootable. Never thought of writing about this but the issue reappeared lately on a G7 so here it goes..
Running “bcdboot.exe c:\windows /l en-us” returned a “Failure when attempting to copy boot files” error. And yes, I did check if the partition was active and it was. I heard that this issue was resolved by some by destroying the array, rebuilding it and installing the image again. I did so but with no further luck – unfortunately a huge waste of time over iLO and a slow connection (you probably know what I mean).
Turns out that the command which finally worked correctly was “bcdboot c:\Windows /s c: /l en-us” while running it from the WinPE drive.
The “/s” option according to the manual “Specifies an optional volume letter parameter to designate the target system partition where boot environment files are copied. The default is the system partition identified by the firmware.”
I guess the default system partition could not be properly identified thus all the fuss. Weird, I haven't found a reason for this. Didn't look deeper since I found a fix. Anyway, hope this helps!
so out of desperation I changed the last line to: bcdboot w:\windows /s w:
and it created boot files successfully! however now I'm stuck on Asus logo.