| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 172
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,724
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 266
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 121
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 217,088
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 222
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 305
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,093
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 946
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 609
|
|
|
| Samsung 970 EVO SSD 1TB - M.2 NVMe works on workstation but not Pinebook Pro |
|
Posted by: mgchristensen - 12-28-2019, 02:10 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (4)
|
 |
I have a Samsung 970 EVO SSD 1TB - M.2 NVMe in a SSK Aluminum M.2 NVME external case, see here for the product on Amazon: https://www.amazon.com/gp/product/B07MNF...UTF8&psc=1
I installed the gnome-disks utility on the Pinebook Pro to assist me with this.
NVMe and enclosure work without problem on my workstation running Fedora 30. Format, partition, read, write, all good.
dmesg reports:
[341405.622922] usb 6-2: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[341405.635207] usb 6-2: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.06
[341405.635211] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[341405.635214] usb 6-2: Product: SSK Storage
[341405.635215] usb 6-2: Manufacturer: SSK
[341405.635217] usb 6-2: SerialNumber: DF56419883E5B
[341405.823661] usb 6-2: USB controller 0000:0c:00.0 does not support streams, which are required by the UAS driver.
[341405.823667] usb 6-2: Please try an other USB controller if you wish to use UAS.
[341405.823671] usb-storage 6-2:1.0: USB Mass Storage device detected
[341405.824043] scsi host15: usb-storage 6-2:1.0
[341406.842939] scsi 15:0:0:0: Direct-Access SSK 0206 PQ: 0 ANSI: 6
[341406.843583] sd 15:0:0:0: Attached scsi generic sg8 type 0
[341409.512535] sd 15:0:0:0: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[341409.515399] sd 15:0:0:0: [sdg] Write Protect is off
[341409.515407] sd 15:0:0:0: [sdg] Mode Sense: 53 00 00 08
[341409.518240] sd 15:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[341409.528580] sdg: sdg1
[341409.534874] sd 15:0:0:0: [sdg] Attached SCSI disk
However, the Pinebook Pro recognizes the enclosure when plugged in to a USB 3 port, assigning it the device file /dev/sda, but gnome-disks reports "No Media". dmesg reports:
[ 1490.403480] usb 2-1.1: new high-speed USB device number 4 using ehci-platform
[ 1490.564908] usb 2-1.1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.06
[ 1490.565662] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1490.566313] usb 2-1.1: Product: SSK Storage
[ 1490.566693] usb 2-1.1: Manufacturer: SSK
[ 1490.567050] usb 2-1.1: SerialNumber: DF56419883E5B
[ 1490.569695] scsi host0: uas
[ 1490.571524] scsi 0:0:0:0: Direct-Access SSK 0206 PQ: 0 ANSI: 6
[ 1490.573978] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1499.433316] sd 0:0:0:0: [sda] Unit Not Ready
[ 1499.433767] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.434347] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.435414] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.436252] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.436829] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.437890] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.438720] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.439285] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.440892] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[ 1499.441442] sd 0:0:0:0: [sda] 0-byte physical blocks
[ 1499.442261] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[ 1499.443012] sd 0:0:0:0: [sda] Asking for cache data failed
[ 1499.443537] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 1499.444514] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
[ 1499.485275] sd 0:0:0:0: [sda] Unit Not Ready
[ 1499.485675] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.486252] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.487290] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.488131] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.488711] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.489911] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.490756] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.491336] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.494885] sd 0:0:0:0: [sda] Attached SCSI disk
I note that there is a package named nvme-cli, is this necessary?
Same problem with the default operating system, and with an install of the Mandriva KDE image.
Is this the problem: [ 1499.490756] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current], is the Pinebook Pro not capable of supplying sufficient current for this device?
Thanks for any ideas offered!
|
|
|
|
| Pinebook won't boot (from eMMC) |
|
Posted by: brent.thierens - 12-28-2019, 01:30 PM - Forum: Linux on Pinebook Pro
- Replies (4)
|
 |
I tried to go back to the default install of Debian. However, after dd to the eMMC, the PBP doesn't want to boot. The active LED goes on and flickers for some time, the backlight goes on, then the power LED goes out and after some time the backlight goes out as well. Then everything starts again.
I'm coming from Manjaro if that matters. Any ideas on how to recover from this (SD boot works fine)
|
|
|
|
| Project Review |
|
Posted by: moriel5 - 12-28-2019, 11:45 AM - Forum: General Discussion on PineTime
- Replies (7)
|
 |
Hello everyone.
While I'm no developer (yet, I need to be more organized to get to that point), I do have the know-how to be able to test the landscape for the PineTime, and therefore I had ordered a developer kit from the Pine shop, once I had realized that it is possible to do so.
To be honest, originally I was contemplating asking for a review sample of the development kit in order to "report", so to speak (english is not my native language), on the project's progress, however before I was able to come up with an idea of how to do so, it became possible order one from the store, and I decided, "whatever, this way I can also financially support Pine64, even though this is a stretch for my current financial situation".
So in short, I intend to start an ongoing review of the PineTime and it's development, once I receive my kit.
As for how often I shall post an update (I do not often have proper access to both my laptop and a stable internet connection at the same time), and where I shall do so (in addition to here), that I'll be glad to receive the community's opinion (I am currently thinking of the LinusTechTips and XDA-Developers forums).
I'd rather not post on Twitter or Telegram(no FaceBook, Mastodon, or most social platforms), though I may do so.
And I'd be very happy to receive comments and constructive criticism on my initiative.
|
|
|
|
| When would it ship? |
|
Posted by: TG127 - 12-28-2019, 09:17 AM - Forum: General Discussion on PinePhone
- Replies (22)
|
 |
Hello all,
If I were to pre-order the Braveheart edition today, would it still ship in mid to late January or would it be after the Chinese New Year?
Also, how likely is it that there will be import taxes? (I’m in the US by the way)
Thanks
|
|
|
|
Rockchip 3530 |
|
Posted by: thewonderer - 12-28-2019, 07:42 AM - Forum: General Discussion on ROCK64
- Replies (5)
|
 |
Hi, been using my 3328 rock64 v2 for a year now and on the whole found it suited to my needs and stable. I see that rockchip have a bunch of new SOCs ready for 2020 and wondered if there will be a replacent for the rock64 and rock64pro? The 3530 looks like a nice step up for the rock64.
|
|
|
|
| Flashing not working |
|
Posted by: yokonav - 12-28-2019, 06:49 AM - Forum: General Discussion on PineTime
- Replies (13)
|
 |
I am using OpenOCD with Raspberry Pi 4 to flash the PineTime dev kit. It worked for a day properly. I tested bluetooth and LCD example code using Zephyr RTOS. But all of the sudden it stopped working.
What I noticed when connecting SWD wires the LCD backlight turns on and also when putting the back cover (no SWD connection) the motor starts vibrating. Is it short-circuit? What should I check? Investing the OpenOCD debug log (below) it seems chip is not getting acknowledged.
Open On-Chip Debugger 0.10.0+dev-00985-g2dc88e14 (2019-12-25-21:43)
User : 13 9 options.c:63 configuration_output_handler(): debug_level: 4
User : 14 9 options.c:63 configuration_output_handler():
Debug: 15 9 options.c:187 add_default_dirs(): bindir=/usr/local/bin
Debug: 16 9 options.c:188 add_default_dirs(): pkgdatadir=/usr/local/share/openocd
Debug: 17 9 options.c:189 add_default_dirs(): exepath=/home/pi/openocd/src
Debug: 18 9 options.c:190 add_default_dirs(): bin2data=../share/openocd
Debug: 19 9 configuration.c:42 add_script_search_dir(): adding /root/.openocd
Debug: 20 9 configuration.c:42 add_script_search_dir(): adding /home/pi/openocd/src/../share/openocd/site
Debug: 21 9 configuration.c:42 add_script_search_dir(): adding /home/pi/openocd/src/../share/openocd/scripts
Debug: 22 10 configuration.c:97 find_file(): found /home/pi/swd-pi.ocd
Debug: 23 10 command.c:143 script_debug(): command - interface interface bcm2835gpio
Debug: 25 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_jtag_nums'...
Debug: 26 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_tck_num'...
Debug: 27 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_tms_num'...
Debug: 28 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_tdo_num'...
Debug: 29 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_tdi_num'...
Debug: 30 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_swd_nums'...
Debug: 31 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_swclk_num'...
Debug: 32 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_swdio_num'...
Debug: 33 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_srst_num'...
Debug: 34 10 command.c:354 register_command_handler(): registering 'bcm2835gpio_trst_num'...
Debug: 35 11 command.c:354 register_command_handler(): registering 'bcm2835gpio_speed_coeffs'...
Debug: 36 11 command.c:354 register_command_handler(): registering 'bcm2835gpio_peripheral_base'...
Debug: 37 11 command.c:143 script_debug(): command - bcm2835gpio_peripheral_base bcm2835gpio_peripheral_base 0x3F000000
Debug: 39 11 command.c:143 script_debug(): command - bcm2835gpio_speed_coeffs bcm2835gpio_speed_coeffs 194938 48
Debug: 41 11 command.c:143 script_debug(): command - bcm2835gpio_swd_nums bcm2835gpio_swd_nums 20 21
Debug: 43 11 command.c:143 script_debug(): command - bcm2835gpio_srst_num bcm2835gpio_srst_num 18
Debug: 45 11 command.c:143 script_debug(): command - transport transport select swd
Debug: 46 11 command.c:354 register_command_handler(): registering 'swd'...
Debug: 47 11 bitbang.c:402 bitbang_swd_init(): bitbang_swd_init
Debug: 48 11 configuration.c:97 find_file(): found /home/pi/openocd/tcl/target/nrf52.cfg
Debug: 49 12 configuration.c:97 find_file(): found /home/pi/openocd/tcl/target/swj-dp.tcl
Debug: 50 12 command.c:143 script_debug(): command - transport transport select
Debug: 51 12 command.c:143 script_debug(): command - transport transport select
Debug: 52 12 command.c:143 script_debug(): command - transport transport select
Debug: 53 13 command.c:143 script_debug(): command - transport transport select
Debug: 54 13 command.c:143 script_debug(): command - swd swd newdap nrf52 cpu -expected-id 0x2ba01477
Debug: 55 13 tcl.c:567 jim_newtap_cmd(): Creating New Tap, Chip: nrf52, Tap: cpu, Dotted: nrf52.cpu, 2 params
Debug: 56 13 core.c:1373 jtag_tap_init(): Created Tap: nrf52.cpu @ abs position 0, irlen 0, capture: 0x0 mask: 0x0
Debug: 57 13 command.c:143 script_debug(): command - dap dap create nrf52.dap -chain-position nrf52.cpu
Debug: 58 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 59 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 60 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 61 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 62 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 63 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 64 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 65 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 66 13 command.c:354 register_command_handler(): registering 'nrf52.dap'...
Debug: 67 13 command.c:143 script_debug(): command - target target create nrf52.cpu cortex_m -dap nrf52.dap
Debug: 68 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 69 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 70 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 71 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 72 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 73 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 74 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 75 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 76 14 command.c:354 register_command_handler(): registering 'arm'...
Debug: 77 14 command.c:354 register_command_handler(): registering 'tpiu'...
Debug: 78 14 command.c:354 register_command_handler(): registering 'itm'...
Debug: 79 14 command.c:354 register_command_handler(): registering 'itm'...
Debug: 80 14 command.c:354 register_command_handler(): registering 'cortex_m'...
Debug: 81 14 command.c:354 register_command_handler(): registering 'cortex_m'...
Debug: 82 14 command.c:354 register_command_handler(): registering 'cortex_m'...
Debug: 83 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 84 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 85 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 86 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 87 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 88 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 89 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 90 14 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 91 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 92 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 93 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 94 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 95 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 96 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 97 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 98 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 99 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 100 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 101 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 102 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 103 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 104 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 105 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 106 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 107 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 108 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 109 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 110 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 111 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 112 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 113 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 114 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 115 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 116 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 117 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 118 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 119 15 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 120 16 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 121 16 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 122 16 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 123 16 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 124 16 command.c:354 register_command_handler(): registering 'nrf52.cpu'...
Debug: 125 16 command.c:143 script_debug(): command - adapter_khz adapter_khz 1000
Debug: 127 16 core.c:1705 jtag_config_khz(): handle jtag khz
Debug: 128 16 core.c:1668 adapter_khz_to_speed(): convert khz to interface specific speed value
Debug: 129 16 core.c:1668 adapter_khz_to_speed(): convert khz to interface specific speed value
Debug: 130 16 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu configure -work-area-phys 0x20000000 -work-area-size 0x4000 -work-area-backup 0
Debug: 131 16 target.c:1961 target_free_all_working_areas_restore(): freeing all working areas
Debug: 132 16 target.c:1961 target_free_all_working_areas_restore(): freeing all working areas
Debug: 133 16 target.c:1961 target_free_all_working_areas_restore(): freeing all working areas
Debug: 134 16 command.c:143 script_debug(): command - transport transport select
Debug: 135 16 command.c:143 script_debug(): command - cortex_m cortex_m reset_config sysresetreq
Debug: 137 16 command.c:143 script_debug(): command - flash flash bank nrf52.flash nrf5 0x00000000 0 1 1 nrf52.cpu
Debug: 139 16 command.c:354 register_command_handler(): registering 'nrf5'...
Debug: 140 16 command.c:354 register_command_handler(): registering 'nrf5'...
Debug: 141 17 command.c:354 register_command_handler(): registering 'nrf51'...
Debug: 142 17 command.c:354 register_command_handler(): registering 'nrf51'...
Debug: 143 17 tcl.c:1156 handle_flash_bank_command(): 'nrf5' driver usage field missing
Debug: 144 17 command.c:143 script_debug(): command - flash flash bank nrf52.uicr nrf5 0x10001000 0 1 1 nrf52.cpu
Debug: 146 17 command.c:376 register_command(): command 'nrf5' is already registered in '<global>' context
Debug: 147 17 command.c:376 register_command(): command 'mass_erase' is already registered in 'nrf5' context
Debug: 148 17 command.c:376 register_command(): command 'info' is already registered in 'nrf5' context
Debug: 149 17 command.c:376 register_command(): command 'nrf51' is already registered in '<global>' context
Debug: 150 17 command.c:376 register_command(): command 'mass_erase' is already registered in 'nrf51' context
Debug: 151 17 command.c:376 register_command(): command 'info' is already registered in 'nrf51' context
Debug: 152 17 tcl.c:1156 handle_flash_bank_command(): 'nrf5' driver usage field missing
Debug: 153 17 command.c:143 script_debug(): command - reset_config reset_config srst_only srst_nogate
Debug: 155 17 command.c:143 script_debug(): command - adapter_nsrst_delay adapter_nsrst_delay 100
Debug: 157 17 command.c:143 script_debug(): command - adapter_nsrst_assert_width adapter_nsrst_assert_width 100
Debug: 159 17 command.c:143 script_debug(): command - init init
Debug: 161 17 command.c:143 script_debug(): command - target target init
Debug: 163 17 command.c:143 script_debug(): command - target target names
Debug: 164 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu cget -event gdb-flash-erase-start
Debug: 165 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu configure -event gdb-flash-erase-start reset init
Debug: 166 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu cget -event gdb-flash-write-end
Debug: 167 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu configure -event gdb-flash-write-end reset halt
Debug: 168 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu cget -event gdb-attach
Debug: 169 18 command.c:143 script_debug(): command - nrf52.cpu nrf52.cpu configure -event gdb-attach halt
Debug: 170 18 target.c:1423 handle_target_init_command(): Initializing targets...
Debug: 171 18 semihosting_common.c:97 semihosting_common_init():
Debug: 172 18 command.c:354 register_command_handler(): registering 'target_request'...
Debug: 173 18 command.c:354 register_command_handler(): registering 'trace'...
Debug: 174 18 command.c:354 register_command_handler(): registering 'trace'...
Debug: 175 18 command.c:354 register_command_handler(): registering 'fast_load_image'...
Debug: 176 18 command.c:354 register_command_handler(): registering 'fast_load'...
Debug: 177 18 command.c:354 register_command_handler(): registering 'profile'...
Debug: 178 18 command.c:354 register_command_handler(): registering 'virt2phys'...
Debug: 179 19 command.c:354 register_command_handler(): registering 'reg'...
Debug: 180 19 command.c:354 register_command_handler(): registering 'poll'...
Debug: 181 19 command.c:354 register_command_handler(): registering 'wait_halt'...
Debug: 182 19 command.c:354 register_command_handler(): registering 'halt'...
Debug: 183 19 command.c:354 register_command_handler(): registering 'resume'...
Debug: 184 19 command.c:354 register_command_handler(): registering 'reset'...
Debug: 185 19 command.c:354 register_command_handler(): registering 'soft_reset_halt'...
Debug: 186 19 command.c:354 register_command_handler(): registering 'step'...
Debug: 187 19 command.c:354 register_command_handler(): registering 'mdd'...
Debug: 188 19 command.c:354 register_command_handler(): registering 'mdw'...
Debug: 189 19 command.c:354 register_command_handler(): registering 'mdh'...
Debug: 190 19 command.c:354 register_command_handler(): registering 'mdb'...
Debug: 191 19 command.c:354 register_command_handler(): registering 'mwd'...
Debug: 192 19 command.c:354 register_command_handler(): registering 'mww'...
Debug: 193 19 command.c:354 register_command_handler(): registering 'mwh'...
Debug: 194 19 command.c:354 register_command_handler(): registering 'mwb'...
Debug: 195 19 command.c:354 register_command_handler(): registering 'bp'...
Debug: 196 19 command.c:354 register_command_handler(): registering 'rbp'...
Debug: 197 19 command.c:354 register_command_handler(): registering 'wp'...
Debug: 198 19 command.c:354 register_command_handler(): registering 'rwp'...
Debug: 199 19 command.c:354 register_command_handler(): registering 'load_image'...
Debug: 200 19 command.c:354 register_command_handler(): registering 'dump_image'...
Debug: 201 19 command.c:354 register_command_handler(): registering 'verify_image_checksum'...
Debug: 202 19 command.c:354 register_command_handler(): registering 'verify_image'...
Debug: 203 20 command.c:354 register_command_handler(): registering 'test_image'...
Debug: 204 20 command.c:354 register_command_handler(): registering 'reset_nag'...
Debug: 205 20 command.c:354 register_command_handler(): registering 'ps'...
Debug: 206 20 command.c:354 register_command_handler(): registering 'test_mem_access'...
Info : 207 20 bcm2835gpio.c:450 bcm2835gpio_init(): BCM2835 GPIO JTAG/SWD bitbang driver
Info : 208 20 bcm2835gpio.c:458 bcm2835gpio_init(): SWD only mode enabled (specify tck, tms, tdi and tdo gpios to add JTAG mode)
Debug: 209 20 bcm2835gpio.c:525 bcm2835gpio_init(): saved pinmux settings: tck 0 tms 0 tdi 0 tdo 0 trst 0 srst 4
Debug: 210 20 bitbang.c:457 bitbang_switch_to_swd(): bitbang_switch_to_swd
Debug: 211 20 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 212 20 core.c:1668 adapter_khz_to_speed(): convert khz to interface specific speed value
Debug: 213 20 core.c:1672 adapter_khz_to_speed(): have interface set up
Debug: 214 20 core.c:1668 adapter_khz_to_speed(): convert khz to interface specific speed value
Debug: 215 20 core.c:1672 adapter_khz_to_speed(): have interface set up
Info : 216 20 core.c:1450 adapter_init(): clock speed 1004 kHz
Debug: 217 20 openocd.c:141 handle_init_command(): Debug Adapter init complete
Debug: 218 20 command.c:143 script_debug(): command - transport transport init
Debug: 220 20 transport.c:239 handle_transport_init(): handle_transport_init
Debug: 221 20 command.c:143 script_debug(): command - dap dap init
Debug: 223 20 arm_dap.c:106 dap_init_all(): Initializing all DAPs ...
Debug: 224 20 bitbang.c:432 bitbang_swd_switch_seq(): bitbang_swd_switch_seq
Debug: 225 20 bitbang.c:440 bitbang_swd_switch_seq(): JTAG-to-SWD
Debug: 226 20 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 227 21 bitbang.c:469 bitbang_swd_read_reg(): bitbang_swd_read_reg
Debug: 228 21 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 229 21 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 230 21 bitbang.c:496 bitbang_swd_read_reg(): JUNK DP read reg 0 = ffffffff
Debug: 231 21 bitbang.c:519 bitbang_swd_read_reg(): No valid acknowledge: ack=7
Debug: 232 21 bitbang.c:528 bitbang_swd_write_reg(): bitbang_swd_write_reg
Debug: 233 21 bitbang.c:532 bitbang_swd_write_reg(): Skip bitbang_swd_write_reg because queued_retval=7
Debug: 234 21 bitbang.c:580 bitbang_swd_run_queue(): bitbang_swd_run_queue
Debug: 235 21 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 236 21 bitbang.c:587 bitbang_swd_run_queue(): SWD queue return value: 07
Debug: 237 21 command.c:629 run_command(): Command 'dap init' failed with error code 7
User : 238 21 command.c:694 command_run_line():
Debug: 239 21 command.c:629 run_command(): Command 'init' failed with error code -4
User : 240 22 command.c:694 command_run_line():
Debug: 241 22 target.c:1961 target_free_all_working_areas_restore(): freeing all working areas
Debug: 242 22 bitbang.c:432 bitbang_swd_switch_seq(): bitbang_swd_switch_seq
Debug: 243 22 bitbang.c:444 bitbang_swd_switch_seq(): SWD-to-JTAG
Debug: 244 22 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 245 22 bitbang.c:580 bitbang_swd_run_queue(): bitbang_swd_run_queue
Debug: 246 22 bitbang.c:409 bitbang_exchange(): bitbang_exchange
Debug: 247 22 bitbang.c:587 bitbang_swd_run_queue(): SWD queue return value: 00
|
|
|
|
|