yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] dougdude10:
Hi guys, I have a board labeled: C021_PX5_V5.1LP I'll attach a pic later of the board.

My MCU is: S32F0_XinRc

Anyway, I have my usb jig made, I can't get windows 10 (x64) to recognize the device. any ideas? I get the "usb device not recognized"

[IMG="board1"]https://lh3.googleusercontent.com/WPwaXPIHDWOVDw58jc1ZwmgWpk6SO9zg5JxFZgNhdIFuOSmypkqGgSNiAB62Vm3mtBh3msUg0CKOy9P30zHRe9uDJNzSCULGyupSkuQ6PIqYc2Y63q_avnVgtbutIz1XZpUia3SZNKEf8ZvIL4ECvYWT-hXdJ-XqorfLD8pGztT0le_XItwTgG-aUDGkeXcuDTNUigsrVXULol1BZtIk6uhU0CCwIIHZu2X6mQp3V8GmQNxhi0SHrDWthrA8YPVbV9KwtGIzIIdpFjD8kC3i3REaC80APuHIAYCU_6Rnt1Ppsk7QFq_xs3sq7NClT7gyy4VWmMuNo5_7_iGUX1OAbKCd6Tmc3Ivfwbw8gYUQiJx1yroo_q3WckNu7fm5ggkowxM4J7XXibxcUUdIacLEB_2PzEhYoDvOQYllp_4yH3IDnU2L7ABjz0oIHwmrj5pH09LEIhAtEL9-ucm0DfiRiQQ7tvERdPiCZTr91F6kct2V28jlC5qM_KvcPlyvF0KyMiasxMB0FyUO1zWyeoSt3hwbC4uPNeEb5-cptVcxf4CnLiTlQOwpdUhDN90zet0xrVfHRYuh8a2J_bXhh36_2T89qcCXP4E9dbTpj7IjEMnTPIVGQ0tc-Uz3pQiyy5UFKucN2RvRMbkNsunu_f3JN2Z4fFaND-tNOosCBsiVRXNEaPjciGEivPQ=w687-h916-no[/IMG]

[IMG="board2"]https://lh3.googleusercontent.com/9rOCF2eR4QBMBNgTPgIGZXRuWhiPN7geC_VeCFQyEjzT0sLqU5tlHlwcL_JEZj4JS1lvyjRN0JFDxGPV9lLZr40TdkWEerhNq0AIdNJDULuF1jMs4LWMEHJRuLYVoRd3GxzAIMoejDDj3fvhO6bS2fTOy1_A6c3Z3wb6WzO-MfCff9_j4cUZrdp2c3vVzdvD8gnvEL_eDJQpExjGTP_i7qYHIpU1-MfKgiDkIel0VATrJDXqJzFJi07iE0eH6KdcFRf4-IXe58z5K78_sev_kyj3kRtgsyHOf17WwqcCaBWv1uAvbuLK1JRAJw884BHBehxCqnatkweuLotOtN8nquMlhezoGhrxOFuUbEZBWzrqLr8yq6YXNL87hZuzz3Ng_-RB-R4fwRsmMU_Z8tkxqXOzk62CqdDf58Mf3xYfjnUsIecIibGmnz5zwBUs0JNr3BAq0_xElwBHSAKKVf1EE2VM987kaZPYR_QKJ7ItJam38P3yI6t0FwEF3ioDWzD9ZpKxzCOXv5BLkIx_3vBUU8VT2gMVq9tojtcMBMKAL4BkVpgi2dLBB937dd1aYShT7YZviK5KZPCdtCbaNRtrbbt_9mPcOKqqrfNIoTnfw7Uc-XPO_UFH3xway1mxYWbrSdc9hpi3iyC50A8HnyGfyzgSXrmzwFMjnYovGQamhhgk8gc9APAOVgU=w687-h916-no[/IMG]

any help would be appreciated

i also believe that I short these two points, can anyone confirm?

https://drive.google.com/open?id=18UkERul93FBpzQHUzhx1LuHFHJQaVr6H
[MTCD Hardware Development] typos1:
A what ? Whats your MCU ?
[MTCD Hardware Development] dougdude10:
S32F0_XinRc
[MTCD Hardware Development] marchnz:
Your unit isn't an MTCD/E, which the instructions and connections are for.

How did you validate the connections to your different SOM are the correct OTG and power supply connections?
[MTCD Hardware Development] dougdude10:
I thought all PX5's were the same, guess I got lucky?
[MTCD Hardware Development] typos1:
All RK3368/PX5 processors are the same, but the processor is mounted on a different SoM.
[MTCD Hardware Development] dougdude10:
I have a RK3368 processor.

So what you're saying is I need the pinout to my specific SoM?
[MTCD Hardware Development] typos1:
PX5 is another name for the RK3368.

Yes, you need a pinout specific to your SoM.
[MTCD Hardware Development] dougdude10:
thank-you so much! one more question, any idea where I would find such pinout?
[MTCD Hardware Development] typos1:
The manufacturer is always a good place to start, this may or may not involve a lot of internet research.
[MTCD Hardware Development] Candanga:
Dead SOM?

Hello,

I manage to build the OTG cable with not results. I made 2 versions with 2 different cables (insulated and non-insulated) and 2 combinations of resistors (12K /22k, 1/4w and 1/2w, though their tolerance is kinda funky, as they are reporting a little off on the multimeter). Tried 3 different PCs (1 AMD B350 and 2 Intels).

I tested continuity between the cables and the USB connectors, all fine according to the OP schematics. The pinouts were confirmed not to short between each other (GND was confirmed to be the correct one against the chassis).

When I plug the board there’s no change in Win Dev Manager nor “any sounds”, reporting connection.

My board is a Rev.10 and this board comes with two connectors (cirlced red in one picture) so you can short the clock and GND to enable MaskRom mode (I mapped them), shorting these or the resistor with GND has no effect.

Any thoughts?
[MTCD Hardware Development] marchnz:
Great to see you try. Sounds like you have a multimeter.

When connected to USB/computer, what are the voltages at the point (with respect to ground) - +3.3, +5, usb data +,- ,recovery,etc.

Just an fyi - you're welcome to send the som to me.
[MTCD Hardware Development] Candanga:
Yes, I do have some multimeters (all over the house :o )

Pin1 (5v) 4.99v

Pin20 (recovery) 1.9v

Pin28 (USB det) 1.9v

Pin29 (Data-) 0.04v (unplugged 0.14v)

Pin30 (data+) 0.04v

Thanks for offering me to send the SOM, I want to fight a little bit more with it.

---------- Post added at 01:54 PM ---------- Previous post was at 01:47 PM ----------

Also, jumped eMMC clock and GND while testing the leads, no difference.
[MTCD Hardware Development] excessdivide:
(X-posted) Bricked

Bricked

Attempted the upgrade from 8x to 9x.

Ran the 'upgrade8' from Hal9k's Pie upgrade package, and it worked fine. Ran the mod4 update.zip and the unit boot looped.

Followed the advice on the forums to use sdformat and now the device is bricked entirely; will not even enter recovery. It's stuck at a blank back-lit screen without ever showing the bootimage or android logo. I've waited over an hour to be certain that it wasn't just being slow. I've also tried to boot to 6, 8, 9 as well as Stock, Malaysk, and Hal9k. Dead as can be.

I'm not technical enough to follow Marchnz's advice to make a otg cable. (https://xdaforums.com/and...dware-t3734376)

Any suggestions?

Really love this unit and not excited about paying for a new one, though I will if I destroyed it.

Thanks gang!
[MTCD Hardware Development] marchnz:
If unable to make an OTG cable or find local help to make one, you're welcome to send the SOM to me in New Zealand, otherwise might you have more local help to build OTG/Force and also force maskrom on your SOM?
[MTCD Hardware Development] marchnz:
Odd, perhaps the PC USB supply isn't good enough, from memory you should measure +1.5 on the USB Datalines.

Others have experienced USB supply as an issue.

Do you have a bench +5 and possibly +3v3 supply you could try to power the SOM with?
[MTCD Hardware Development] Candanga:
Yes Sir I do, my bench PSU has only one output, so +5 only? how many amps do you suggest?

Let me know how do you want me to supply the board, as I don't want to backfeed the PCs motherboard.
[MTCD Hardware Development] marchnz:
Disconnect the +5 from the USB Cable, retain the USB Power earth/neg connection.

I'd limit current to 1A, if the current consumption is steadily above that, there may be a much bigger problem.
[MTCD Hardware Development] excessdivide:
Thanks!

You are really incredible [MENTION=4974080]marchnz[/MENTION]! I'll keep playing with it and see if I can get some local help.

Thanks!
[MTCD Hardware Development] marchnz:
Depends on who you talk to ;) I enjoy helping those that at least attempt to try and help themselves :)
[MTCD Hardware Development] excessdivide:
36 hours later; I'm sitting in traffic, and suddenly the bootlogo pops up, followed by Android Recovery 9. I swear for the life of me I couldn't tell you what happened! After I got home I kept the car running so not lose recovery, and I was able to successfully install the Hal9k v4 mod! It is great as always! Thanks!
[MTCD Hardware Development] Candanga:
Hello again,

Witson staff sent me an update.img image file for my unit. I'm working overseas and should be back tomorrow. In the vegetative state that my unit is (no video, just triple LED blink when power button pressed for 8secs), will this shed some light if I plug it in the MAP/SD slot?

Haven't sit on the bench yet to apply power with my variable PSU.

Thnx again
[MTCD Hardware Development] marchnz:
Hi, what android version and MCU?
[MTCD Hardware Development] Candanga:
Android 9. MCU dont recall, I have it at home. I just saw they sent me some other tools, the factorytool and drivers. Apparently my unit can be recovered by a loader mode using the rear USB ports.

I'll test it when I get home.
[MTCD Hardware Development] Candanga:
Ok, so I have succeeded to make my PC recognize the board under Maskrom mode. The voltage supplied by the USB wasn't enough, so I had to supply the 5v through my PSU.

Now I'm reading all over the forums how to use the Android Tool, cause I don't want to FUBAR this even more. If I succeed, I will post my whole procedure to avoid further readers stumble upon what I've gone through, and avoid people go all over XDA looking for puzzle pieces (though this is 100% unavoidable, as every case is unique and different).

I can see the supplied AndroidTools 2.7 is missing a cfg file (I have an RK3368), so I will look on that. Though the supplied manual is fine, I still don't know how to properly load the FW the vendor has provided me.

I have OEM update.img, an MCU and update.zip.

Thanks
[MTCD Hardware Development] Candanga:
Ok, SOM recovered partially, was able to flash the OEM update.img, but it still behaves as before (before the screen went black and all died).

I will now read more about erasing the flash and lower format, I'll try as well the published procedure of using recommended ROM.
[MTCD Hardware Development] Candanga:
Hello again!

I have successfully established comms between the android tool (rkdevtool) and the SOM. I have flashed several ROMs including the OEM image supplied by the vendor with no results, so I’m suspecting a NAND failure or some other HW component (due to the fact that this is an unmodified HU and the errors and bootloops began randomly)

I have learned the hard way about the compatibility of drivers and the android tool (older versions have the Lower Format function, newer ones have Dev Partition), that said, this is where I’m standing:

When first connected, the only way to boot it up was under MASKROM mode, now it loads as LOADER

Used v2.1/2.35 with 4.3 drivers (better than v2.71 with 4.9 drivers), and I’m getting “cleaner” logs, though the NAND fails to check at the end of the process (screenshot below)

Lower formatted, loaded the config16 removing cache and userdata (files are huge eitherways, about 22GB), flashed A8-Kumarai, added parameter, etc.

Tried the above steps backwards, including Erasing the Flash and flashing the miniloder

Same results under FactoryTool, process hangs at the end (log and screenshot added)

At this point I think I might have bad HW or maybe there might be hope trying another format procedure, maybe using the batchtool, as I’ve seen in other forums.

BTW, the vendor says they can't go to work cause of the coronavirus, hope my replacement SoM comes clean :D , in the mean time I haven't lose hope on this one.

Thanks [MENTION=4974080]marchnz[/MENTION], your OTG procedure has at leat shed a light in my journey to getting this fixed.

Comments are appreciated!
[MTCD Hardware Development] elalvaro19:
Is there any solution for usb that doesn't work? My px3 drive has 2 usb ports, one works but the other doesn't work, It doesn't work since I recovered the drive
[MTCD Hardware Development] typos1:
Did you damage the header when you inserted pins into it ? This has happened before.
[MTCD Hardware Development] elalvaro19:
I would say that I had all the pins well when I put the board, the USB has power because I have a USB with light and it works.

on the other usb that works, if I put a usb switch will it work?
[MTCD Hardware Development] typos1:
Some people damaged the header and the contacts inside, but they repaired them with silver foil.
[MTCD Hardware Development] GiuCic:
help me, px5 rev 4.0 brick.

Hi, i made the otg-usb cable,but the pc never recognise the som. I used many combinations of resistors from 12k to 22k from 1/2w and 1/4w. I tried even maskrom mode but nothing change, i hve hct px5 rev 4.0.

The head unit is bricked when i tried to update to android 9, with the sd card upgrade, the hal9k mod recovery it was successfully installed, than the message to remove the card and thats it, i got black screen, can not enter anymore in recovery mode, with sd card upgrade is not starting. And now i tried the otg unbrick but no success. First of this brick i have upgrade/downgrade many times my unit, from android 6 to 8, then to malaysk mod, and now wanted to try the "pie" update. help please.
[MTCD Hardware Development] GiuCic:
Help to connect som to pc.

hi, I wanted to ask you to help me build an otg usb to unlock a som hct px5 rev. 4.0 I can't connect it to the pc. I followed the whole procedure but I can't. thank you.
[MTCD Hardware Development] marchnz:
Have you had a good read through the thread, as it covers probably all of the issues.

First, check if the USB supply and connections are correct - suggest checking the voltages at each pin when connected to the SOM as a start.
[MTCD Hardware Development] GiuCic:
Hello. thanks marchnz for replying I have read almost all posts I have been looking for solutions for a long time. you can help me get the som back to pc, you can tell me the pin voltages.

is which resistors should I use from 12k, 15k from 1 / 2w or those 12k 15k from 1 / 4w. thank you.
[MTCD Hardware Development] GiuCic:
Help. SOM px5 rev4.0

hello, I have seen many images to create an otg cable for px5, I have tried it and the pc does not recognize the som. mine is PX5 SOM rev4.0. which pin are needed to create the cable. Is there someone who can help me. Thank you
[MTCD Hardware Development] Candanga:
So, The seller finally sent me a new SOM, once installed I get a white screen.

I replaced the LCD screen ZIF/Flex cables with the same result. I replaced the bad/original SOM and I get the faulty OS trying to boot up with video and all crap.

Took it off my bench and installed it in the car, same results. I try reverse and the HU blinks, trying to switch to the reverse camera module, but still with a blank screen.

Is this might be related to incompatible MCUs? I'm thinking about making a backup as per the MCU thread.

Any ideas?
[MTCD Hardware Development] bugyc:
Hct-px5-rev8.0 4/32 gb

Hello

I have a px5 board. Flash via OTG, put SoM in HU, works random, sometime 5 min, sometime 2 hours. At a moment on the screen appear POWER OFF, after that the HU is dead. Remove SoM , flash again, start , config, dead again.

Anyone same symptoms?

A advice? Thank's.
[MTCD Hardware Development] Malugo:
Px30 pinout

hi is it possible to have pinout for px30?
[MTCD Hardware Development] marchnz:
MTCD or MTCE SOM pinouts are all the same!
[MTCD Hardware Development] Malugo:
px30 otg cable

I made all the connection with resistances from 15k and 12k the pc detects the connection, unknown hardware, I use windows7 64bit
[MTCD Hardware Development] Malugo:
Px30 download boot failed

I made all the connections, now the drivers work, when I go to download the firmware it always gives me download boot failed, how can I solve it?
[MTCD Hardware Development] marchnz:
Erase flash. What version of SOM (px3/5/6) android, MCU type and instructions are you following. Assume MTCx device and not some other variant?

Details are where it's as to get help, guessing isn't fun for anyone.
[MTCD Hardware Development] Malugo:
Px30 boot failed

i am using px30

HCT-PX30_rev06
[MTCD Hardware Development] bilodemir:
Px5 MTCE

I uploaded the image of android 6 "firmware new.img" with the px5 maskrom usb method androidtool. but there is still a black screen. In addition, when you hold down the power button for 10 seconds, the lights flash and reset takes place.

which roma maskrom method should blink.

Or what can I do differently.

Thanks.
[MTCD Hardware Development] chargeable:
OTG for REV10

Hello 2all,

Can anybody tell me, is it REVision 10 PX5 SOM pinout is different then REV8? i was trying my best to connect OTG usb cable to SOM and no luck with detecting it...

Thanks in advance
[MTCD Hardware Development] marchnz:
Wouldn't that require the mainboard change? MTCD/E units SOM headers haven't changed.

I cant see necessary detail in your post needed to be anymore helpful.
[MTCD Hardware Development] chargeable:
OK, starting from scratch:

My HU Seicane H2002L with PX5 4/32gb Android9 (MCU HF-3.18a / android version 20190612), was messing from begining with black screen problem, when car is just started, headunit wont start until reset pressed. Thought it was software issue. Seller sent me "update" (later i find out that it was older version), but then i got stuck in BOOTloop.. Reset hole just cuts power, no recovery mode accessible. Took out coreboard, was thinking of making USB otg cable and connect it to PC.. Connected with resistors, tried alternative power for 3.3v.. still no activity on device manager.. and today found topic 418... maybe i missed something with pinouts, because i was using only pins 1,5,20,28,29,30 on REV10 board..

Do i have to use other mentioned pins for 5v and ground? (not tried yet)

Does shielded ground from USB must be connected also to black(ground) wire also?

Communication with seller is lost for good... (seen for sale android10 units already..) they dont send update files anymore sadly..

Because it happened long time ago, i bought second same unit, but now i got REV13 board with 4/64GB. MCU was already 3.30 and Android version 2019-11-14. Black screen issue gone on new HU, and i updated my old motherboard with ST-link to update 3.18mcu and it did work too; UPdated TDA sound chip also.

[IMG="new HU"]https://i.postimg.cc/B6HmTx24/IMG-20191225-220348-02.jpg[/IMG]
[MTCD Hardware Development] marchnz:
Great response. Didnt see if MASKROM was tried?

Does the good unit SOM work in the bad unit?

Does the "bad" SOM work in the good unit?

Regarding the issue of SOM not communicating via USB - I have had multiple SOMs sent to me that would only connect via USB with MASKROM. Thought I had posted about that in the OP.

No you do not need to connect the shield of USB, but cant hurt connecting to GND of SOM.

Re.

"Because it happened long time ago, i bought second same unit, but now i got REV13 board with 4/64GB. MCU was already 3.30 and Android version 2019-11-14. Black screen issue gone on new HU, and i updated my old motherboard with ST-link to update 3.18mcu and it did work too; UPdated TDA sound chip also."

Not sure what you mean. Are you saying you tried the "bad" SOM in the GOOD headunit and it worked? Or tried good SOM in BAD unit and it worked?
[MTCD Hardware Development] chargeable:
Tried MASKROM but did not get any response either.

I wanted to know if MCU motherboard is ok, and it was. "BAD" SOM was doing same bootloop in the new headunit. New SOM in old MCU board worked ok.

By the time i got sorted new unit coming, done old mcu motherboard sound upgrade and soldered wires for flashing MCU. Would be nice to have external button for going to recovery, but my knowledge ends here.. soldering and resistors is not my thing, i think practice is not enough, you have to know what you are doing...

I will try to give another chance for that OTG cable; Do you use same pins for others PX5 boards or tried different combinations? Thanks
[MTCD Hardware Development] marchnz:
Same pins. Double check wiring is correct.
[MTCD Hardware Development] chargeable:
Finally got in maskrom, throught male to male USB.Now updating.. last need to get latest android9 update :) Thanks marchnz
[MTCD Hardware Development] shtresatu:
I'm now in the same trouble with same board as yours. I can't enter maskrom, usb doesn't detect my px5 board. Otg cable soldered, but nothing... Is not seen by PC
[MTCD Hardware Development] cubanito_2k7:
Black Screen

Hi, do u know how get recovery mode in PX6 12.8 inches car radio? The screen is black after install the firmware, Thanks
[MTCD Hardware Development] Clandaries:
Can you please tell me how those tips are called or can you show me on Amazon?

Looks very nice and clean.

Thank you
[MTCD Hardware Development] scorillo_ro:
https://www.amazon.com/Solderless-F...=1522123431&sr=8-11&keywords=prototyping+wire
[MTCD Hardware Development] jacko5:
marchnz,

If i am reading your post correctly does this mean we will be able to update our px5 car radio's via USB ?

I have a rock chip android box for my television that i used to update vis OTG port on side of the android tv box and used to update it just like on the above link you have posted.

I am hoping to update my Xtrons 6.01 android car radio the same way if i have read your post correctly :)
[MTCD Hardware Development] marchnz:
Yes. Uses standard rockchip OTG tool.
[MTCD Hardware Development] jacko5:
Ok thanks.

Will we use a standard USB lead or a OTG like above ?

I can make a OTG board and lead like above but i am not sure where to get the parts needed in the UK.
[MTCD Hardware Development] scorillo_ro:
https://www.ebay.co.uk/itm/11K-to-1...hash=item256ff926a8:m:mz3Ssm_-31F59vLSpV4ZlbA

https://www.ebay.co.uk/itm/X-65-Bre...032717&hash=item2eece085cd:g:edMAAOSwmmxW6KwT

https://www.ebay.co.uk/itm/GOLD-USB...885?hash=item2cc4ba64e5:g:eek:wgAAOSwVqlaIUqA
[MTCD Hardware Development] jacko5:
Many thanks :D

I take it the board in the first thread above is the one out of any PX5 android car radio ?
[MTCD Hardware Development] Clandaries:
Do we need a male to male USB wire? Or does a normal USB wire work to?
[MTCD Hardware Development] scorillo_ro:
Yes, on the first page of the thread you will see PX5 boards, both the green one and the blue one.

Both are PX5 boards, just different versions...

---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------

No, you can cut and use any USB cable that have at least one male plugs at its ends.

If you don't have any spare USB cable to use and need to buy one, you can buy an male to male one just to cut it in two equal parts. Use one part to build the PX5 OTG cable and keep the other one for spare :)

I'll also recommend the cable to be not too long and not too thin.
[MTCD Hardware Development] moshe3150:
Tenksss very much, is work for me, px5 - bord kld

Tenksss very much, is work for me, px5 - bord kld

? note, the Resistors are 12K and 15k is work for me, 1/4 volt/Watts

And I Restore with RockChip tool 1.8 - this is the link for software

https://androidmtk.com/download-rockchip-batch-tool
[MTCD Hardware Development] typos1:
I dont think you needed to do it if you have a Klyde as another user (I m sure in this thread) has found that Klydes have USB OTG via one of the ports on the back.
[MTCD Hardware Development] marchnz:
GS reference hardware have OTG, but the unit MCU will timeout, powering OFF the SOM during a full flash. This method gets around that without mainboard mods to force +5v rail always on, so has less risk and is reliable.
[MTCD Hardware Development] moshe3150:
I tried to connect otg but the computer detected a connection without i could do if it is something, maybe send me your idea, anyway i left this connection and it works great
[MTCD Hardware Development] typos1:
One user reported that Klyde units have OTG on one of the connectors on the back and that he had no need to do this mod on his unit. I m certain it was in this thread.

EDIT: actually it wasnt in this thread, it was in your "PX5 Stuck In Bootloop" thread and it was [MENTION=4768815]scorillo_ro[/MENTION] who did it (luckily I usually screenshot useful posts).

Its not my idea, another user has done it.
[MTCD Hardware Development] marchnz:
I hear you. Take away from my comment is that native OTG is problematic in that the MCU thinks the SOM isn't responding so powers off the SOM during flash, breaking the flash process.

I got around this on my jig by forcing the +5v rail on, disabling MCU control. The USB cable method is easy.