Kureigu07

Yeah, easily within a 3rd of the price, the LCD is small and low res, the chip is only a few bucks in low volume, and it handles everything, USB, LCD, Digitizer. Without cloning it, the challenge would indeed be decent firmware and software.

Info : SWD DPIDR 0x2ba01477 Info : m484sidae.cpu: hardware has 6 breakpoints, 4 watchpoints Info : starting gdb server for m484sidae.cpu on 3333 Info : Listening on port 3333 for gdb connections target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x00007974 msp: 0x20022698 AP ID register 0x24770011 Type is MEM-AP AHB3 MEM-AP BASE 0xe00ff003 Valid ROM table present Component base address 0xe00ff000 Peripheral ID 0x04000bb4c4 Designer is 0x4bb, ARM Ltd. Part is 0x4c4, Cortex-M4 ROM (ROM Table) Component class is 0x1, ROM table MEMTYPE system memory present on bus ROMTABLE[0x0] = 0xfff0f003 Component base address 0xe000e000 Peripheral ID 0x04000bb00c Designer is 0x4bb, ARM Ltd. Part is 0xc, Cortex-M4 SCS (System Control Space) Component class is 0xe, Generic IP component ROMTABLE[0x4] = 0xfff02003 Component base address 0xe0001000 Peripheral ID 0x04003bb002 Designer is 0x4bb, ARM Ltd. Part is 0x2, Cortex-M3 DWT (Data Watchpoint and Trace) Component class is 0xe, Generic IP component ROMTABLE[0x8] = 0xfff03003 Component base address 0xe0002000 Peripheral ID 0x04002bb003 Designer is 0x4bb, ARM Ltd. Part is 0x3, Cortex-M3 FPB (Flash Patch and Breakpoint) Component class is 0xe, Generic IP component ROMTABLE[0xc] = 0xfff01003 Component base address 0xe0000000 Peripheral ID 0x04003bb001 Designer is 0x4bb, ARM Ltd. Part is 0x1, Cortex-M3 ITM (Instrumentation Trace Module) Component class is 0xe, Generic IP component ROMTABLE[0x10] = 0xfff41003 Component base address 0xe0040000 Peripheral ID 0x04000bb9a1 Designer is 0x4bb, ARM Ltd. Part is 0x9a1, Cortex-M4 TPIU (Trace Port Interface Unit) Component class is 0x9, CoreSight component Type is 0x11, Trace Sink, Port ROMTABLE[0x14] = 0xfff42003 Component base address 0xe0041000 Peripheral ID 0x04000bb925 Designer is 0x4bb, ARM Ltd. Part is 0x925, Cortex-M4 ETM (Embedded Trace) Component class is 0x9, CoreSight component Type is 0x13, Trace Source, Processor ROMTABLE[0x18] = 0x0 End of ROM table > reg ===== arm v7m registers (0) r0 (/32): 0x00000000 (1) r1 (/32): 0x00000000 (2) r2 (/32): 0x00000000 (3) r3 (/32): 0x00000000 (4) r4 (/32): 0x00000000 (5) r5 (/32): 0x00000000 (6) r6 (/32): 0x00000000 (7) r7 (/32): 0x00000000 (8) r8 (/32): 0x00000000 (9) r9 (/32): 0x00000000 (10) r10 (/32): 0x00000000 (11) r11 (/32): 0x00000000 (12) r12 (/32): 0x00000000 (13) sp (/32): 0x20022698 (14) lr (/32): 0xffffffff (15) pc (/32): 0x00007974 (16) xPSR (/32): 0x01000000 (17) msp (/32): 0x20022698 (18) psp (/32): 0x00000000 (19) primask (/1): 0x00 (20) basepri (/8): 0x00 (21) faultmask (/1): 0x00 (22) control (/2): 0x00 (23) d0 (/64): 0x0000000000000000 (24) d1 (/64): 0x0000000000000000 (25) d2 (/64): 0x0000000000000000 (26) d3 (/64): 0x0000000000000000 (27) d4 (/64): 0x0000000000000000 (28) d5 (/64): 0x0000000000000000 (29) d6 (/64): 0x0000000000000000 (30) d7 (/64): 0x0000000000000000 (31) d8 (/64): 0x0000000000000000 (32) d9 (/64): 0x0000000000000000 (33) d10 (/64): 0x0000000000000000 (34) d11 (/64): 0x0000000000000000 (35) d12 (/64): 0x0000000000000000 (36) d13 (/64): 0x0000000000000000 (37) d14 (/64): 0x0000000000000000 (38) d15 (/64): 0x0000000000000000 (39) fpscr (/32): 0x00000000 ===== Cortex-M DWT registers Should it be 0x00000000 for bank 1, and 0x0000000000000000 for bank 2?

This was a couple days ago, but I managed to pull 512KB (the size of the ROM) from 0x0. But the disassembler didn't make much sense of it. TBH i'm not even sure if 0x0 would be the correct address to read from. https://www.nuvoton.com/products/microcontrollers/arm-cortex-m4-mcus/m484-usb-hs-otg-series/?__locale=en https://developer.arm.com/documentation/ddi0439/b/Debug/About-debug/Cortex-M4-ROM-table-identification-and-entries?lang=en

What would be a way to test that?

Hi folks, wasn't sure which cat to put this in, hopefully ok... I've got a bricked (bootloop) Elgato Stream Deck Mini (20GAI9901), which doesn't initialize the USB controller. So I would like to try (re)flashing the firmware onto it via an ICP, however Elgato will not provide the firmware. I have been able to communicate with the Nuvoton M484SIADE (Cortex M4) microprocessor onboard via the debug interface (SWD) with a RPi using OpenOCD. I'm hoping that someone would be willing to do an image dump from an out of warranty device for me try burning to my device. "Out of warranty" purely because this will require opening the SDM. If you are using OpenOCD, details are as follows; transport select swd set CHIPNAME m484sidae source [find target/numicro.cfg] J2 Pins; >VCC CLK DI/O Reset GND Thanks for reading, and if any more details are required please let me know Best regards

I've measured power at some resistors while trying to trace the enable signal, but if you've got any in mind to check please do let me know. On another note, if anyone with a working 1080 could measure the resistance from ground to the main cap's after the VRMs and post the results I would greatly appreciate it.

Nope, fan doesn't spin, all components and traces look perfect. The card is seated fine.

Currently running my old GTX 770 in the PC that this (1080) card failed in, and doing all the testing of the 1080 on another test system, so unfortunately its not the PSU connectors.

Not that I've been able to find. The board is; V336 VER 4.0 JH M3 94V-0 E2030435 I'll try contacting MSI, it is very unlikely that they'll release the full schematic, but if I'm luck I might be able to at least get some data for the automated probe points. The best I can offer right now is some photos of a Gaming X model which is practically identical (just has some additional hardware to support the LEDs) https://www.techpowerup.com/reviews/MSI/GTX_1080_Gaming_X/3.html

Hi all, I've got a MSI GTX 1080 Armor with zero output and no fan spin. All of the main power rails are present and the 3 fuses are good. The uP9511 PWM Controller has 0V on the Enable pin, so it is definitely in a fault state as it requires 0.4v to turn on, but so far I have been unable to find the problem. Is there a list of generic test points, for resistance and voltages. Or some written testing methodology that I can follow? So far I have tested the following; (All resistance values are from the ground plane to the component) PCIE Pins B1,B2,A2,B3,A3 ~M B8 29.9K A9&A10 131.7K B10 ~M Fuses, RS1,2,3 195Ω uP9511 1 REFIN 0.831V 2 VREF 2.00V 12 5VCC 4.96V 27 VINMON 1.20V 36 EN 0.00V 38 PGOOD 0.00V Is there any good spots for checking for shorts on the memory and GPU? Is it worth while pulling the VRM caps and chokes and testing them out of circuit?

Hahaha not my first post.

Those speakers! I'm so tired of having poor audio volume and quality on portable devices.

Thanks to Darrin Lynch for joining us today. And thank you Linus for this awesome giveaway.