Kestrel-3

Timeline
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

50 most recent check-ins

2020-02-08
07:08
[e264c3cff1] Leaf: first steps for CLI wrapper (user: kc5tja tags: makerom)
2020-02-02
06:09
[675b1e2afa] I believe this completes the program loader for building a ROM image. There are a few error conditions that are not checked for; for example, segment IDs are not bounds checked. Similarly, it's not checked to see if a BSS segment has a HUNK_TEXT hunk with a non-zero length. However, these should be fairly easy to add later on, should these become problematic inputs to the MakeROM tool. (user: kc5tja tags: makerom)
05:31
[051e950121] merge in (:remove) directive (user: kc5tja tags: makerom)
05:30
[3a47f2f9d6] Leaf: Introduce the (:remove ...) directive (user: kc5tja tags: trunk)
05:28
[36a562f18f] Closed-Leaf: Introduce (:remove ...) directive (user: kc5tja tags: brickie-remove-directive)
05:28
[1b58c53c39] Create new branch named "brickie-remove-directive" (user: kc5tja tags: brickie-remove-directive)
05:27
[c3a23a7120] Steps towards better support for BSS segments (and, now that I think about it, page protection as well). (user: kc5tja tags: makerom)
03:33
[74b1dabdba] HUNK_RELOC64 support added to load interpreter. Still need to implement support for distinguishing between BSS and CODE/DATA ahead of time, though; otherwise, we'd need two passes through the input file, which I'm not a fan of. (user: kc5tja tags: makerom)
01:59
[1bc0382449] Import (:delete ...) function in Brickie (user: kc5tja tags: makerom)
01:58
[33dcc7213e] Introduce (:delete ...) command to Brickie. (user: kc5tja tags: trunk)
01:57
[921e48fb0a] Closed-Leaf: Forgot the remove utility word (user: kc5tja tags: brickie-delete-directive)
01:53
[f12588c011] Add (:delete ...) directive (user: kc5tja tags: brickie-delete-directive)
01:52
[a0542294ab] Create new branch named "brickie-delete-directive" (user: kc5tja tags: brickie-delete-directive)
01:49
[439adf1ad6] Lay down relocation hunks for processing. (user: kc5tja tags: makerom)
2020-01-27
07:47
[bb9ada72cc] Documentation fixes (user: kc5tja tags: makerom)
07:36
[4844f0ae51] Designed very basic load file interpreter. Correctly places segment contents. Does not yet understand relocations. (user: kc5tja tags: makerom)
2020-01-26
23:03
[34a0e063d2] Choose better name for section (user: kc5tja tags: makerom)
20:40
[1f7133f0d8] Inserted a lot of explanation behind why I chose the magic constants that I did. They probably don't belong here. They probably need to reside in a separate reference document. But, at least I have them under revision control somewhere. (user: kc5tja tags: makerom)
18:50
[da8e336246] Update brickie (user: kc5tja tags: makerom)
18:49
[a28155cb66] Introduce doc and code directives to make "weaving" easier. (user: kc5tja tags: trunk)
18:45
[b8c915baf6] Closed-Leaf: Rename (:code) to (:bottom), bringing symmetry with (:top), and also allowing me to use (:code) as a tag to identify where code picks up versus documentation. (:code) (which is also invoked implicitly in some other directives) enables outlist generation, while (:doc) disables it. This allows for bulk documentation in, e.g., raw Markdown or HTML to comingle with executable program code. (user: kc5tja tags: doc-directive)
18:10
[f4190db675] Create new branch named "doc-directive" (user: kc5tja tags: doc-directive)
18:09
[a06942ac8e] Starting work on makerom utility (user: kc5tja tags: makerom)
16:25
[55a465d93c] merge feature (user: kc5tja tags: makerom)
16:25
[515b6aefb4] Place definition of lines in appropriate context (user: kc5tja tags: trunk)
16:24
[f754c53ba9] Create new branch named "makerom" (user: kc5tja tags: makerom)
2020-01-16
20:10
[63fa3ba241] Introducing Brickie, a literate programming tool written for GForth, but it should be portable to DX-Forth with modest effort. It is based on Akkartik's "tangle" tool, and has similar syntax for markup. Brickie is optimized for my project's needs, however, and will evolve independently of Akkartik's work. Long story short, you write software as layers of related functionality: in a sense, you explicitly name and compose patches which ultimately leads to the finished product. This allows for code and commentary to co-reside, even when chunks of related functionality are widely separated in the source code. See http://akkartik.name/post/wart-layers for more behind the theory of this approach to literate programming. (user: kc5tja tags: trunk)
20:00
[9ac2855656] Closed-Leaf: Clean up working file if tangle succeeds (user: kc5tja tags: x-brickie)
19:57
[3f4f6d01a1] Added makefile; makes tangle a binary (user: kc5tja tags: x-brickie)
19:03
[ca2352c8b1] Add tangle script (user: kc5tja tags: x-brickie)
08:41
[16be7efd90] Introduces :before and :after directives. Precise syntax isn't *quite* the same as Akkartik's version, but pretty close. This basically completes Brickie's inner guts. Next up, wrapping this up into a convenient shell-invokable script of some kind. (user: kc5tja tags: x-brickie)
07:27
[b53ea0892d] Evaluate directives as Forth command strings. (user: kc5tja tags: x-brickie)
06:44
[86bd346a6c] Introduced an "insertion point" (IP) variable. This tracks where the next line of input will be placed in the output list. Future directives will adjust the insertion point; for example (:before XXX) will look for XXX in the outlist, and if found, will set IP to the immediately preceding line. (:after YYY) will do the same, but sets IP directly to the line containing YYY, so that new text will appear after it. (No facility exists for deletion of code yet; I'm not sure how that works. Need to study akkartik's code to learn more about that.) (user: kc5tja tags: x-brickie)
06:12
[2589910629] refactor (user: kc5tja tags: x-brickie)
06:07
[bece2ded3d] refactor (user: kc5tja tags: x-brickie)
05:51
[3192ac7b76] Forth instructions to read in a file, line by line. Accumulate the input; directives not yet implemented. Writes output file. (user: kc5tja tags: x-brickie)
00:16
[f2b941471e] Create new branch named "x-brickie" (user: kc5tja tags: x-brickie)
2020-01-11
04:56
[02c01ec8d4] forgot about m4 (user: kc5tja tags: trunk)
04:50
[77617ea1f5] fix formatting (user: kc5tja tags: trunk)
04:42
[b205b9737b] Contribute official E3 user documentation (user: kc5tja tags: trunk)
03:54
[0154dbff6a] Try to fix build bug on Ubuntu 19.04 cloud box. (This might go on for a while...) (user: kc5tja tags: trunk)
2020-01-09
06:11
[7b40e899bd] Feature parity with E2, but much easier to add new virtual hardware. Also, much easier to support interrupts in the future as well. (user: kc5tja tags: trunk)
05:55
[51649cc385] Closed-Leaf: BUG FIX: Distribute sub-dword-sized data across the data bus, as hardware would. (user: kc5tja tags: e3-cpu)
2020-01-06
16:59
[f84f6c3126] Add KEY? and DRAINKEY to deal with SIA1 garbage from emulation (user: kc5tja tags: e3-cpu)
16:51
[32387908da] s/buffer/character/ in SIA code, for greater communication of intent. (user: kc5tja tags: e3-cpu)
02:30
[7a457a320b] You can now leave minicom to terminate the emulator. (user: kc5tja tags: e3-cpu)
02:25
[687e009e23] Forgot to remove debugging code (user: kc5tja tags: e3-cpu)
02:25
[52ff954d87] NEW: Implemented SIA read functionality. And, it successfully is running DX-Forth without causing the emulator to crash. Holy crap, I never thought I'd get this far. BUT: there's problems. When DX-Forth starts up, the banner comes right back as input to the interpreter. This is highly undesirable, and I really wish I could figure out a way to prevent this from happening. I don't think it's causing the interpreter distress; but, still, it's damn annoying. There are other problems too: for some reason, numeric output is not working. AGAIN. Also, Forth refuses to recognize input longer than a single character. Neither issue is clear to me why it happens. I don't yet have a plan to debug this yet either. Baffling. (user: kc5tja tags: e3-cpu)
01:32
[212569624f] NEW: Instruction fetch, load, and store misalignment traps. CPU bus interface properly models Wishbone byte lanes. (Turns out this was easier all along.) External bus errors now produce instruction fetch, load, and store access fault traps. SIA now modeled in software. ROM and RAM are now modeled in software. FIX: loads from memory properly assert their transfer sizes. Instruction fetch now acquires its instruction from the correct byte lanes. Memory writes no longer deadlock the CPU. (user: kc5tja tags: e3-cpu)
2020-01-03
07:03
[502b06662b] In theory, we have a KCP53000B emulated without support for external interrupts. In theory. Next steps is to get RAM, ROM, and SIA core access support implemented, and with *any* luck at all, we can see the DX-Forth 1.2 prompt come up. (I suspect this will not be easy.) (user: kc5tja tags: e3-cpu)