I have created a PR [1] that introduces a new design for https://free-pdk.github.io/ and also integrates the pinout diagrams as well as an overview of the many different free-pdk repositories. There is a lot of room for further improvements, but this should get the ball rolling when it comes to tutorials and more detailed instructions. Adding pages is as easy as adding new markdown files (no more HTML ).
I have not yet added any information on the SDCC examples and headers, since that is an ongoing discussion.
[1] https://github.com/free-pdk/free-pdk.github.io/pull/3
https://free-pdk.github.io/
It's live now, thanks a lot!
Now it's much easier to contribute some much needed documentation. Everyone, feel free to contribute. You can directly submit pull-requests here: https://github.com/free-pdk/free-pdk.github.io/tree/development
I will add a section about ordering the lite-programmer once I received and validated the r1 samples - they are being made right now.
I have created a PR [1] that introduces a new design for https://free-pdk.github.io/ and also integrates the pinout diagrams as well as an overview of the many different free-pdk repositories. There is a lot of room for further improvements, but this should get the ball rolling when it comes to tutorials and more detailed instructions. Adding pages is as easy as adding new markdown files (no more HTML ).
I have not yet added any information on the SDCC examples and headers, since that is an ongoing discussion.
[1] https://github.com/free-pdk/free-pdk.github.io/pull/3
https://free-pdk.github.io/
It's live now, thanks a lot!
Now it's much easier to contribute some much needed documentation. Everyone, feel free to contribute. You can directly submit pull-requests here: https://github.com/free-pdk/free-pdk.github.io/tree/development
I will add a section about ordering the lite-programmer once I received and validated the r1 samples - they are being made right now.
Excellent! Nice work!
A few things I noticed while playing around with the pinout diagrams:
- It would be nice if the diagrams were centered on the page.
- Maybe provide a quick way to check/uncheck all.
- For the 'Programming Pins', instead of RESET, maybe use ICVPP like it is labeled on the programmer schematic. And maybe add an associated ICVDD on the VDD pin to help clarify that it is directly manipulated during programming.
- I can help explain the datasheet for current sink/drive if needed. What actual questions do you have?
I also just submitted PRs for:
- Slightly better consistency with descriptions - https://github.com/cmfcmf/ic-pinout-diagram-generator/pull/5
- Add support for PMS152 - https://github.com/cmfcmf/ic-pinout-diagram-generator/pull/6
- Add support for PMS150C/PMS15A - https://github.com/cmfcmf/ic-pinout-diagram-generator/pull/7
PFS154 | PFS173 |
"negative drive current", e.g. -5mA | "positive drive current, e.g. 5mA |
"low" vs. "normal" current | "normal" vs. "strong" current |
My confusion with the drive/sink currents in the PFS154 datasheet arose from the fact that it listed the drive/sink currents differently than the PFS173 datasheet:
PFS154 PFS173 "negative drive current", e.g. -5mA "positive drive current, e.g. 5mA "low" vs. "normal" current "normal" vs. "strong" current
But, looking at your PR, I gathered that both seem to mean the same thing.
Centering the diagrams is on my TODO list, however it currently breaks the image download buttons.
When will the Mini-pill programmer available? It'll be fun to build one because it's such an impressive design!
Since all of these padauk micros are surface mounted, I learned quite a lot of surface mounting soldering during the last two months.
Just don't do what I did on the first one. After carefully tacking down the first corner and repositioning the board so I could tack down the second corner, my OCD got the better of me and without thinking about it, I put my finger on the STM32 to 'clean' off the flux residue. Let's just say, the pins were never straight again. I still might be able to fix it, but it was easier/quicker to just grab a spare pcb/ic and try again, this time even more carefullly.
In this description there is a mistake at STT16 M | LDT16 M | IDXM M,A | IDXM A,M instructions:
https://free-pdk.github.io/PADAUK_FPPA_14_bit_instruction_set.html
000011c<7-bit MEM addr>c // 7+7+1=15 bit, but this is only 14 bit device
Thanks for sharing JS
Both of these projects make me wonder how easy it would be to combine them with an inexpensive NOR flash IC (i.e. W25Q80 or similar) to greatly increase the quantity/duration of the sounds/patterns and allow them to be changed even without having to re-compile.
already completed a project with external SPI flash - a good quality audio player (plays 8 bit @32kHz).
I created a PCB which holds an 8 pin PADAUK (e.g. PMS150C/PFS154/PFS173) and added a 16MBit SPI flash and a small class D amplifier.
I use it inside of my hackintosh to play the startup chime immediately after a power cycle.
Thanks.
Another confusing instructions are T0SN M.n | T1SN M.n | SET0 M.n | SET1 M.n. The table shows 6-bit MEM addr, but for M address you need 7 bit address to be able to address the whole memory. (128bytes PFS154) For IO space needs 6 bit because it is only 64bytes.
I wrote a pure assembler, finished now, testing is in progress. That's why I need to know how every instruction works.
A video Demo of some sort would be very nice
.rom
wdreset
set0 clkmd.1
set1 pac.0
mov a,#01h
label1:
xor pa,a
nop
nop
...
97 nops total
goto label1
I experiance so many strange things around this MCU
I run my PFS154 on ILRC but according to my calculation it runs approx. at 143kHz. I wrote a loop with 97nop + 1 goto + 1 xor (to invert led), that's 100 instruction, the execution of the 100 instruction takes 700us, so to execute 1 instruction takes 7us. I don't find any explanation for this. According to the datasheet it should run at 55kHz. I know ILRC is not accurate but I did not expect 143kHz.