Skip to content

Commit

Permalink
STABLE flwrite erase and new keyboard-await blinker.
Browse files Browse the repository at this point in the history
copy_to_ram mode tested good.

Very brief testing.  Blinks every 10 seconds (or so)
while waiting for keyboard input.

More like 'stable' with a very small 's' there.

Expecting it to 'suddenly not work as it had been'
due to luck alone. ;)

The RPi Pico RP2040 board is curiously presenting to Linux
as /dev/ttyACM1 (and the transition was noted). Not sure
what's happening there.

There is no /dev/ttyACM0 present (now) but that was the
device until yesterday.

	modified:   .gitignore
	modified:   17-camelforth-a.d/pico-examples/camelforth-a/forth/forth.c
	modified:   doc/results_debugging.txt

On branch erase_sector-a
  • Loading branch information
wa1tnr committed Feb 28, 2021
1 parent 39bcf3f commit 723d34a
Show file tree
Hide file tree
Showing 3 changed files with 48 additions and 2 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
17-camelforth-a*
doc/*
4 changes: 2 additions & 2 deletions 17-camelforth-a.d/pico-examples/camelforth-a/forth/forth.c
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
#define DATE_STAMP "Sun Feb 28 03:29:51 UTC 2021"
#define DATE_STAMP "Sun Feb 28 03:49:59 UTC 2021"
#define BRANCH_STAMP "erase_sector-a"
#define COMMIT_STAMP "2bcef4a"
#define COMMIT_STAMP "39bcf3f"
// #define MODE_STAMP "copy_to_ram"
#define MODE_STAMP "copy_to_ram"
// #define MODE_STAMP "no_flash "
Expand Down
45 changes: 45 additions & 0 deletions doc/results_debugging.txt
Original file line number Diff line number Diff line change
@@ -1,5 +1,50 @@
results_debugging.txt

Sun Feb 28 19:44:45 UTC 2021

BUG: system unresponsive after QSPI flash access/ops.

State: Seems okay, very brief testing done copy_to_ram mode
(seen as more difficult; no_flash mode expected to perform
even better, if anything).

commit 39bcf3f Keyboard idle indicator
Date: Sun Feb 28 03:49:59 2021 +0000

New feature: LED blinker while awaiting keyboard input.

It was noticed that some forth words seemed to complete,
after a flash op word (erase, flwrite .. don't remember
which) even though the user interface never came back
(no longer accepted keyboard input).

So the idea, here, was to ascertain if getchar() was
still listening in the do .. while loop.

ref. rp2040_pico_getkey_usb.inc

getchar_timeout_us(18) (not 'getchar()').

Have done few tests - system didn't exhibit the problem.

The test was to erase flash at 0x10050000:

[power cycle boot here]

+flwrite +erase Sun Feb 28 03:29:51 UTC 2021
branch erase_sector-a 2bcef4a UNDER TEST
copy_to_ram mode

[very first keystrokes typed after power cycling]:

ok HEX
ok 10050000 erase F E D C B A 9 CR 9 SPACES .S CR CR WORDS
Erasing target sector...
DEBUG: 50000 was number input.
Done. Exiting the 'erase' word.

(and what follows is as expected).

Fri Feb 19 22:47:24 UTC 2021

BUG: .S word prints lower case abcdef
Expand Down

0 comments on commit 723d34a

Please sign in to comment.