lupyuen / pinetime-updater Goto Github PK

I can't figure out what's wrong now at this step. I don't see "done" and what I do get doesn't completely match your logs.

it outputs nothing after info:clock speed , the cables are connected

did i do something wrong (edit it still ran infinitime until i tried to flash something on it ).

Here are links to the latest bootloader and firmware:

Bootloader: https://github.com/JF002/pinetime-mcuboot-bootloader/releases/download/1.0.0/bootloader.bin

Application Firmware: https://github.com/JF002/InfiniTime/releases/download/1.0.0-RC4/pinetime-mcuboot-app-image-1.0.0.bin

I could make a pull request if you would like.

A more permanent solution over hardcoded values would be to check for the most recent stable release and set that for the url value. This would be easier for Infinitime than it would be for the bootloader.

I am going to contribute, as I stated on Twitter, regardless, but could you please tag this as Hacktoberfest friendly so I can use my pull requests toward Hacktoberfest?

PR to follow
with fresh raspbian install on Raspberry PI 1

libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./src -I./src -I./src/helper -DPKGDATADIR=\"/usr/local/share/openocd\" -DBINDIR=\"/usr/local/bin\" -I./jimtcl -I./jimtcl -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -g -O2 -MT src/flash/nor/jtagspi.lo -MD -MP -MF src/flash/nor/.deps/jtagspi.Tpo -c src/flash/nor/jtagspi.c -o src/flash/nor/jtagspi.o In file included from ./src/flash/common.h:21, from src/flash/nor/core.h:25, from src/flash/nor/imp.h:22, from src/flash/nor/jtagspi.c:22: src/flash/nor/jtagspi.c: In function ‘jtagspi_write_enable’: ./src/helper/log.h:133:2: error: ‘status’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 133 | log_printf_lf(LOG_LVL_ERROR, __FILE__, __LINE__, __func__, expr) | ^~~~~~~~~~~~~ src/flash/nor/jtagspi.c:262:11: note: ‘status’ was declared here 262 | uint32_t status; | ^~~~~~ src/flash/nor/jtagspi.c: In function ‘jtagspi_wait’: src/flash/nor/jtagspi.c:249:15: error: ‘status’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 249 | if ((status & SPIFLASH_BSY_BIT) == 0) { | ~~~~~~~~^~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors

This is a great project. Flashing the bootloader and InifiniTime is really easy, but I miss the bootloader logo flasher.
After using the updater I get a garbage screen when booting the PineTime. I assume this is because of the missing bootloader logo.

I'm on raspberry pi
do you have an idea ?

Hi, I'm trying to flash a customized InfiniTime to my PineTime dev kit watch. I was able to flash the latest firmware (option 2), but when I try to download from URL/file the watch is perpetually loading the starting screen. I tried to use the InfiniTime github repository, but had the same error. I am thinking I am typing the wrong path, but am not sure what the right path should be. Would you know where I'm going wrong?

Steps to replicate:

1. Choose "Download from URL"

2. Enter the InfiniTime github repository URL:
   https://github.com/InfiniTimeOrg/InfiniTime

I'm just got my pine time about a week ago and an st link v2 and have been trying to reprogram the pinetime. Here is the read from the terminal. Im running manjaro btw

----- Downloading https://github.com/lupyuen/pinetime-rust-mynewt/releases/download/v4.1.7/mynewt_nosemi.elf.bin to /tmp/mynewt_nosemi.elf.bin... (If it stops here, URL is invalid)

• wget -q https://github.com/lupyuen/pinetime-rust-mynewt/releases/download/v4.1.7/mynewt_nosemi.elf.bin -O /tmp/mynewt_nosemi.elf.bin
• '[' '!' -f /tmp/mynewt_nosemi.elf.bin ']'
• set +x

----- Flashing /tmp/mynewt_nosemi.elf.bin to address 0x0...

• xpack-openocd/bin/openocd -c ' set filename "/tmp/mynewt_nosemi.elf.bin" ' -c ' set address "0x0" ' -f scripts/swd-stlink.ocd -f scripts/flash-program.ocd
  xPack OpenOCD, x86_64 Open On-Chip Debugger 0.10.0+dev-00378-ge5be992df (2020-06-26-09:27)
  Licensed under GNU GPL v2
  For bug reports, read
  http://openocd.org/doc/doxygen/bugs.html
  /tmp/mynewt_nosemi.elf.bin
  0x0

nRF52 device has a CTRL-AP dedicated to recover the device from AP lock.
A high level adapter (like a ST-Link) you are currently using cannot access
the CTRL-AP so 'nrf52_recover' command will not work.
Do not enable UICR APPROTECT.

force hard breakpoints
Error: target voltage may be too low for reliable debugging
Error: init mode failed (unable to connect to the target)