STM32F103ZET6 support

I have either that board or one very similar and the basics work OK.

I have read that there are some issues accessing all the pins, but I’m not sure why, and also some issue with hardware I2C, but this has not been verified.

So I think its fairly safe to buy, as even if there are issues they would probably not be hard to fix.

BTW. Why do you want to use that board, is it the RAM / Flash or the number of Pins etc

The number of pins.. And DAC.. FSMC..

FSMC ? I don’t think we have core or library support for that.

But the DAC does work on the V series, so it should work on the Z series

FSMC – sw is not difficult – just setting a few bits in regs when doing with sram for example.
What is difficult is you need ~40wires

Here is a board with 2x pads for a sram/flash on the bottom side.
I cannot find a schematics, however

http://www.ebay.com/itm/minimum-system- … SwOyJX35SG

PS: I’ve asked a few sellers, waiting..

The DAC works on the ZET6 board. I’ve tried it myself on my board.

This is my board.
http://www.ebay.co.uk/itm/1PCS-STM32F10 … SwepJXYgwK

I had to get hold of the STM32 application to burn the bootloader over the serial port and then I managed to use STM32duino to program it. The battery powers the RTC registers and the socket next to the battery fits an nRF24L01. I wasn’t sure what it was, but connected one there and it configured (I did not test any comms).

Pito wrote:Here is a board with 2x pads for a sram/flash on the bottom side.
I cannot find a schematics, however

http://www.ebay.com/itm/minimum-system- … SwOyJX35SG

PS: I’ve asked a few sellers, waiting..

Great!! Thanks!
I think the 10ns sram there is an overkill, 55ns would be enough, and much more cheaper.
It can execute out of external sram, afaik.
The stm32duino with 1MB of ram

Pito wrote:Great!! Thanks!
I think the 10ns sram there is an overkill, 55ns would be enough, and much more cheaper.
It can execute out of external sram, afaik.
The stm32duino with 1MB of ram

W25X10, W25X20, W25X40, W25X80
Family of Serial Flash Memories
W25X10: 1M-bit / 128K-byte (131,072)
W25X20: 2M-bit / 256K-byte (262,144)
W25X40: 4M-bit / 512K-byte (524,288)
W25X80: 8M-bit / 1M-byte (1,048,576)
256-bytes per programmable page
Uniform 4K-byte Sectors / 64K-byte Blocks
•
SPI with Single or Dual Outputs
– Clock, Chip Select, Data I/O, Data Out
– Optional Hold function for SPI flexibility
•
Data Transfer up to 150M-bits / second
– Clock operation to 75MHz
– Fast Read Dual Output instruction
– Auto-increment Read capability
•
Flexible Architecture with 4KB sectors
– Sector Erase (4K-bytes)
– Block Erase (64K-byte)
– Page program up to 256 bytes <2ms
– Up to 100,000 erase/write cycles
– 20-year retention

Another interesting improvement with ADC:
The 144package has got +Vref and -Vref pins. On that board there are 2 simple LC low pass filters wired on both (bottom side).
Improvement:
To replace the L in the +Vref rail with say 1k resistor, and something like LM136-2.5 voltage reference from +Vref against the ground (or against the -Vref ??) :geek:

Got the http://wiki.stm32duino.com/index.php?ti … 32F103ZET6 board, flashed the generic_boot20_pc13 bootloader into it, and it seems it works.
Getting this error after the upload:
maple_loader v0.1
Resetting to bootloader via DTR pulse
Reset via USB Serial Failed! Did you select the right serial port?
Searching for DFU device [1EAF:0003]...
Assuming the board is in perpetual bootloader mode and continuing to attempt dfu programming...

Found it!

Opening USB Device 0x1eaf:0x0003...
Found Runtime: [0x1eaf:0x0003] devnum=1, cfg=0, intf=0, alt=2, name="STM32duino bootloader v1.0 Upload to Flash 0x8002000"
Setting Configuration 1...
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=342
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
error resetting after download: usb_reset: could not reset device, win error: The device is not connected.

Ignore the usb dfu reset message. It is a biproduct of the way dfu works.

I do , thanks.
Btw, I’ve been always confused by the info on the available flash – why we see the figures for the _total_ flash_on_the_chip when the bootloader eats a bit of it ?
// Sketch uses 17,164 bytes (3%) of program storage space. Maximum is 524,288 bytes.

Pito wrote:I do , thanks.
Btw, I’ve been always confused by the info on the available flash – why we see the figures for the _total_ flash_on_the_chip when the bootloader eats a bit of it ?
// Sketch uses 17,164 bytes (3%) of program storage space. Maximum is 524,288 bytes.