Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi again, asterisk: set debug output on console console = notice,warning,error,debug so, all software recognize correctly the correct port [Nov 11 15:08:06] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0 detected event off hook [Nov 11 15:08:10] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0 detected event on hook [Nov 11 15:08:24] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 1 detected event off hook [Nov 11 15:08:26] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 1 detected event on hook but both owsip and asterisk route call to TAPI/1 (and never TAPI/2) Regards Eddi On Mon, Nov 10, 2014 at 9:30 PM, Eddi De Pieri e...@depieri.net wrote: - tapidemo -d 1: (tapidemo-5.1.0.53) phone1 connected: [...] EASY80910: Detected event on channel 0: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) [...] phone2 connected: EASY80910: Detected event on channel 1: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) Phone No 2: Off-Hook detected. Phone No 2: FXS state: S_READY FXS event: IE_HOOKOFF Phone No 2: Line mode changed to IFX_TAPI_LINE_FEED_ACTIVE Phone No 2: DTMF detection started on EASY80910, DataCh 1, fd 5 Phone No 2: LEC started on EASY80910, PhoneCh 1 Phone No 2: Play Dialtone. Phone No 2: Handling state executed, current FXS state: S_OUT_DIALTONE EASY80910: Detected event on channel 1: ID: 0x2004 (IFX_TAPI_EVENT_FXS_ONHOOK) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x2004 (IFX_TAPI_EVENT_FXS_ONHOOK) Phone No 2: On-Hook detected. Phone No 2: FXS state: S_OUT_DIALTONE FXS event: IE_HOOKON Phone No 2: TAPIDEMO_ClearPhone. Phone No 2: DTMF detection stopped on EASY80910, data ch 1, fd 5 Phone No 2: LEC stopped on EASY80910, phone ch 1 Phone No 2: Line mode changed to IFX_TAPI_LINE_FEED_STANDBY Phone No 2: Handling state executed, current FXS state: S_READY EASY80910: Detected event on channel 1: ID: 0x3302 (IFX_TAPI_EVENT_TONE_GEN_END) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x3302 (IFX_TAPI_EVENT_TONE_GEN_END) - owsip + pjsip: it start even if this device have 32mb ram no difference between phone1 and phone2 connected... it works but but you have two connectors that seen just one fxs line - asterisk + chan_lantiq: no difference between phone1 and phone2 connected... it works but but you have two connectors that seen just one fxs line Stay tuned... Let me know it this piece of log may help to understand how to patch owsip and/or asterisk Regards On Tue, Oct 21, 2014 at 11:44 PM, Eddi De Pieri e...@depieri.net wrote: I've managed to get FXS working on my vgv7519 vr9 router using asterisk-chan-lantiq. busy/free tone ok chan-lantiq to sip ok sip to chan-lantiq to test. I need to do some other tests before start to release code for BB... Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi Eddi, On Tue, Nov 11, 2014 at 04:10:30PM +0100, Eddi De Pieri wrote: asterisk: set debug output on console console = notice,warning,error,debug so, all software recognize correctly the correct port [Nov 11 15:08:06] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0 detected event off hook [Nov 11 15:08:10] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0 detected event on hook [Nov 11 15:08:24] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 1 detected event off hook [Nov 11 15:08:26] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 1 detected event on hook but both owsip and asterisk route call to TAPI/1 (and never TAPI/2) I don't remember if that worked on owsip. But asterisk should support both channels. What about TAPI/0? I am unsure if we started naming the channels from 0 or 1... Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
On Tue, Nov 11, 2014 at 4:24 PM, Luka Perkov l...@openwrt.org wrote: Hi Eddi, I don't remember if that worked on owsip. But asterisk should support both channels. What about TAPI/0? I am unsure if we started naming the channels from 0 or 1... /* on asterisk user's side, we're using port 1-2. * Here in non normal human's world, we begin * counting at 0. */ my doubt is: chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%s, 1); If I understand correctly this is like a printf... so it seems it will always map c to TAPI/1 I think it should be: chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%s, sprintf(%d, (c+1))); Let me try... Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
it seems it work better in this way... chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, (c + 1)); I don't know so well asterisk programming... please let me know if it seems correct to you! Eddi On Tue, Nov 11, 2014 at 6:11 PM, Eddi De Pieri e...@depieri.net wrote: On Tue, Nov 11, 2014 at 4:24 PM, Luka Perkov l...@openwrt.org wrote: Hi Eddi, I don't remember if that worked on owsip. But asterisk should support both channels. What about TAPI/0? I am unsure if we started naming the channels from 0 or 1... /* on asterisk user's side, we're using port 1-2. * Here in non normal human's world, we begin * counting at 0. */ my doubt is: chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%s, 1); If I understand correctly this is like a printf... so it seems it will always map c to TAPI/1 I think it should be: chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%s, sprintf(%d, (c+1))); Let me try... Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi Eddi, On Tue, Nov 11, 2014 at 07:11:13PM +0100, Eddi De Pieri wrote: it seems it work better in this way... chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, (c + 1)); I don't know so well asterisk programming... please let me know if it seems correct to you! I'm not sure. Why don't you use 'TAPI/%d, c' so the naming starts with 0? Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi Luka, For me is the same... just to compliant comment inside source code: /* on asterisk user's side, we're using port 1-2. * Here in non normal human's world, we begin * counting at 0. */ So you confirm that TAPI/%s,1 map both port0 and port1 to TAPI/1 and you can't use asterisk extensions rule to choose which port to use to route the call Do you think we need to patch the source to use chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, (c + 1)); or chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, c); Eddi... On Tue, Nov 11, 2014 at 10:59 PM, Luka Perkov l...@openwrt.org wrote: Hi Eddi, On Tue, Nov 11, 2014 at 07:11:13PM +0100, Eddi De Pieri wrote: it seems it work better in this way... I don't know so well asterisk programming... please let me know if it seems correct to you! I'm not sure. Why don't you use 'TAPI/%d, c' so the naming starts with 0? Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
- tapidemo -d 1: (tapidemo-5.1.0.53) phone1 connected: [...] EASY80910: Detected event on channel 0: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) [...] phone2 connected: EASY80910: Detected event on channel 1: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) Phone No 2: Off-Hook detected. Phone No 2: FXS state: S_READY FXS event: IE_HOOKOFF Phone No 2: Line mode changed to IFX_TAPI_LINE_FEED_ACTIVE Phone No 2: DTMF detection started on EASY80910, DataCh 1, fd 5 Phone No 2: LEC started on EASY80910, PhoneCh 1 Phone No 2: Play Dialtone. Phone No 2: Handling state executed, current FXS state: S_OUT_DIALTONE EASY80910: Detected event on channel 1: ID: 0x2004 (IFX_TAPI_EVENT_FXS_ONHOOK) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x2004 (IFX_TAPI_EVENT_FXS_ONHOOK) Phone No 2: On-Hook detected. Phone No 2: FXS state: S_OUT_DIALTONE FXS event: IE_HOOKON Phone No 2: TAPIDEMO_ClearPhone. Phone No 2: DTMF detection stopped on EASY80910, data ch 1, fd 5 Phone No 2: LEC stopped on EASY80910, phone ch 1 Phone No 2: Line mode changed to IFX_TAPI_LINE_FEED_STANDBY Phone No 2: Handling state executed, current FXS state: S_READY EASY80910: Detected event on channel 1: ID: 0x3302 (IFX_TAPI_EVENT_TONE_GEN_END) Phone No 2: Event on DevIDX 0, PhoneCh 1, DataCh 1: 0x3302 (IFX_TAPI_EVENT_TONE_GEN_END) - owsip + pjsip: it start even if this device have 32mb ram no difference between phone1 and phone2 connected... it works but but you have two connectors that seen just one fxs line - asterisk + chan_lantiq: no difference between phone1 and phone2 connected... it works but but you have two connectors that seen just one fxs line Stay tuned... Let me know it this piece of log may help to understand how to patch owsip and/or asterisk Regards On Tue, Oct 21, 2014 at 11:44 PM, Eddi De Pieri e...@depieri.net wrote: I've managed to get FXS working on my vgv7519 vr9 router using asterisk-chan-lantiq. busy/free tone ok chan-lantiq to sip ok sip to chan-lantiq to test. I need to do some other tests before start to release code for BB... Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
I've managed to get FXS working on my vgv7519 vr9 router using asterisk-chan-lantiq. busy/free tone ok chan-lantiq to sip ok sip to chan-lantiq to test. I need to do some other tests before start to release code for BB... Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi to all, about gpio... before starting tapidemo (or asterisk): gpio8: dir/in alt0/0 alt1/0 gpio34: dir/in alt0/0 alt1/0 gpio35: dir/in alt0/0 alt1/0 gpio36: dir/in alt0/0 alt1/0 after starting tapidemo (or asterisk): gpio8: dir/out alt0/1 alt1/0 gpio34: dir/out alt0/0 alt1/1 gpio35: dir/in alt0/0 alt1/1 gpio36: dir/in alt0/0 alt1/1 both tapidemo and asterisk die with [ 1047.256000] WARNING: ** ACCESSING SLIC DEVICE FAILED ** by setting gpio3 to out and by setting it to 1 both stay up but I can't hard any tone on phone (tested with firmware 2.1.1.7.0 and 2.3.1.7.0) Please, someone can give me a suggestion if the problem might be due to wrong coef file or something else? Regards, Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi to all, by manually setting correcly gpio like on original board with devmem: root@OpenWrt:/# /etc/init.d/tapidemo start eth1 ITM version 0.0.0.27. Compiled for EASY80910 with FXO (Slic121). Filesystem firmware binary used (/lib/firmware/voice_ar9_firmware.bin). VMMC [version 0x 0, type 0x 7, channels 2] ready! FW Version 2.1 VMMC Driver version 1.9.0.3 Using board EASY80910 with: - CID support: ETSI FSK, Europe (standard 1). - VAD support: IFX_TAPI_ENC_VAD_NOVAD - no voice activity detection. - LEC support: IFX_TAPI_WLEC_TYPE_NE - LEC using fixed window. No Echo Suppressor. - Debug level: HIGH. - Transparent fax/modem and T.38 transmission support. Dialing sequences for different call types: a) Local connection: c b) Extern connection: 0iiic c) PCM connection: 09iiic d) FXO connection: 05d e) FEATURE selection first digit must be 'STAR (*), afterthat feature number (4 digits). f) CONFERENCING first digit must be 'HASH (#)', afterthat normal dialing sequence, g) Extern connection with full ip: 0*xxx*xxx*xxx*xxx*dcc - each part separated with STAR (*), Legend: c - channel number started from 1 (1 means channel 0). iii - lowest part of external board IP address (a.b.c.iii) d - FXO channel, started from 1 (1 means channel 0). xxx*xxx*xxx*xxx - external board IP address (xxx.xxx.xxx.xxx) FXS channels calling table: | Dial | Board | Phone channel | || |1 | EASY80910 |0 | |2 | EASY80910 |1 | Stay tuned... (for the moment watchdog disabled, like has ben done on falcon patches) Regards Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi Mikko, I've pushed my changes on https://github.com/openwrt-vgv7519/openwrt (branch vgv7519-20141007-begin_vmmc) If you want to try it on different router remember to adjust profiles and dts like VGV7519. bootargs = console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M vpe1_wired_tlb_entries=1; adjust; -phym to (memory on your board)M, -mem to (phym -2)M, -vpe1_load_addr to 0x(131+phym20) (note that I haven't configured yet some gpio to get voice working correctly... but I doubt this is the real problem.. From Daniel Schwierzeck: that's the Lantiq propietary SSIO interface for analog SLIC chips which is controlled by the voice firmware. You only need to setup GPIO's 8, 34, 35 and 36 as follows: GPIO alt0 alt1 dir 8101 CLKOUT0 34 011 SSIO_TX 35 011 SSIO_RX 36 011 SSIO_CLK So i get firmware load on vpe1 but it crash on worker process.. Do you know if tapi works on other lantiq cpu with 3.14 kernel? folowing dmesg... Filesystem firmware binary used (/lib/firmware/voice_ar9_firmware.bin). [ 96.396000] I'm here 8a [ 96.456000] I'm here 8b [ 96.512000] eddi I'm here 9 - mps release [ 96.516000] eddi I'm here 9 - mps release done [ 96.52] eddi I'm here 10 - start wdog [ 96.524000] eddi I'm here 10 - start wdog done [ 96.528000] eddi I'm here 11 - return version and exit [ 96.60] MPS: FW checksum OK [ 96.604000] CPU 0 Unable to handle kernel paging request at virtual address 0094, epc == 82f9d960, ra == 82843fd4 [ 96.612000] Oops[#1]: [ 96.612000] CPU: 0 PID: 558 Comm: kworker/0:2 Not tainted 3.14.18 #58 [ 96.612000] Workqueue: TAPIevents 0x8284 [ 96.612000] task: 829b2a90 ti: 8283a000 task.ti: 8283a000 [ 96.612000] $ 0 : f406 f406 [ 96.612000] $ 4 : 0088 1100fd00 00fe [ 96.612000] $ 8 : 8283bfe0 fd00 0001 [ 96.612000] $12 : 77977ca0 [ 96.612000] $16 : 82fd9000 838b3408 829645f8 [ 96.612000] $20 : 8041 8040b280 [ 96.612000] $24 : 7796a000 82843dec [ 96.612000] $28 : 8283a000 8283be30 803b6dc8 82843fd4 [ 96.612000] Hi: 00a0 [ 96.612000] Lo: 008c [ 96.612000] epc : 82f9d960 IFXOS_MutexGet+0x8/0x48 [drv_ifxos] [ 96.612000] Not tainted [ 96.612000] ra: 82843fd4 IFX_TAPI_Event_Dispatch_ProcessCtx+0x1e8/0xfbc [drv_tapi] [ 96.88] Status: 1100fd02 KERNEL EXL [ 96.88] Cause : 8088 [ 96.88] BadVA : fff0 [ 96.88] PrId : 00019555 (MIPS 34Kc) [ 96.88] Modules linked in: rt2800pci rt2800mmio rt2800lib iptable_nat rt2x00pci t2x00mmio rt2x00lib pppoe nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multi port xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp nf_conntrack ltq_deu_vr9 iptable_r aw iptable_mangle iptable_filter ipt_REJECT ip_tables drv_vmmc crc_itu_t crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables pppoatm ppp_generic slhc br2684 atm drv_ta pi ipv6 eeprom_93cx6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug [ 96.88] Process kworker/0:2 (pid: 558, threadinfo=8283a000, task=829b2a90, tls=) [ 96.88] Stack : 8040b5d0 80408c60 83820970 829b2c6c 829b2a90 8000d478 8283bd80 800bebb 829ca1c0 0001 829b2a88 829b2a90 83820970 829b2be8 829b2a88 829b2be8 0020 0012 800e7b88 829b2a90 80bb 80bb 801864cc 8283bc50 8283bc50 829b2c30 8283bc50 0001 8283bd80 803b3fc0 000b 829b2a90 8041 0003 8283bd80 800ddd14 ... [ 96.88] Call Trace: [ 96.88] [80189eec] kthread_data+0x4/0xc [ 96.88] [80314074] wq_worker_sleeping+0x14/0x100 [ 96.88] [8000d478] __schedule+0xf0/0x578 [ 96.88] [800e7b88] do_exit+0x840/0x858 Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hello Eddi,
Eddi De Pieri wrote on 2014-10-14:
Hi to all,
I've applied to kernel patch for vpe committed for falcon, fixed for
vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters
console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M
mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M
vpe1_wired_tlb_entries=1
Why do you reserve 2M? The voice FW only needs 1M
Now I get:
[ 175.672000] Here I am: #1
[ 175.672000] Here I am: #2
[ 175.676000] Here I am: #3
[ 175.68] Here I am: #4
[ 175.68] Here I am: #5
[ 175.684000] Here I am: cpu1_base_addr: 83e0 #6
[ 175.688000] Here I am: #7
[ 175.692000] Here I am: #8
[ 175.70] Unhandled kernel unaligned access[#1]:
[ 175.70] CPU: 0 PID: 1516 Comm: tapidemo Not tainted 3.14.18 #40
[ 175.70] task: 829819b0 ti: 82b54000 task.ti: 82b54000
[ 175.70] $ 0 : 77d95290 bf001f38 cc123456
[ 175.70] $ 4 : a3e0 00082280 8000
[ 175.70] $ 8 : a6e5d6ef 00080080 00ff 91008110
[ 175.70] $12 : 807f807f 293f1500 00fe00fe
[ 175.70] $16 : 82b55da0 8296 8296
[ 175.70] $20 : 0001 82b55e88
[ 175.70] $24 :
[ 175.70] $28 : 82b54000 82b55d60 7fd3aec8 8295ee84
[ 175.70] Hi: 1b08
[ 175.70] Lo: 6c20
[ 175.70] epc : bf001f44 0xbf001f44
This looks like a crash in the decrypt-routine, located in the bootrom.
Any suggestion?
Please check the vmmc driver sources (I don't know which version is available
in OpenWrt),
if it already contains something like this:
const void *ifx_mps_get_decrypt_entrypoint(void)
{
#if defined(SYSTEM_AR9)
return (const void *)0xbf0017c4;
#elif defined(SYSTEM_VR9)
u32 part_number;
part_number = IFX_MPS_CHIPID_PARTNUM_GET(*IFX_MPS_CHIPID);
if ((part_number 0xFFF0) == 0x01C0)
return (const void *)0xbf001ea4;
else
return (const void *)0xbf001f38;
#elif defined(SYSTEM_...)
...
#endif /* SYSTEM_... */
}
I don't know, why the people from the bootrom team did not manage to provide a
constant entry point across all chips/chip-version, but this is another story.
On Sat, Oct 11, 2014 at 5:35 PM, Eddi De Pieri e...@depieri.net wrote:
Hi to all,
I've started to figure out how much work is needed to support fxs on vr9
board like mine.
On latest trunk :
- owsip is missing (i know is bugged with 32mbram)
- ltq-tapidemo is m issing
- lantiq falcon fxs support seems broken
Falcon and vr9 are different SoCs!
It seems to me that by rebasing some patch for falcon should be possible to
make vmmc for vr9 working (or at least to build for now...).
You agree?
Eddi
Best Regards,
Thomas
---
There are two hard things in computer science: cache invalidation, naming
things, and off-by-one errors.
---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
On 15/10/2014 12:10, thomas.lan...@lantiq.com wrote:
Hello Eddi,
Eddi De Pieri wrote on 2014-10-14:
Hi to all,
I've applied to kernel patch for vpe committed for falcon, fixed
for vr9 ltq-vmmc, modified VGV7519 dts for passing new
parameters
console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1
phym=64M mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M
vpe1_wired_tlb_entries=1
Why do you reserve 2M? The voice FW only needs 1M
Now I get:
[ 175.672000] Here I am: #1 [ 175.672000] Here I am: #2 [
175.676000] Here I am: #3 [ 175.68] Here I am: #4 [
175.68] Here I am: #5 [ 175.684000] Here I am:
cpu1_base_addr: 83e0 #6 [ 175.688000] Here I am: #7 [
175.692000] Here I am: #8 [ 175.70] Unhandled kernel
unaligned access[#1]: [ 175.70] CPU: 0 PID: 1516 Comm:
tapidemo Not tainted 3.14.18 #40 [ 175.70] task: 829819b0
ti: 82b54000 task.ti: 82b54000 [ 175.70] $ 0 :
77d95290 bf001f38 cc123456 [ 175.70] $ 4 : a3e0
00082280 8000 [ 175.70] $ 8 : a6e5d6ef
00080080 00ff 91008110 [ 175.70] $12 : 807f807f
293f1500 00fe00fe [ 175.70] $16 : 82b55da0
8296 8296 [ 175.70] $20 : 0001
82b55e88 [ 175.70] $24 :
[ 175.70] $28 : 82b54000 82b55d60 7fd3aec8
8295ee84 [ 175.70] Hi: 1b08 [ 175.70] Lo:
6c20 [ 175.70] epc : bf001f44 0xbf001f44
This looks like a crash in the decrypt-routine, located in the
bootrom.
Any suggestion?
Please check the vmmc driver sources (I don't know which version is
available in OpenWrt), if it already contains something like this:
const void *ifx_mps_get_decrypt_entrypoint(void) { #if
defined(SYSTEM_AR9) return (const void *)0xbf0017c4; #elif
defined(SYSTEM_VR9) u32 part_number;
part_number = IFX_MPS_CHIPID_PARTNUM_GET(*IFX_MPS_CHIPID); if
((part_number 0xFFF0) == 0x01C0) return (const void
*)0xbf001ea4; else return (const void *)0xbf001f38; #elif
defined(SYSTEM_...) ... #endif /* SYSTEM_... */
you can skip this. its lantiqs attempt at obfuscation if i recall, its
a simple xor which can be done on the build host.
John
}
I don't know, why the people from the bootrom team did not manage
to provide a constant entry point across all chips/chip-version,
but this is another story.
On Sat, Oct 11, 2014 at 5:35 PM, Eddi De Pieri e...@depieri.net
wrote:
Hi to all,
I've started to figure out how much work is needed to support
fxs on vr9 board like mine.
On latest trunk : - owsip is missing (i know is bugged with
32mbram) - ltq-tapidemo is m issing - lantiq falcon fxs
support seems broken
Falcon and vr9 are different SoCs!
It seems to me that by rebasing some patch for falcon should be
possible to make vmmc for vr9 working (or at least to build for
now...).
You agree?
Eddi
Best Regards, Thomas --- There are two hard things in computer
science: cache invalidation, naming things, and off-by-one errors.
--- ___ openwrt-devel
mailing list openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq vr9 and fxs
Hi to all, I've applied to kernel patch for vpe committed for falcon, fixed for vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M vpe1_wired_tlb_entries=1 Now I get: [ 175.672000] Here I am: #1 [ 175.672000] Here I am: #2 [ 175.676000] Here I am: #3 [ 175.68] Here I am: #4 [ 175.68] Here I am: #5 [ 175.684000] Here I am: cpu1_base_addr: 83e0 #6 [ 175.688000] Here I am: #7 [ 175.692000] Here I am: #8 [ 175.70] Unhandled kernel unaligned access[#1]: [ 175.70] CPU: 0 PID: 1516 Comm: tapidemo Not tainted 3.14.18 #40 [ 175.70] task: 829819b0 ti: 82b54000 task.ti: 82b54000 [ 175.70] $ 0 : 77d95290 bf001f38 cc123456 [ 175.70] $ 4 : a3e0 00082280 8000 [ 175.70] $ 8 : a6e5d6ef 00080080 00ff 91008110 [ 175.70] $12 : 807f807f 293f1500 00fe00fe [ 175.70] $16 : 82b55da0 8296 8296 [ 175.70] $20 : 0001 82b55e88 [ 175.70] $24 : [ 175.70] $28 : 82b54000 82b55d60 7fd3aec8 8295ee84 [ 175.70] Hi: 1b08 [ 175.70] Lo: 6c20 [ 175.70] epc : bf001f44 0xbf001f44 [ 175.70] Not tainted [ 175.70] ra: 8295ee84 ifx_mps_download_firmware+0x378/0x43c [drv_vmmc] [ 175.70] Status: 1100fd03 KERNEL EXL IE [ 175.70] Cause : 00800014 [ 175.70] BadVA : cc123456 [ 175.70] PrId : 00019555 (MIPS 34Kc) [ 175.70] Modules linked in: rt2800pci rt2800mmio rt2800lib iptable_nat rt2x00pci rt2x00mmio rt2x00lib pppoe nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp nf_conntrack ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables drv_vmmc crc_itu_t crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables pppoatm ppp_generic slhc br2684 atm drv_tapi ipv6 eeprom_93cx6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug [ 175.70] Process tapidemo (pid: 1516, threadinfo=82b54000, task=829819b0, tls=77e7b440) [ 175.70] Stack : 829640f0 cc123456 8040bd94 80408c60 82b55e68 cf68 ffea [ 175.70]82964f90 20004f11 82b55e04 8295ad0c 0007 8296 82961b88 8294c084 [ 175.70]77d13008 00082280 829640f0 2000 2000 [ 175.70]7fe68968 2000560f 829640f0 8294fb5c 82b55ef8 82b01000 ff9c [ 175.70]8004710e 82fd9800 77d13008 000822a0 [ 175.70]... [ 175.70] Call Trace: [ 175.70] [8295ad0c] ifx_mps_ioctl+0x4c8/0x754 [drv_vmmc] [ 175.70] [8294c084] VMMC_ChipAccessInit+0xd4/0xe64 [drv_vmmc] [ 175.70] [8294fb5c] VMMC_Dev_Spec_Ioctl+0x4bc/0x5f0 [drv_vmmc] [ 175.70] [8004710e] __kfifo_alloc+0xfe/0x100 [ 175.70] [8019580c] lookup_fast+0x58/0x2e8 [ 175.70] [8004710e] __kfifo_alloc+0xfe/0x100 [ 175.70] [82846254] TAPI_Ioctl+0xd4/0xda0 [drv_tapi] [ 175.70] [800e837c] do_filp_open+0x3c/0xa4 [ 175.70] [828403a4] 0x828403a4 [ 175.70] [800f7d80] do_vfs_ioctl+0x558/0x5c0 [ 175.70] [8012e6b4] getname_flags+0x40/0x14c [ 175.70] [800f5258] do_sys_open+0x218/0x240 [ 175.70] [8001c034] SyS_ioctl+0x50/0x94 [ 175.70] [8000843c] handle_sys+0x11c/0x140 [ 175.70] [ 175.70] [ 175.70] Code: 3c06 34ca00ff 00aa4824 ac69 8c68 240cc0ff 35070100 ac67 ac600010 [ 175.984000] ---[ end trace 108c9297dfbeb9c8 ]--- It seems kernel crash on /* copy FW image to base address of CPU1 */ IFXOS_CpyFromUser ((IFX_void_t *)cpu1_base_addr, (IFX_void_t *)pFWDwnld-data, pFWDwnld-length)) Any suggestion? On Sat, Oct 11, 2014 at 5:35 PM, Eddi De Pieri e...@depieri.net wrote: Hi to all, I've started to figure out how much work is needed to support fxs on vr9 board like mine. On latest trunk : - owsip is missing (i know is bugged with 32mbram) - ltq-tapidemo is m issing - lantiq falcon fxs support seems broken It seems to me that by rebasing some patch for falcon should be possible to make vmmc for vr9 working (or at least to build for now...). You agree? Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] lantiq vr9 and fxs
Hi to all, I've started to figure out how much work is needed to support fxs on vr9 board like mine. On latest trunk : - owsip is missing (i know is bugged with 32mbram) - ltq-tapidemo is m issing - lantiq falcon fxs support seems broken It seems to me that by rebasing some patch for falcon should be possible to make vmmc for vr9 working (or at least to build for now...). You agree? Eddi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
