Jump to content

timotet

Members
  • Content Count

    223
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by timotet

  1. Im going to use it in a testing machine I'm working on. details coming soon!
  2. Got mine today. Nice work Trey!
  3. yep I got it pretty much immediatley.
  4. Nice job! Ive been thinking about the same thing. How are you going about the G-code translator? I was talking to friend about trying to do just that. I think being able to control more Fets with the extra I/O would be awesome.
  5. just ordered, ought to be sweet!
  6. I agree this is going to be great. TI is making a good move by making the arm cortex available cheap.
  7. Dont let it get you down blue the forum is awesome and I think it has been a great success! 10000 + registered is proof of that. If they want to see and or download files for an awesome project bad enough they will register, it only takes a minute even if they are a 1 timer. Maybe after a year or so the inactive accounts should go away. just a thought. Keep up the good work.
  8. GW I was on the standard issue vicodin for a few days following the surgery, Now Im just doin alleve when needed. Still having a fair amount of residual pain in my lower leg and ankle, but nothing like prior to surgery. I would not wish that on my worst enemy! The doc offered some other scripts but Im not much of a pill taker. Im optimistic that it will all be gone in time. heres to a speedy recovery to ya! beers! Tim
  9. thanks Getting there cant do much for 6 weeks or so.
  10. Welcome back! If it makes you feel better I just had a microdiscectomy about 10 days ago so I know how it feels to have to can your physical projects for awhile....but guess what they will wait for you. good luck and best wishes for a speedy recovery! Tim
  11. Rando Thanks for the compliment!! If you are using the serial.asm code be sure to uncheck the exclude resource from build box in the compiler preferences. Right click on the serial.asm file in the project explorer click on msp430 compiler then uncheck the box. I tried to comment everything that needs to be un-commented for the serial terminal to work. That serial code of oPossum's was a great help in debugging I use it all the time now. As far as the exclamation point on the printf.c file goes, I think its mostly a syntax thing I have CCS 5.1 and I get "Possible assignment in condition 'c =*format++'. If it compiled and ran than I guess its not that big of a problem. This is a good question for oPossum the original author of the code, maybe he will see this and reply, I'm pretty sure he uses CCS as well. edit: Ive updated my CCS to ver 5.2.0.00071 and I get 6 function declared implicitly warnings when compiling. Due to the fact that the putc function is declared in the main and not the printf file. It loads and runs fine. I hope this helps Tim
  12. Some of these may seem like common sense but bear with me. Your usb cable is good? Are you using a usb hub? Your machine loaded the drivers for the f4 board when you plugged it in? It says STM32 STlink when you open devices and printers? Have you looked around on the ST e2e forum? I know that there is a STM32 stlink utility you can down load from here:http://www.st.com/in...duct/251168.jsp The latest usb drivers are there also. hope it helps Tim
  13. this is what my external tools configuration looks like: I have no problem connecting. hope this helps Tim
  14. You are close! I know the feeling Are you using windows 7 or XP?
  15. Yes it turns out that the way I was using the GPIO_init() function was incorrect. I was, as the st forum member clive1 put it: "The way your code works is that is trashes the setting of PA.14 (SWCLK) which is the clock for the debug interface." I changed it to portF and it worked fine... but I need to rework the way I was initializing the GPIO to make it work the way I had intended. thanks for the reply
  16. Did you link the STM32F4 Stdperiph_Driver src folder to your project?
  17. Is that in the atollic software? Im using eclipse with the gnuarm plugin and atollic gdb server here is the start up code Im using /** ****************************************************************************** * @file startup_stm32f0xx.s * @author MCD Application Team * @version V1.0.0 * @date 23-March-2012 * @brief STM32F0xx Devices vector table for Atollic toolchain. * This module performs: * - Set the initial SP * - Set the initial PC == Reset_Handler, * - Set the vector table entries with the exceptions ISR address * - Configure the clock system * - Branches to main in the C library (which eventually * calls main()). * After Reset the Cortex-M0 processor is in Thread mode, * priority is Privileged, and the Stack is set to Main. ****************************************************************************** * @attention * * <h2><center>© COPYRIGHT 2012 STMicroelectronics</center></h2> * * Licensed under MCD-ST Liberty SW License Agreement V2, (the "License"); * You may not use this file except in compliance with the License. * You may obtain a copy of the License at: * * http://www.st.com/software_license_agreement_liberty_v2 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. * ****************************************************************************** */ .syntax unified .cpu cortex-m0 .fpu softvfp .thumb .global g_pfnVectors .global Default_Handler /* start address for the initialization values of the .data section. defined in linker script */ .word _sidata /* start address for the .data section. defined in linker script */ .word _sdata /* end address for the .data section. defined in linker script */ .word _edata /* start address for the .bss section. defined in linker script */ .word _sbss /* end address for the .bss section. defined in linker script */ .word _ebss .equ BootRAM, 0xF108F85F /** * @brief This is the code that gets called when the processor first * starts execution following a reset event. Only the absolutely * necessary set is performed, after which the application * supplied main() routine is called. * @param None * @retval : None */ .section .text.Reset_Handler .weak Reset_Handler .type Reset_Handler, %function Reset_Handler: ldr r0, =_estack mov sp, r0 /* set stack pointer */ /* Copy the data segment initializers from flash to SRAM */ movs r1, #0 b LoopCopyDataInit CopyDataInit: ldr r3, =_sidata ldr r3, [r3, r1] str r3, [r0, r1] adds r1, r1, #4 LoopCopyDataInit: ldr r0, =_sdata ldr r3, =_edata adds r2, r0, r1 cmp r2, r3 bcc CopyDataInit ldr r2, =_sbss b LoopFillZerobss /* Zero fill the bss segment. */ FillZerobss: movs r3, #0 str r3, [r2] adds r2, r2, #4 LoopFillZerobss: ldr r3, = _ebss cmp r2, r3 bcc FillZerobss /* Call the clock system intitialization function.*/ bl SystemInit /* Call static constructors */ bl __libc_init_array /* Call the application's entry point.*/ bl main LoopForever: b LoopForever .size Reset_Handler, .-Reset_Handler /** * @brief This is the code that gets called when the processor receives an * unexpected interrupt. This simply enters an infinite loop, preserving * the system state for examination by a debugger. * * @param None * @retval : None */ .section .text.Default_Handler,"ax",%progbits Default_Handler: Infinite_Loop: b Infinite_Loop .size Default_Handler, .-Default_Handler /****************************************************************************** * * The minimal vector table for a Cortex M0. Note that the proper constructs * must be placed on this to ensure that it ends up at physical address * 0x0000.0000. * ******************************************************************************/ .section .isr_vector,"a",%progbits .type g_pfnVectors, %object .size g_pfnVectors, .-g_pfnVectors g_pfnVectors: .word _estack .word Reset_Handler .word NMI_Handler .word HardFault_Handler .word 0 .word 0 .word 0 .word 0 .word 0 .word 0 .word 0 .word SVC_Handler .word 0 .word 0 .word PendSV_Handler .word SysTick_Handler .word WWDG_IRQHandler .word PVD_IRQHandler .word RTC_IRQHandler .word FLASH_IRQHandler .word RCC_IRQHandler .word EXTI0_1_IRQHandler .word EXTI2_3_IRQHandler .word EXTI4_15_IRQHandler .word TS_IRQHandler .word DMA1_Channel1_IRQHandler .word DMA1_Channel2_3_IRQHandler .word DMA1_Channel4_5_IRQHandler .word ADC1_COMP_IRQHandler .word TIM1_BRK_UP_TRG_COM_IRQHandler .word TIM1_CC_IRQHandler .word TIM2_IRQHandler .word TIM3_IRQHandler .word TIM6_DAC_IRQHandler .word 0 .word TIM14_IRQHandler .word TIM15_IRQHandler .word TIM16_IRQHandler .word TIM17_IRQHandler .word I2C1_IRQHandler .word I2C2_IRQHandler .word SPI1_IRQHandler .word SPI2_IRQHandler .word USART1_IRQHandler .word USART2_IRQHandler .word 0 .word CEC_IRQHandler .word 0 .word BootRAM /* @0x108. This is for boot in RAM mode for STM32F0xx devices. */ /******************************************************************************* * * Provide weak aliases for each Exception handler to the Default_Handler. * As they are weak aliases, any function with the same name will override * this definition. * *******************************************************************************/ .weak NMI_Handler .thumb_set NMI_Handler,Default_Handler .weak HardFault_Handler .thumb_set HardFault_Handler,Default_Handler .weak SVC_Handler .thumb_set SVC_Handler,Default_Handler .weak PendSV_Handler .thumb_set PendSV_Handler,Default_Handler .weak SysTick_Handler .thumb_set SysTick_Handler,Default_Handler .weak WWDG_IRQHandler .thumb_set WWDG_IRQHandler,Default_Handler .weak PVD_IRQHandler .thumb_set PVD_IRQHandler,Default_Handler .weak RTC_IRQHandler .thumb_set RTC_IRQHandler,Default_Handler .weak FLASH_IRQHandler .thumb_set FLASH_IRQHandler,Default_Handler .weak RCC_IRQHandler .thumb_set RCC_IRQHandler,Default_Handler .weak EXTI0_1_IRQHandler .thumb_set EXTI0_1_IRQHandler,Default_Handler .weak EXTI2_3_IRQHandler .thumb_set EXTI2_3_IRQHandler,Default_Handler .weak EXTI4_15_IRQHandler .thumb_set EXTI4_15_IRQHandler,Default_Handler .weak TS_IRQHandler .thumb_set TS_IRQHandler,Default_Handler .weak DMA1_Channel1_IRQHandler .thumb_set DMA1_Channel1_IRQHandler,Default_Handler .weak DMA1_Channel2_3_IRQHandler .thumb_set DMA1_Channel2_3_IRQHandler,Default_Handler .weak DMA1_Channel4_5_IRQHandler .thumb_set DMA1_Channel4_5_IRQHandler,Default_Handler .weak ADC1_COMP_IRQHandler .thumb_set ADC1_COMP_IRQHandler,Default_Handler .weak TIM1_BRK_UP_TRG_COM_IRQHandler .thumb_set TIM1_BRK_UP_TRG_COM_IRQHandler,Default_Handler .weak TIM1_CC_IRQHandler .thumb_set TIM1_CC_IRQHandler,Default_Handler .weak TIM2_IRQHandler .thumb_set TIM2_IRQHandler,Default_Handler .weak TIM3_IRQHandler .thumb_set TIM3_IRQHandler,Default_Handler .weak TIM6_DAC_IRQHandler .thumb_set TIM6_DAC_IRQHandler,Default_Handler .weak TIM14_IRQHandler .thumb_set TIM14_IRQHandler,Default_Handler .weak TIM15_IRQHandler .thumb_set TIM15_IRQHandler,Default_Handler .weak TIM16_IRQHandler .thumb_set TIM16_IRQHandler,Default_Handler .weak TIM17_IRQHandler .thumb_set TIM17_IRQHandler,Default_Handler .weak I2C1_IRQHandler .thumb_set I2C1_IRQHandler,Default_Handler .weak I2C2_IRQHandler .thumb_set I2C2_IRQHandler,Default_Handler .weak SPI1_IRQHandler .thumb_set SPI1_IRQHandler,Default_Handler .weak SPI2_IRQHandler .thumb_set SPI2_IRQHandler,Default_Handler .weak USART1_IRQHandler .thumb_set USART1_IRQHandler,Default_Handler .weak USART2_IRQHandler .thumb_set USART2_IRQHandler,Default_Handler .weak CEC_IRQHandler .thumb_set CEC_IRQHandler,Default_Handler /************************ (C) COPYRIGHT STMicroelectronics *****END OF FILE****/ Is that what you wanted? I have played around with it a little more since I posted and I figured out it is definitely somewhere in my code, I was able to get the link to initalize by holding the reset button and starting the tool in the IDE. It took a few tries then worked, so I reloaded the program and as soon as I hit run I lost the link again. I reset the link again, using the same method as above and loaded a simple blink led program then I could debug no problem. Reloaded the other program and same deal lost the link! weird. thanks for the help
  18. Hi I have been programming the stm32f0 discovery kit for a few days now using the Atollic gdb server with no problems whatsoever, that is until today. I was in the middle of debugging and lost the link to the stm32f0, now when I try to reinitialize the device I get the initialization error. I can use the stm stlink utility and load a hex file with no problems. I actually reloaded the same program I was working on when I lost the link. I have the Stm32f4 discovery board as well and I connected that to see if it was a driver issue but I have no problems initializing the st-link on that board. I connected the f0 board to another computer I have and I cant get it to initialize the st-link either. Does anyone have any suggestions for a fix, Im at a loss here. thanks Tim I posted this on the stm e2e forum as well with a link to this forum so maybe some more people will join this forum. I will update this if I can get the issue fixed
  19. Hello! Ive been waiting for a forum like this. Thanks to bluehash lets hope it takes off.
  20. you can use eclipse with the gnu arm plug in, codesourcery g++ lite, and The atollic gdb server.
  21. CortexArmy good one didnt KISS do that? I think if you set up a forum like 43oh for the arm cortex you would get a huge response. Just browsing the st forum is proof that people are looking for it, as far as a place to go and get some advice on where to start. There are some really experienced people on the st forum if they sighed up too it would be great. 43oh is awesome and we know what makes it that way, if the community was behind it like it is here then its on! What does moderator entail? I have to agree with oPossum on the like feature, even if no one replies to your post at least you know it was useful to someone.
×
×
  • Create New...