STM32MP157 DK2

[Turbyho]

Neni to ono?
https://www.openstm32.org/forumthread7824

T



> 25. 12. 2019 v 18:17, Jaroslav Buchta <jaroslav.buchta na hascomp.cz>:
> 
> 
> Tak jeste jeden pokus o dotaz - postupuju podle tohoto navodu, vse se zda OK. https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157C-DK2/Let%27s_start/Populate_the_target_and_boot_the_image
> Proc sakra ten CubeProgrammer nevidi to zarizeni? Zkousel jsem ruzne firmware co se daji prostrednictvim ruznych aplikaci nainstalovat. Mozna je problem v tom DFU mode, ze to neni defaultni stav? Co s tim?
> Ve windows je to asi podobne, tam zkouseno i na jinem pocitaci a CubeProgrammer ho nevidi. Takova zajimavost tam je, ze kdyz pripojim jiny ST Link V2, tak aplikace vidi jen jeden, ale podle serioveho cisla prave ten V2-1 na DK2... 
> 
> Vypis chovani - zarizeni v systemu videt je, programmer ho nevidi...
> stm na stm-VirtualBox:~$ lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 003: ID 0483:3752 STMicroelectronics 
> Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> stm na stm-VirtualBox:~$ mc
> 
> stm na stm-VirtualBox:/etc/udev/rules.d$ STM32_Programmer_CLI -l usb      -------------------------------------------------------------------
>                         STM32CubeProgrammer v2.2.0                  
>       -------------------------------------------------------------------
> 
> =====  DFU Interface   =====
> 
>  No STM32 device in DFU mode connected
> 
> 
> 
> 
> Dne 23.12.2019 v 18:46 Jaroslav Buchta napsal(a):
>> Zdravim, vytahnul jsem ze supliku a premyslim, jestli to tam zase na pul roku neulozim... 
>> 
>> Coz o to, Linux funguje zatim uspokojive, zkusil jsem vyrobit i skrz BuilRoot a vypada nadejne, ale nejsem schopen se pripojit pres ST-Link a nahrat nebo dokonce ladit SW v M4. Z IDE to dopadne takhle: 
>> 
>> Open On-Chip Debugger 0.10.0+dev-01152-g3e96053-dirty (2019-10-01-16:48) 
>> Licensed under GNU GPL v2 
>> For bug reports, read 
>>     http://openocd.org/doc/doxygen/bugs.html
>> cortex_a interrupt mask on 
>> cortex_a interrupt mask on 
>> cortex_a domain access control fixup on 
>> cortex_a domain access control fixup on 
>> 3333 
>> none separate 
>> adapter speed: 8000 kHz 
>> adapter_nsrst_assert_width: 200 
>> adapter_nsrst_delay: 200 
>> none srst_pulls_trst 
>> srst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srst 
>> Info : Listening on port 64567 for tcl connections 
>> Info : Listening on port 62345 for telnet connections 
>> Info : STLINK V2J34S25 (API v2) VID:PID 0483:3752 
>> Info : using stlink api v2 
>> Info : Target voltage: 3.199476 
>> Info : clock speed 8000 kHz 
>> Info : SRST line released 
>> Info : stlink_connect(connect) 
>> Info : SWD DPIDR 0x6ba02477 
>> Info : STM32MP157CACx.cpu0: hardware has 6 breakpoints, 4 watchpoints 
>> Info : STM32MP157CACx.cpu1: hardware has 6 breakpoints, 4 watchpoints 
>> Error: Could not find MEM-AP to control the core 
>> Info : Listening on port 3334 for gdb connections 
>> Info : Listening on port 3333 for gdb connections 
>> ap 0 selected, csw 0x10006000 
>> 
>>  za chvili chybova hlaska, divna... viz priloha 
>> 
>> 
>> CubeProgrammer ted uz STLink ani nenajde, pred aktuializaci jeho firmware ho aspon nasel ale nedokazal se k cili pripojit 
>> 
>> ST-LinkUtility zarizeni najde, ale k procesoru se nepripoji v jakemkoli modu. 
>> 
>> Aktualizace firmware jde ve vsem na ruzne verze, ale nektera z nich zpusobi, ze LED na ST-Linku sviti cervene a linux nenabehne... VCP funguje. 
>> 
>> Ma to nekdo proslapnuty? Mozna je chyba na strane windows, zkusim kdyz tak dat systemovou zalohu pred tema pokusama ale nejak se mi to nezda celkove... 
>> 
>> 
>> 
>> _______________________________________________
>> HW-list mailing list  -  sponsored by www.HW.cz
>> Hw-list na list.hw.cz
>> http://list.hw.cz/mailman/listinfo/hw-list
> 
> _______________________________________________
> HW-list mailing list  -  sponsored by www.HW.cz
> Hw-list na list.hw.cz
> http://list.hw.cz/mailman/listinfo/hw-list
------------- další část ---------------
HTML příloha byla odstraněna...
URL: <http://list.hw.cz/pipermail/hw-list/attachments/20191226/d516b609/attachment.html>