Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 05 2020 21:27

    0xdec on v2.0a

    More WIP (compare)

  • Jul 31 2020 21:36

    0xdec on v2.0a

    WIP migration + v2.0a (compare)

  • Nov 06 2018 16:29
    esden commented #16
  • Nov 06 2018 16:28

    esden on master

    Fix formatting, typos, grammar … (compare)

  • Nov 06 2018 16:28
    esden closed #16
  • Nov 06 2018 03:42
    0xdec opened #16
  • Oct 21 2018 20:53
    Poofjunior opened #15
  • Oct 12 2018 05:48
    frankalicious closed #10
  • Aug 24 2018 22:49
    irandms opened #5
  • Aug 22 2018 11:38
    elektor-labs edited #14
  • Aug 22 2018 11:36
    elektor-labs opened #14
  • May 24 2018 12:17

    kbob on master

    Improve audio clock calculation. Experiment with different color… Added bit definitions for the g… and 1 more (compare)

  • Apr 23 2018 12:45
    RandoSY edited #13
  • Apr 23 2018 12:44
    RandoSY edited #13
  • Apr 23 2018 12:33
    RandoSY opened #13
  • Apr 01 2018 06:53

    esden on master

    Removed digital volume up/down … (compare)

  • Apr 01 2018 06:50

    esden on master

    Updated PKL. Added MEMS microphone input. (compare)

  • Apr 01 2018 00:16

    esden on master

    Added FPGA. (iCEBreaker circuit… (compare)

  • Mar 31 2018 06:35

    esden on master

    Added STM32 symbol library. Added 1Bytsy schematic to the 1… (compare)

  • Mar 31 2018 04:26

    esden on master

    Connected the audio sense signa… (compare)

Piotr Esden-Tempski
@esden
@bobbatcomcastdotnet I might recall the command wrong: use monitor help to check
yeah I was wrong the command is actually monitor connect_srst enable which is mon connect enable in short.
tulanthoar
@tulanthoar
You don't technically "need" to solder the DFU pads, you just need to short the connection for a moment right as you plug in the USB cable. You can jab some copper onto the pads, it's imprecise and hacked but it worked for me after a few tries. I can't say for sure what Windows will recognize the board as, but the Linux Kernel will recognize the MCU even in non DFU mode.
bobbatcomcastdotnet
@bobbatcomcastdotnet
@esden You were absolutely correct :) Once I issued the 'mon connect enable' and 'mon jtag_scan' requests the board responded with the normal scan results including detection of the STM32F4xx device PID :+1: This resolves my immediate problem, Thank you very much guys...
bobbatcomcastdotnet
@bobbatcomcastdotnet
bobbatcomcastdotnet
@bobbatcomcastdotnet

I am using MSYS to (try) building libopencm3 for the 1Bitsy board. I get the following error:

c:/arm/gcc/bin/make --directory=lib/stm32/f4 SRCLIBDIR="c:/libopencm3/lib"
make[1]: Entering directory 'c:/libopencm3/lib/stm32/f4'
make[1]: No rule to make target '/usr/lib/gcc/arm-none-eabi/7.2.1/include/stdint.h', needed by 'adc.o'. Stop.
make[1]: Leaving directory 'c:/libopencm3/lib/stm32/f4'
make:
[makefile:64: lib/stm32/f4] Error 2

Can anyone help in resolving this error?
Thanks

Nicolas Schodet
@schodet
did you use this directory from linux before?
in this case I guess you have some .d files which refers to linux path, a git clean should solve this
bobbatcomcastdotnet
@bobbatcomcastdotnet
@schodet Thanks for the suggestion. I deleted the .d files and the make worked without errors :smile:
Shaun
@aprgl
Any interest in starting a 1bitsy-wall-of-shame room for capturing magic smoke escape events? I've got a newly formed vent hole in my stm32...
bobbatcomcastdotnet
@bobbatcomcastdotnet
Has anyone adapted the FatFS SD disk firmware to run on the 1Bitsy?
Jock Murphy
@jockm
So I just broke out the BlackMagic Probe (I was a patreon supporter) and am running into an odd issue. I can use it fine from Windows or Linux, but when I fire up arm-none-eabi-gdb and enter target extended-remote /dev/tty.usbmodem7AB878B1 GDB simply hangs and never comes back. Any suggestions?
Piotr Esden-Tempski
@esden
you have to use cu.usbmodemXXXX not tty.usbmodem
mac os x has "issues" with tty due to kernel cashing/non cashing
Jock Murphy
@jockm
DOH! Thank you very much
Piotr Esden-Tempski
@esden
No preblem! :)
Thank you for your support. :D
Daniel O'Connor
@DanielO
@esden BTW I think tty vs cu is that tty will wait for DTR or something - pretty sure it's a BSDism
also, hello
w
anyone tried nuttx on a 1bitsy? I built an image using the STMF4 discovery board description but after flashing it I can't attach the board via JTAG anymore..
(or SWDP)
Daniel O'Connor
@DanielO
just realised I can recover via DFU mode.. would be nice to know if it should work tho :)
Piotr Esden-Tempski
@esden
@/all most of you probably already saw, we are moving the chat from Gitter to Discord. As the move to Discord is going pretty well I would like to invite the rest of you, who only have mention notifications enabled. ;) Join us on Discord chat for all the fun and information about ongoing projects. Share your progress help others and ask questions. The Discord invite link is: https://discord.gg/P7FYThy
James Harton
@jimsynz
Hey folks. I just ordered a couple of 1bitsys and a debugger. Looking forward to playing with it.
I'm working on a Hexapod Raspberry Pi hat, which has a bunch of sensors and 18 servo ports on it. I can't quite understand from the datasheet and the docs how many pins I can run as PWM outputs. Can anyone give me some pointers? I'm going to prototype with the 1bitsy, but I eventually plan on just putting the MCU on my board, so in the long run I'll just copy pasta the 1bitsy schematic into mine :)