>The firmware update step fails. I tried both methods described on the page. Below is the console output.

I am currently working on getting the toolchain for firmware development running and have this exact same issue with the reply packet (using crosstool-ng version 1.13.3).  Following the advice of Jean-Claude, I tried building crosstool-ng 1.9.1, however, it errors while building CLoog.  Before leaving for work today, I started building version 1.12.4 however I am not too hopeful as it extracted the same version of CLoog that 1.9.1 did.  I will try some other versions of 1.13 and see how things go.

Thanks,
Brett




On Wed, Nov 30, 2011 at 9:33 AM, Jean-Claude Monnin <jc_monnin@emailplus.org> wrote:
Here is a follow-up on the robovero firmware update issues I had.

It seems that the gcc version generated by crosstool-ng version 1.13.1 has issues with openocd-0.5.0. Maybe it's the issue described in the following thread (see post of Oct 5 from athquad)
http://stackoverflow.com/questions/7053067/arm-none-eabi-gdb-and-openocd-malformed-response-to-offset-query-qoffsets
which would mean that a GDB fix upsets a openocd workaround. However this is just a guess.

I could update the robovero firmware by using the crosstool-ng version 1.9.1.

When setting up my toolchain I struggled on following points:
- The tutorial suggest to take the latest version of crosstool-ng. It's safer to take version 1.9.1
- For the LPC1700CMSIS library, I could not follow the instructions for the "Test" section. I discovered the already patched library on https://github.com/robovero/lpc17xx.cmsis.driver.library. It would be good to have a reference to it in the tutorial.
- There is a typo in the URL to get the lpc1769.cfg file (OpenOCD section). Instead of
       wget http://cumulus.gumstix.org/robovero/sources/lpc1769.cfg
  it sould be
       wget http://cumulus.gumstix.org/sources/robovero/lpc1769.cfg

This might be helpful for others, and maybe the documentation could be updated if my comments are appropriate.

Cheers

Jean-Claude

On Nov 28, 2011, at 22:34 , Jean-Claude Monnin wrote:

> Hi all,
>
> I'm trying to update the robovero firmware as described in http://robovero.org/index.php/tutorials/firmware. I have successfully done all the steps described to setup the toolchain.
> The firmware update step fails. I tried both methods described on the page. Below is the console output.
>
> Any help is appreciated
>
> Thanks
>
> Jean-Claude
>
>
> 1) Using "make flash"
> -----------------------------------------------------------------------------------------
> jean-claude@ubuntu:~/robovero/firmware$ make flash
> Building target: all
> Invoking: GCC C Linker
> arm-bare_newlib_cortex_m3_nommu-eabi-ld -nostdlib -L"lib" -Map=firmware.map -T "script.ld"  --gc-sections -o"firmware" src/wrap/_core.o src/wrap/_debug_frmwrk.o src/wrap/_lpc17xx_adc.o src/wrap/_LPC17xx.o src/wrap/_lpc17xx_can.o src/wrap/_lpc17xx_clkpwr.o src/wrap/_lpc17xx_dac.o src/wrap/_lpc17xx_emac.o src/wrap/_lpc17xx_exti.o src/wrap/_lpc17xx_gpdma.o src/wrap/_lpc17xx_gpio.o src/wrap/_lpc17xx_i2c.o src/wrap/_lpc17xx_i2s.o src/wrap/_lpc17xx_libcfg.o src/wrap/_lpc17xx_mcpwm.o src/wrap/_lpc17xx_nvic.o src/wrap/_lpc17xx_pinsel.o src/wrap/_lpc17xx_pwm.o src/wrap/_lpc17xx_qei.o src/wrap/_lpc17xx_rit.o src/wrap/_lpc17xx_rtc.o src/wrap/_lpc17xx_spi.o src/wrap/_lpc17xx_ssp.o src/wrap/_lpc17xx_systick.o src/wrap/_lpc17xx_timer.o src/wrap/_lpc17xx_uart.o src/wrap/_lpc17xx_wdt.o src/wrap/_lpc_types.o src/usb/cdcuser.o src/usb/usbcore.o src/usb/usbdesc.o src/usb/usbhw.o src/usb/usbuser.o src/extras.o src/main.o src/return.o src/ringbuffer.o src/serial.o src/startup.o src/system_LPC17xx
> .o src/table.o   -lDriversLPC17xxgnu -lgcc -lc
> Finished building target: all
>
> make --no-print-directory post-build
> arm-bare_newlib_cortex_m3_nommu-eabi-objcopy -O binary firmware firmware.bin
>
> md5sum firmware > md5sum.txt
> git log -1 --pretty=oneline > commit-id.txt
> ./flash.py
> getting sudo password
> [sudo] password for jean-claude:
>
> starting openocd: jtag chain detected
> gdb runtime: timeout
> failed. please try again
> make: [flash] Error 1 (ignored)
>
>
> 2) Using "old fashioned way" (output from both terminal sessions)
> -----------------------------------------------------------------------------------------
> jean-claude@ubuntu:~/robovero/firmware$ arm-bare_newlib_cortex_m3_nommu-eabi-gdb -x gdbconfig firmware
> GNU gdb (crosstool-NG 1.13.1) 7.3
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=x86_64-build_unknown-linux-gnu --target=arm-bare_newlib_cortex_m3_nommu-eabi".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/jean-claude/robovero/firmware/firmware...done.
> .gdbinit:1: Error in sourced command file:
> Remote 'g' packet reply is too long: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> gdbconfig:1: Error in sourced command file:
> Remote 'g' packet reply is too long: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> (gdb) load
> You can't do that when your target is `exec'
> (gdb) continue
> The program is not being run.
> (gdb)
>
>
>
>
> jean-claude@ubuntu:~$ sudo openocd -f interface/openocd-usb.cfg -f target/lpc1769.cfg
> [sudo] password for jean-claude:
> Open On-Chip Debugger 0.5.0 (2011-11-27-17:47)
> Licensed under GNU GPL v2
> For bug reports, read
>       http://openocd.berlios.de/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> 500 kHz
> Info : clock speed 500 kHz
> Info : JTAG tap: lpc1768.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
> Info : lpc1768.cpu: hardware has 6 breakpoints, 4 watchpoints
> Info : accepting 'gdb' connection from 3333
> Warn : acknowledgment received, but no packet pending
> undefined debug reason 6 - target needs reset
> Info : dropped 'gdb' connection
> Info : accepting 'gdb' connection from 3333
> Warn : acknowledgment received, but no packet pending
> undefined debug reason 6 - target needs reset
> Info : dropped 'gdb' connection
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users