Tinker Board 3N R1.02 - Cannot start TinkerBoard in OTG mode for OS upload

[Jovan 0]

After successfully using TinkerBoard 2S in production, we wanted to evaluate TinkerBoard 3N and bought it.

However, using the same setup (macOS and USB-C <-> USB-C cable directly connected to the mac laptop), we cannot get it to be recognized as a storage device.

We're following the same procedure as we do with the TinkerBoard 2S (unplug everything from TinkerBoard, connect the USB-C cable to board and laptop using the OTG port and then connecting the power supply.

But nothing happens when we connect the board...

 

Can you suggest what can we try to resolve the issue?

Photo of the board itself is attached if that helps in any way...

 

Thanks

 

[tooz 47]

hello @Jovan, 

the cc logic controllers between tinker board 2s and tinker board 3n are different -- for tinker board 3n, if both the ports connected are type c port, the controller will not be able to recognise which port should be in host mode and which port should be in device mode. 

for tinker board 3n i would recommend to connect type c port from tinker board 3n to type a (macbook)

 

[Jovan 0]

Thanks for the feedback.

On Mac I had to use USB Hub to get USB-A port. Tried two without any success. Result is the same.

Then I tried on the Windows machine and it got recognized, but not as a storage device, but as "Unknown Device", which then was not available for flashing in BalenaEther as it's not recognized as a storage device.

Any further help please? Is there any drivers I should install on Win?

 

Thanks again

 

[tooz 47]

hello @Jovan, 

please remove the yellow jumper cap, and re-do the procedure (connecting tinker board 3n to the computer) again

booting without the jumper cap attached so the tinker board 3n can start on uboot and the board should be in ums mode

 

 

[Jovan 0]

Thanks for really fast answers.

Unfortunatelly... still nothing.

So, I've removed jumper from Mask2 pins.

What about the Recovery pins, should I have the jumper there ON or no)?

And also the Mask1 dip-switch?

[tooz 47]

hello @Jovan, 

1. the connection should be type c port (tinker board 3n) to type a port (macbook)

2. both the jumper caps need to be removed 

3. no need to adjust mask1 dip switch 

 

[Jovan 0]

I've done all that, both jumper caps removed, except Macbook does not have USB-A port, so have to use USB hub for that.

Also tried on Windows, which now does not recognize anything at all 😞

[Jovan 0]

I've attached the latest setup photo for reference.

Red light is there, USB-C -> USB-A, but nothing detected by Win, and nothing in device manager.

Edited April 3 by Jovan

[tooz 47]

hello @Jovan, 

was the led (led1) on while using?

please check if you're able to use the adb with mask2 cap on while booting?

[Jovan 0]

I'm not sure I understand the last question, but I've never "used" the board in term of booting the OS.

As soon as I plug in the power supply, red led turns on. It was on also before I've removed the mask2 jumper.

So, it's always on when I connect the power supply, no matter if USB cable is connected or not.

[tooz 47]

hello @Jovan, 

given the clues i can only suggest to 

1. restart the windows pc

2. change the type a - type c cable

tinker board 3n should be recognised in device manager, as same as tinker board 2s

(the quickest way to debug the environment is to plug a usb drive to the same port of the windows pc and see if it's working)

[Jovan 0]

Thanks for all the great feedback.

There is always an option it's a faulty one.

 

[Jovan 0]

I just got and tried a new, second one (same model, Tinker Board 3N).

Removed the jumper cap, plugged into the mac and it immediately recognized and works like a charm.

Looks like the first one needs to be RMA.

 

Thanks

 

[tooz 47]

hello @Jovan, 

thanks for letting me know.  also, could you try use flash a sd card with v.1.0.17, and see if the first tinker board 3n can boot from sd and then flash emmc? 

Tinker Board 3N Debian 11 (Kernel 5.10) V1.0.17

[Jovan 0]

I can, just to know the behaviour, but in production we deliver it to customer without the SD Card with the OS on the eMMC 😞