Jump to content

squalyl

Members
  • Content Count

    18
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    squalyl got a reaction from hunjit in hard fault when accessing GPIO configuration registers via AHB   
    Yes, we crossed messages !
     
    as always, writing about my problem made me find it.
     
    I'm now setting the correct bit in GPIOHBCTL, and it works \o/
     
    So guys, in order to access GPIO via the AHB addresses, you have to set the correct bit for your port in the GPIOHBCTL register, address 0x400fe000+0x06C , page 247 of datasheet !
     
    Hope it can be useful to someone else!
  2. Like
    squalyl got a reaction from hunjit in hard fault when accessing GPIO configuration registers via AHB   
    Small update: beware of the GPIODATA register    Adress lines 9..2 act as a mask, so it's useless to write at GPIODATA+0x000 See page 608 of datasheet...
     
    The LM4F is the first microprocessor that forces me to do that much RTFM!
  3. Like
    squalyl got a reaction from bluehash in Linux Tool Chain Options   
    I just did like the github project.
     
    TARGET=arm-none-eabi
     
    the prefix is /opt/stella
    Do you have a preference for $PREFIX?
     
    the binaries have "natural" names, do arm-none-eabi-gcc et al.
     
    I know one can create a relocatable toolchain so that it does not depend on the prefix and can be installed elsewhere, I don't remember how to do this at the moment.
     
    I also cross-built binutils for mingw, working on gcc now.
  4. Like
    squalyl got a reaction from jsolarski in Linux Tool Chain Options   
    I just did like the github project.
     
    TARGET=arm-none-eabi
     
    the prefix is /opt/stella
    Do you have a preference for $PREFIX?
     
    the binaries have "natural" names, do arm-none-eabi-gcc et al.
     
    I know one can create a relocatable toolchain so that it does not depend on the prefix and can be installed elsewhere, I don't remember how to do this at the moment.
     
    I also cross-built binutils for mingw, working on gcc now.
  5. Like
    squalyl got a reaction from jsolarski in Stellaris gcc compile on linux.   
    Okay, I'm building one now. I expected some patches to be required. thanks!
  6. Like
    squalyl got a reaction from jsolarski in Linux Tool Chain Options   
    Based on the makefile from the github project above, I could build a native "vanilla" toolchain from official sources, with just two little glitches:
     
    -I have to manually create a $PREFIX/arm-none-eabi/usr/include folder before building gcc the second time, or it won't build! (but nothing gets installed there) I get a pretty message: "the directory that should contain system headers does not exist", but no one on the intarwebs seems to have a satisfying solution. I don't want to patch sources, the goal is to build from official tarballs.
     
    -ld cannot find crt0.o when running arm-none-eabi-gcc trivial.c (with an empty main function), but gcc -c does work. That may not be required for our platform.
     
    I used:
    binutils 2.22
    gcc 4.7.2 (dependencies gmp 5.0.0 and mpfr 3.1.1)
    newlib 1.20.0
     
    I will retry the build in a clean VM in an attempt to reproduce the issues, then attempt to cross build the toolchain for mingw. I did that before for cegcc.
  7. Like
    squalyl reacted to ntfreak in ICDI support in OpenOCD   
    TI have released some info on the ICDI interface - i have uploaded here for all to access:
    https://docs.google.com/uc?export=download&id=0Bzv7UpKpOQhnWDFfSENySkJfdW8
     
    Also checlout the following project that supports the ICDI:
    https://github.com/utzig/lm4tools
     
    I am still working on OpenOCD support, the above projects are standalone.
     
    Cheers
    Spen
×
×
  • Create New...