Hello,
I have a question for all coockers about file structure.
I've managed to edit my OS.nb for removing the first partition how is unusable on our Prophet.
My problem is now with RomMaster : I can't extract my XIP anymore, I test to Fix my XIP start and end address but don't work (Make_XIP from hypercore don't work too).
Some informations :
My error with RomMaster :
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77b82448, but file length is 0x035f0000.
Click to expand...
Click to collapse
What I test to resolve my problem, so it don't work too
D:\ROMEDIT> RomMaster.exe -s 0x00000400 -e 0x0030FFF0 -w 5 OS.nb
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77b82448, but file length is 0x035f0000.
Click to expand...
Click to collapse
My OS.nb info (make with NBInfo.exe)
NBInfo 2.1rc2
'OS.nb' has valid boot sector
Partition table:
Partition 0
-----------
File System: 0x23 (XIP RAM)
Start Sector: 0x00000002
Total Sectors: 0x00001800
Boot indicator: 0x00
First Head: 0x02
First Sector: 0x01
First Track: 0x00
Last Head: 0x7f
Last Sector: 0x01
Last Track: 0x30
Partition 1
-----------
File System: 0x25 (imgfs)
Start Sector: 0x00001880
Total Sectors: 0x00019700
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x31
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x1c7
Partition 2
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Partition 3
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Geometry: flash has 128 virtual heads
MSFLSH50 header found at offset 0x200
(0 Reserved Entries, 2 Flash Region Entries)
Flash Region Entry 0:
---------------------
Region type: XIP
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x00000061 -> Size in sectors: 0x00003080
Sectors per block: 0x00000080
Bytes per block: 0x00010000
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Flash Region Entry 1:
---------------------
Region type: READONLY_FILESYS
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x0000032e -> Size in sectors: 0x00019700
Sectors per block: 0x00000080
Bytes per block: 0x00010000
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Searching for IMGFS signature...
Found IMGFS at byte 0x00310000 (sector 0x00001880).
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 00000000
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
---
Click to expand...
Click to collapse
So, if anyone can explain to me how to fix my XIP addresses to extract and modify it... Or without fixing an another method to extract XIP from my ROM (RomMaster and Make_XIP don't work with it)
Thanks in advance for your responses.
ps : sorry for my English for my problem explain but it's not my native language
Have you tried msflshtool to extract your xip partition ?!
hma4 said:
Have you tried msflshtool to extract your xip partition ?!
Click to expand...
Click to collapse
Thanks for your response, when I dump my ROM with this tool I've two files OS.nb.part0 and OS.nb.part1, so what is the real format of those files ? it's nb or bin extension (real) cause I want a bin file to edit with XipPort how request a xip.bin file.
I havn't tried to rename it cause don't say if it's the good format.
Just need that
Another question : for XIP can I add/remove some "FF FF" at the end to change the size? (for offset definition msflh50 header) ?
Thank for your hard work, perfect ROM and your help
xvx45 said:
Thanks for your response, when I dump my ROM with this tool I've two files OS.nb.part0 and OS.nb.part1, so what is the real format of those files ? it's nb or bin extension (real) cause I want a bin file to edit with XipPort how request a xip.bin file.
I havn't tried to rename it cause don't say if it's the good format.
Just need that
Another question : for XIP can I add/remove some "FF FF" at the end to change the size? (for offset definition msflh50 header) ?
Thank for your hard work, perfect ROM and your help
Click to expand...
Click to collapse
it's bin format. just rename it to xip.bin
you don't have to touch those FF in xip
Thank hma4 for your quick responses !
I'll test it !
So addinf FF at the end of XIP can make it unusable or anything else ?
hma4 said:
Have you tried msflshtool to extract your xip partition ?!
Click to expand...
Click to collapse
hma4
how to use this tool ( command, or Syntax )
Thank so much
Hi, i have NDrive for my HD2 and i have a little, very little problem
What i mean is... real little....
The Buttons are big and greatful to Tuch. But if i search a street or a city, the text are so small..
how i can change the text size?
On my Touch HD it work perfekt.
use this ini:
[settings]
GpsSaveButton = false
ManeuversOn = trueStretchMap = true
DPI = 245
UnitDefaultIsMiles = false
TrafficDefaultIsOff = true
[YFPND]
EnableTimeZoneConfig=true
PowerManagerOff = true
BacklightAPI = false
EnableGpsConfigButtons = true
[ELENTEC_NAVI]
EnableTimeZoneConfig=true
PowerManagerOff = true
BacklightAPI = false
EnableGpsConfigButtons = true
[GPS Navigation System]
EnableTimeZoneConfig=true
PowerManagerOff = true
BacklightAPI = false
EnableGpsConfigButtons = true
DPI = 250
[Handhold Reference Board_A3]
DPI=128
[PLATFORM_OEM]
PowerManagerOff = true
HWVolumeControl = true
DPI = 100
DatabaseOnCard = true
HasPhotoViewer = false
[GPS6027]
PowerManagerOff = true
HWVolumeControl = true
DPI = 128
[GPS6088]
PowerManagerOff = true
[GUEPARD]
PowerManagerOff = true
[NDriveG280]
PowerManagerOff = true
BacklightAPI = false
[NDriveG800]
PowerManagerOff = true
BacklightAPI = false
DPI = 128
[NDriveG400]
HWVolumeControl = true
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[NDriveTouch]
DPI=115
[NDriveTouchXL]
DPI=128
[Handhold Reference Board_A3]
DPI=128
[X1i]
StretchMap = true
DPI = 245
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[Palm Treo 850]
ForceGdi = true
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI=181
[NDRIVE S300]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI = 143
[DX900V040]
StretchMap = true
DPI = 286
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[Toshiba TG01]
StretchMap = true
DPI = 228
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC Touch Pro2 T7373]
StretchMap = true
DPI = 245
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC Touch Pro T7272]
StretchMap = true
DPI = 286
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC Touch HD T8282]
StretchMap = true
DPI = 245
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC T8282]
StretchMap = true
DPI = 245
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC Touch Diamond P3700]
StretchMap = true
DPI = 286
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[HTC_Touch_Diamond]
StretchMap = true
DPI = 286
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[SIM Technology]
StretchMap = true
DPI = 286
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[SGH-i780]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI = 177
[SGH-i900]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI = 147
ForceGDI = true
WM6SuspendThreads = true
SMSTransport = body
[GT-I8000]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI = 286
StretchMap = true
[ARTE10000]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Key.Camera = 0x5B, 0xC5
Key.SysMenu = 0x5B, 0xC2
Key.PocketIE = 0x5B, 0xC4
Key.SpeedDial = 0x5B, 0xC6
DPI = 143
[PHAR10000]
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Key.Camera = 0x5B, 0xC3
Key.SysMenu = 0x5B, 0xC1
DPI = 143
[ARTE20000]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.VolumeUp = 0x75, 0x75
Key.VolumeDown = 0x76, 0x76
GPS.ForceBT = 0
GpsIsBuiltIn = true
GPS.Port = 4
DPI = 143
[ARTE*****]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.VolumeUp = 0x75, 0x75
Key.VolumeDown = 0x76, 0x76
GPS.ForceBT = 0
GpsIsBuiltIn = true
GPS.Port = 4
GPS.Baud = 38600
DPI = 143
[Kaiser]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.Enter = 0x5C, 0x75
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Key.Camera = 0xE9
Key.Messaging = 0x5B, 0xC2
Key.SpeedDial = 0x5B, 0xC6
Key.PocketIE = 0x5B, 0xC1
Key.SysMenu = 0x5B, 0xC3
DPI = 143
[HERA10000]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.Enter = 0x5C, 0x75
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Key.Camera = 0xE9
Key.SpeedDial = 0x5B, 0xC6
Key.SysMenu = 0x5B, 0xC3
DPI = 143
[Polaris]
ForceGdi = true
Key.Up = 0x26, 0x84
Key.Down = 0x28, 0x84
Key.Left = 0x25, 0x84
Key.Right = 0x27, 0x84
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Key.VolumeUp = 0x75, 0x75
Key.VolumeDown = 0x76, 0x76
GPS.ForceBT = 0
GpsIsBuiltInt = true
DPI = 143
[NIKI100]
ForceGdi = true
Key.VolumeUp = 0x75, 0x75
Key.VolumeDown = 0x76, 0x76
DPI = 143
[Treo]
ForceGdi = true
DPI = 108
[AMOI Electronic CO.,LTD.]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
DPI = 143
[Mio Technology Ltd.]
ForceGdi = true
DPI = 143
[Hewlett-Packard Company]
Key.RotateScreen = 0x5B, 0xCE
Key.EndCall = 0x5C, 0x75
Key.Discard = 0x5B, 0xC4
DPI = 115
[hp iPAQ hw6915]
GPS.ForceBT = 0
GPS.ForceGPSID = 1
GpsIsBuiltIn = true
GPS.Port = 7
GPS.Baud = 57600
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Key.SysMenu = 0x5B
DPI = 108
[i-mate JAQ4]
GPS.ForceBT = 1
GPS.Port = 8
GPS.Baud = 9600
[HTC-S620]
Key.Fn = 0xEC
Key.ZoomIn = 0x28, 0x83
Key.ZoomOut = 0x26, 0x83
Power.LockLevel = 1
[HTC S310]
Key.Delete = 0x1B
Power.LockLevel = 1
[MAINSTN]
GpsIsBuiltIn = true
GPS.Port = 7
GPS.Baud = 9600
[Handheld Reference Board]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[Mitac, Mio DigiWalker]
GpsIsBuiltIn = true
GPS.Port = 2
GPS.Baud = 4800
Key.Soft1 = 0x5B, 0xC1
Key.Soft2 = 0x5B, 0xC4
Key.EndCall = 0x5B, 0xC3
Key.SysMenu = 0x5B, 0xC2
DPI = 115
[S3C2440]
Key.ZoomIn = 0x44
Key.ZoomOut = 0x45
Key.Soft1 = 0x42
Key.ZoomIn = 0x0D
[S3C2410]
HWVolumeControl = true
[GP75-ARMV4-30200]
HWVolumeControl = true
[Handheld Reference Board]
HWVolumeControl = true
[manta-35-01]
HWVolumeControl = true
[PU10]
DPI = 223
[HP iPAQ hx4700]
DPI = 266
[CREDIX M43C2 Board]
HWVolumeControl = true
DPI = 128
[NDrivePC]
DPI = 300
StretchMap = true
FullScreenMode = false
WindowSize = 800x600
[ZTE CO.,LTD]
DisableSoftKeyboard = true
Alpha2NumericMap = @ERTDFGCVB
SoftKeyboardStartsMinimized = true
[QUALCOMM]
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
Alpha2NumericMap = 0ERTDFGCVB
SoftKeyboardStartsMinimized = true
[GT-C6625]
DisableSoftKeyboard = true
Alpha2NumericMap = +ERTDFGXCV
SoftKeyboardStartsMinimized = true
[MACOSX]
StretchMap = false
[DX900V040]
StretchMap = true
DPI = 286
[MOTOROLA MC75]
StretchMap = true
DPI = 260
[Touch Diamond2 T5353]
StretchMap = true
DPI = 245
[GB_RAMAR_BLUE_BT]
PowerManagerOff = true
HWVolumeControl = true
DPI = 128
[NDriveTouch_SE]
DPI=125
[NDriveTouchXL_SE]
DPI=136
[NDriveTouchXXL_SE]
DPI=117
[HTC Snap S521]
DisableSoftKeyboard = true
DisableNumericMode = true
TegicET9Off = true
[Toshiba TG02]
StretchMap = true
DPI = 228
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
[GT-B7300]
DPI = 155
Key.VolumeUp = 0x75
Key.VolumeDown = 0x76
or only change [settings]
Thanks hol9er, this is working great.
Thank you SO much. Brilliant!
Hi hol9er
Thanks m8, this is it..
Sorry, but I don't understand what to do exactly with hol9er's information
Thanks for your help
arturobandini said:
Sorry, but I don't understand what to do exactly with hol9er's information
Thanks for your help
Click to expand...
Click to collapse
You have to edit the ini file on the ndrive folder.
Ok, I see.
Thank you very much.
[EDIT: I changed the text in the ini file, but the graphics in the settings are still very small ((( ]
I had the same issue, and this ini text worked for me!! Now the letters in Settings are big enough. Thank you!!
Hello arturobandini !
open the NDrive.ini file in windows with editor
it is a text file
delete the text
copy and paste my text
dont forget to save
phone to pc - active sync
copy and paste the new file over the old
path: /storage card/NDrive
thats all
run NDrive and enjoy
hol9er
edit:
landscape view with BSB-Tweaks
hol9er
I have oneother problem.
When ndrive starts tries to find a bluetooth connection (which isnt there) and there is a very annoying popup.
Also cant find the gps port at all.
Disable GPS (dis)connection sound?
I find the GPS disconnection/reconnection sound immensely annoying, as I routinely drive through a number of tunnels. I can't find a way to control it separately from the voice.
Any ideas? Any secret INI settings, maybe?
ugumba said:
I find the GPS disconnection/reconnection sound immensely annoying, as I routinely drive through a number of tunnels. I can't find a way to control it separately from the voice.
Click to expand...
Click to collapse
Of course, immediately after posting, I realised I could look for the audio files. I found the GPS connection sounds as 62.wav and 63.wav in the voice ZIP. They should be trivial to replace - I just deleted them myself.
Thanks a lot. U are the best.
What is the config so i only rotate NDRIVE?
Are there another way to view this in landscape without change other apps?
Thanks again
Good work !
Works 100%
Kindly yours
Worked a treat
Thank you so much
how can i landscape view
i love ndrive but the screen doesn´t rotate i don´t know what to do please help
i really need ndrive to rotate
thanks
no ideas..
mat19835 said:
no ideas..
Click to expand...
Click to collapse
Install BsB Tweaks foudn here (bottom of the 1st post): http://forum.xda-developers.com/showthread.php?t=589305
After you've installed it, launch it from the StartMenu and then click on Menu. From Menu, click on Rotation. From Rotation, click on Options and then click on Add Application and follow the directions and you'll be all set.
» OMAPFlash v4.15 (Aug 12 2011)
» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt
» @targets\Projects\espresso\omap4430hs_1200MHZ.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.txt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes
eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)
eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
ME too
nirmalece19 said:
» OMAPFlash v4.15 (Aug 12 2011)
» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt
» @targets\Projects\espresso\omap4430hs_1200MHZ.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.txt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes
eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)
eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
Click to expand...
Click to collapse
i think NAND error , cannot get into recovery mode, but get into dowload mode, flash via odin error
Hi,
I was looking to use the DJI Fly on Windows through WSA, I was able to install it just fine and it loads, but can't find a way to make it see the controller, can't find a mount option like yhe one find for example on VirtualBox, tried usbipd-win but it doesn't seem to recognize the Subsystem.
Has anyone been able to get any device "mounted"?
Thanks
Oscar
No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Renate said:
No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Click to expand...
Click to collapse
The controller is recognized as it should, I'm pretty sure, the device manager shows 3 types under the same device, with one being a com port which I suspect the DJI Fly app uses to communicate the controls, but I expect there to be some kind of menu or command that needs to be run to "attach" the device to the Android Subsystem.
Not knowing what the USB interfaces are I couldn't say anything intelligent.
That's why I asked you to tell me what they are in post #2.
This is what USB View gives when the controller is connected from the bottom port
Code:
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0xEF
bDeviceSubClass: 0x02
bDeviceProtocol: 0x01
bMaxPacketSize0: 0x40 (64)
idVendor: 0x2CA3
idProduct: 0x1020
bcdDevice: 0x0404
iManufacturer: 0x01
0x0409: "DJI"
iProduct: 0x02
0x0409: "C5"
iSerialNumber: 0x03
0x0409: "3QDCH950010H2U"
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x04
Open Pipes: 10
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Configuration Descriptor:
wTotalLength: 0x00BB
bNumInterfaces: 0x06
bConfigurationValue: 0x01
iConfiguration: 0x04
0x0409: "Configuration"
bmAttributes: 0xC0 (Bus Powered Self Powered )
MaxPower: 0x00 (0 Ma)
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x05
0x0409: "MA Channel"
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x06
0x0409: "HS-Data Channel"
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 02 02 02 02 01 07
Interface Descriptor:
bInterfaceNumber: 0x02
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x08
0x0409: "V1 ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 03
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 02 03
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x03
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x09
0x0409: "V1 ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 04 02 02 02 01 0A
Interface Descriptor:
bInterfaceNumber: 0x04
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x0B
0x0409: "Log ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 05
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 04 05
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x05
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x0C
0x0409: "Log ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
So, in short, you should have 4 "devices", that is 4 things with drivers.
There are two things that should appear in Device Manager as DJI things.
There are two things that should appear as generic Com Ports.
You can check the drivers for all four.
The last two should have usb2ser.sys
I would guess that the first two would just use WinUsb.
They should have under Details > Inf name something like oem123.inf
You can go to C:\Windows\INF\oem123.inf and see stuff there.
In any case, you should be able to find 4 happy devices in the Device Manager.
There are no Mass Storage devices here, so "mount" is used in some other context.
Code:
Device, VID/PID 2ca3/1020
The device class itself is ef:02:01, Miscellaneous class, Interface Association Descriptor
Unfortunately, you should only use this class:subclass:protocol in interfaces, not devices.
Interface #0
The interface is ff:43:01, proprietary, "MA Channel"
Bulk in/out is 512/8 bytes. Kind of unusual.
Interface #1
The interface is ff:43:01, proprietary, "HS-Data Channel"
Bulk in/out is 512/512
Generic serial port
{
Interface #2
The interface is 02:02:01, CDC control, "V1 ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #3
The interface is 0a:00:00, CDC data, "V1 ACM Data"
Bulk in/out is 512/512
}
Generic serial port
{
Interface #4
The interface is 02:02:01, CDC control, "Log ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #5
The interface is 0a:00:00, CDC data, "Log ACM Data"
Bulk in/out is 512/512
}
Yes I meant "mount" as in tell WSA to "connect" the devices to the Android system. In Device Manager the COM ports have drivers but the "HS-Data Channel" and "MA Channel" don't have drivers, as it was never meant to be used with Windows.
But you can see the two "Channels" in Device Manager?
No problem, just give them Zadig (WinUSB) drivers.
Zadig - USB driver installation made easy
You can't share anything from Windows to the Android subsystem unless it's a device with a driver (I think).