Re: [OpenWrt-Devel] Using JTAG on Ralink

[jonsm...@gmail.com]

This is a bug in openocd. I have a fix but what to do with it is being
discussed on the openocd list.

On Sun, Jun 9, 2013 at 8:28 AM, Karl P  wrote:
>
> I've seen this a lot with openocd and arm cortex-m targets.  There's always
> lots of finger pointing, but it's "incompatible" gdb version and gdbserver
> version. It's to do with the gdbserver sending an XML memory map that your
> version of gdb doesn't understand.  (or at least, doesn't understand
> receiving it from the target)  The "easiest" is finding the "right" version
> of gdb to use with the gdbserver you're using, which may be an up or a
> downgrade.  There's some workarounds with manually specifying target type
> architecture and pointing to local memory map xml files and so on, but it's
> increasingly ugly.
>
> Seeing as it looks like the gdb is built by openwrt, can you check if it has
> xml support built in?
>
> Cheers,
> Karl P
>
>
>
> On 06/09/2013 02:06 AM, jonsm...@gmail.com wrote:
>>
>> Any idea what I am doing wrong? Why are the registers too long?
>>
>> jonsmirl@terra:/home/apps/openwrt$
>>
>> ./staging_dir/toolchain-mipsel_dsp_gcc-4.7.2_uClibc-0.9.33.2/bin/mipsel-openwrt-linux-uclibc-gdb
>> GNU gdb (Linaro GDB) 7.5-2012.12-1
>> Copyright (C) 2012 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> 
>> 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-linux-gnu
>> --target=mipsel-openwrt-linux-uclibc".
>> For bug reporting instructions, please see:
>> .
>> (gdb) target remote localhost:
>> Remote debugging using localhost:
>> Remote 'g' packet reply is too long:
>>
>> 62000a0040001050f780c080fc80439d11001050f780d0b2fc80d52ef580ca2ef5800040fb80a02ff580b02ff780ac72fc80ff8160c2fc80d830f58055aa55aa06000100424644202c80006004020080
>> (gdb) show architecture
>> The target architecture is set automatically (currently mips)
>> (gdb)
>>
>>
>> -
>>
>> jonsmirl@terra:~$ openocd -f interface/olimex-arm-usb-ocd.cfg -f
>> ralink.cfg
>> Open On-Chip Debugger 0.5.0 (2011-12-03-10:15)
>> Licensed under GNU GPL v2
>> For bug reports, read
>> http://openocd.berlios.de/doc/doxygen/bugs.html
>> Info : only one transport option; autoselect 'jtag'
>> 2000 kHz
>> adapter_nsrst_delay: 100
>> jtag_ntrst_delay: 100
>> rt3050.cpu
>> Info : clock speed 2000 kHz
>> Info : JTAG tap: rt3050.cpu tap/device found: 0x1535024f (mfg: 0x127,
>> part: 0x5350, ver: 0x1)
>> Info : accepting 'telnet' connection from 
>> target state: halted
>> target halted in MIPS32 mode due to debug-request, pc: 0x8204
>> Info : accepting 'gdb' connection from 
>> Warn : acknowledgment received, but no packet pending
>> Info : dropped 'gdb' connection
>>
>>
>> --
>> Jon Smirl
>> jonsm...@gmail.com
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel



-- 
Jon Smirl
jonsm...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LUCI works extremely slow...

[Ben West]

Hi Jinzcheng.  Indeed, you are correct that LUCI's speed of operation would
not be directly related to memory requirements for a v3.x kernel.
Likewise, Manuel is correct that older versions of OpenWRT should run OK
with 16MB RAM, e.g. Backfire v10.03.1 or so, and that pre-compiling LUCI's
source files could yield some performance improvement.

The OP didn't specify which version of OpenWRT he is using, and I assumed
it was a newer one incorporating the v 3.x kernel.  I responded, since I
was suggesting the slow LUCI could also be due to the kernel leaving too
little available RAM for lua and other application-layer elements.

On Mon, Jun 10, 2013 at 6:51 PM, jinzhcheng  wrote:

>
> >My understanding is that OpenWRT Attitude Adjustment, along with current
> >versions of trunk, are not expected to run in any reliable way under less
> >than 32MB of RAM.  In particular, the v3.x kernel is not supported for so
> >little memory, and the OpenWRT dev community
> likewise doesn't support it.
> >
> Hi Ben
>
> What you means is v3.x kernel don't support 32MB RAM? not the issue of LUCI?
>
>
>
>


-- 
Ben West
http://gowasabi.net
b...@gowasabi.net
314-246-9434
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LUCI works extremely slow...

[jinzhcheng]

>My understanding is that OpenWRT Attitude Adjustment, along with current
>versions of trunk, are not expected to run in any reliable way under less
>than 32MB of RAM.  In particular, the v3.x kernel is not supported for so
>little memory, and the OpenWRT dev community likewise doesn't support it.
>
Hi BenWhat you means is v3.x kernel don't support 32MB RAM? not the issue of 
LUCI?___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LUCI works extremely slow...

[Manuel Munz]

On 10.06.2013 20:13, Ben West wrote:
> My understanding is that OpenWRT Attitude Adjustment, along with current
> versions of trunk, are not expected to run in any reliable way under less
> than 32MB of RAM.  In particular, the v3.x kernel is not supported for so
> little memory, and the OpenWRT dev community likewise doesn't support it.
> 

Ack. But maybe he is running an older version or just wants to try. What
helps to speed up luci is to build images with luci precompiled
(luci->libs) in menuconfig.

Regards, Manuel




signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LUCI works extremely slow...

[xakep6666]

Try to use 'openwrt' theme (old)
10.06.2013 22:13 пользователь "Ben West"  написал:

> My understanding is that OpenWRT Attitude Adjustment, along with current
> versions of trunk, are not expected to run in any reliable way under less
> than 32MB of RAM.  In particular, the v3.x kernel is not supported for so
> little memory, and the OpenWRT dev community likewise doesn't support it.
>
> On Mon, Jun 10, 2013 at 11:20 AM, Wojciech Kromer <
> wojciech.kro...@dgt.com.pl> wrote:
>
>>
>> on small custom device with rt3052, 16MB RAM, 4MB SPI-FLASH
>>
>> Is it an known issue?
>> Are there any advices?
>>
>> Best regards.
>> __**_
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.**org 
>> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel
>>
>
>
>
> --
> Ben West
> http://gowasabi.net
> b...@gowasabi.net
> 314-246-9434
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LUCI works extremely slow...

[Ben West]

My understanding is that OpenWRT Attitude Adjustment, along with current
versions of trunk, are not expected to run in any reliable way under less
than 32MB of RAM.  In particular, the v3.x kernel is not supported for so
little memory, and the OpenWRT dev community likewise doesn't support it.

On Mon, Jun 10, 2013 at 11:20 AM, Wojciech Kromer <
wojciech.kro...@dgt.com.pl> wrote:

>
> on small custom device with rt3052, 16MB RAM, 4MB SPI-FLASH
>
> Is it an known issue?
> Are there any advices?
>
> Best regards.
> __**_
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.**org 
> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel
>



-- 
Ben West
http://gowasabi.net
b...@gowasabi.net
314-246-9434
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] LUCI works extremely slow...

[Wojciech Kromer]

on small custom device with rt3052, 16MB RAM, 4MB SPI-FLASH

Is it an known issue?
Are there any advices?

Best regards.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 3g disconnect on WR703N

[jinzhcheng]

>On 6/8/2013 8:10 PM, Mitch Kelly wrote:
>>
>> Hi,
>>
>> The 703N can only supply 200mA out the USB port, Its likely this issue 
>> is caused by the device using more power that can be supplied and the 
>> device resetting.
>>
>> TP-Link have a compatibility Martix for devices, It is based on Power 
>> consumption, Not just drivers in stock firmware.
>>
>> Mitch Kelly.
>>
>>
>I and others run an OpenWRT based project that expands the USB modem 
>capabilities of the firmware to include automatic connection, full LTE 
>speeds for 4G modems and other modem related features.
>
>We have come across this problem of disconnection shortly after 
>connecting many times and it always has come down to lack of power being 
>supplied to the modem. With over 7000 downloads of our firmware we have 
>much experience in this area.
>
>The WR703N can supply, if available, up to 1.25 amps to the USB port 
>according to the specs of the switch chip that they use. The stock power 
>supply that comes with the WR703N is rated at 1 amp by the sticker but 
>we have found this is not always the case.
>
>By using a better, higher rated power supply you'll see the problem 
>disappear. Modems take much more power than you would think and a poor 
>signal can add to the drain. An LTE modem in a low signal area can use 
>up to 800ma, which is far more than the stock power supply can provide.
>
>The issue of disconnections is seldom caused by the router firmware but 
>seems to be power supply based in almost every case.
>
>Ralph Deane
Thanks for your help!I do any test, use battery to power supply 3G modem and 
usb is only used to communication, but the issue exist too.By the way, Why 
openwrt don't support re-dial if 3G is disconnected?Thanks!

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 3g disconnect on WR703N

[jinzhcheng]

>On 6/8/2013 8:10 PM, Mitch Kelly wrote:
>>
>> Hi,
>>
>> The 703N can only supply 200mA out the USB port, Its likely this issue 
>> is caused by the device using more power that can be supplied and the 
>> device resetting.
>>
>> TP-Link have a compatibility Martix for devices, It is based on Power 
>> consumption, Not just drivers in stock firmware.
>>
>> Mitch Kelly.
>>
>>
>I and others run an OpenWRT based project that expands the USB modem 
>capabilities of the firmware to include automatic connection, full LTE 
>speeds for 4G modems and other modem related features.
>
>We have come across this problem of disconnection shortly after 
>connecting many times and it always has come down to lack of power being 
>supplied to the modem. With over 7000 downloads of our firmware we have 
>much experience in this area.
>
>The WR703N can supply, if available, up to 1.25 amps to the USB port 
>according to the specs of the switch chip that they use. The stock power 
>supply that comes with the WR703N is rated at 1 amp by the sticker but 
>we have found this is not always the case.
>
>By using a better, higher rated power supply you'll see the problem 
>disappear. Modems take much more power than you would think and a poor 
>signal can add to the drain. An LTE modem in a low signal area can use 
>up to 800ma, which is far more than the stock power supply can provide.
>
>The issue of disconnections is seldom caused by the router firmware but 
>seems to be power supply based in almost every case.
>
>Ralph Deane
Thanks for your help!I do any test, use battery to power supply 3G modem and 
usb is only used to communication, but the issue exist too.By the way, Why 
openwrt don't support re-dial if 3G is disconnected?Thanks!___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] ramips: add support for belkin F7C027 wemo/homeautomatisation plug

[John Crispin]

Hi,

can you already switch the power on/off for the socket ?

John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel