Dernier message de la page précédente :

en effet, j'avais pas fait le rapprochement :/
Mais du coup, ça pourrait pas être une solution, plus risquée, mais qui permettrait de lui mettre les paramètres souhaités en espérant qu'il soit reprogrammable le MFD ?

je pense pas, il à dejà dit que la bic elle à rien a voir avec l'rs monitor...

pierrot9538 Sorry but I am not going to help a person that has access to DDT and a proper Renault sonde and that does not know the program functionalities.
Myself, I have searched for more than a year and payed a lot of money to obtain everything and the thought that you or someone else have something like this but you are not learning by yourself is making me angry to be honest. My first interface was made by me on a circuit board ... others have everything yet they don't know all program features.

I will only tell you how it works as a concept, for the reprogramming part , it's enough that I say it is in DDT. The rest, search for it and put some educated questions.

Now, for the BIC, if you want the RS monitor to properly send you the correct info, the key are the RS Banks. You will see that the banks are in MFD but also in BIC. Some BICs accept the RS Bank slots to be configured (new hardware versions like the one with ...105R) others need to be reprogrammed (not all of the work). There are several serial numbers and versions of BIC. I told you the one that works.
For the others you need to play with them and try to reconfigure/reprogram.

Please note again that activating the RS Monitor has nothing to do with the BIC. Only after you have it, on a non RS car, you need to tweek the BIC in order to receive the data.

Heureusement que tous les gros pros de la mécanique de ce forum (et qui ont du super matériel) ne font pas ce genre de réflexions à tous ceux qui cherchent de l'aide et qui n'y connaissent pas grand chose.....

C'est pas parce-que tu galére que les autres doivent aussi galérer...
Le but du forum c'est l'entraide... Sinon tu passes ton chemin.

Je trouve ce genre de réflexion pitoyable.
J'espère juste qu'il ne sera pas confronté à un problème pour lequel il ne maîtrise pas son sujet !

bah c'est déjà expliqué ici je crois pour le rs mon d'une 3Rs : http://www.cliors-concept.com/configura ... 94-15.html

Après soit tu proposes une prestation en tant que pro dans ton garage avec la garantie qui va avec soit t'es sur un forum communautaire et tu aides la communauté; chacun son idéologie ; c'est comme le type qui vendent les cd / url avec clip & co ...

Well i must admit I am a bit disappointed. I don't really understand what you want. Aside from someone to tell you word by word what to do and you obtain fast what you wanted.

I fail to see how I did not contribute to this forum. I already told everybody that the activation cannot be done by any normal tool or option. This also includes CLIP but it seems nobody believes me when i say it. If you want a new screen, just take a VIN from a car that has it and order a spare one. It will have the RS Monitor. Otherwise once it left the factory without RS Monitor, normally it cannot be reconfigured with it. You probably forget that my experience and a lot of lost time is what enables me now to tell you not to search in that direction too. Is all my research that lets me tell you that the BIC is only used after the activation and not to do it and that the bank slots are in fact the info and parameters transmitted from the ECM to the MFD.
I already told everybody that I managed to do it by means of hardware. I had to buy a lot of electronics equipment to do it and it cost me a lot. Even if i would try to teach someone, the investment in tools is greater than buying a second hand display with RS Monitor already activated.
And now because I cannot give you some magic way to do it yourself in 5 minutes i am pitiful, I don't think so, maybe you are...
More than this, when you have guys that invested in something (time and resources) and made it possible for you, if they ask for money you say they are bad? But you forget that without them you wouldn't have the possibility at all. And second, did you ever stop to think that this type of guys you should maybe sustain in order to have options for the future when Renault is not giving any? ...

I am sorry I ever said anything. I find it stupid to be judged when I was really trying to help even if it meant not to let people go in the wrong direction. What was my crime, that I asked a guy to look into a menu (just click on it and see where reprogramming is written) instead of just asking me without any effort? To share is one thing, this is another ...
Mathieu78 - it's one thing not to know to much and another to refuse to look into a menu of an application

In any case good luck people, me out ...

Come on man, really, this is more than off topic, why he didn't open a thread asking forum informations/guides forum DDT? Here, actually we're talking about something else... Novas you are not obliged ti answer every question, it's up to you... Stay, please, really, stay

I'm going to connect directly to eMMC. Does anyone have a description of pads? I know where VCC and GND are but I still need CMD, CLK and DATA0. If nobody knows, I intend to desolder it.

simrucci Thanks for your support.
ebt25 you can try but be aware that because of the OMAP 3630 HS partition signing algorithm, you will not be able to change anything. If you change 1 bit on the image that you will extract , and try to write it back, the unit will not work anymore. In any case what you will extract from that 2GB memory will be pretty much what you can find in a ttpkg file from an update that you receive directly by R-Link Toolbox. What we need is the private key from the guys that make the updates or a way to trick the bootloader not to verify the zimage file when it is loaded.
I have been working on the bootloader for 3 months but I am still unable to break it.

Below you can see an example of how the unit boots.
Observe the : Verifying device tree...
libfdt fdt_setprop() failed
Verifying executable image signature ...

-------------------------------------------------------------------------

Texas Instruments X-Loader 1.41 (Mar 30 2012 - 11:31:59)
Starting OS Bootloader from NOR ...


U-Boot 1.3.41077437-dirty (Oct 3 2012 - 17:18:30)

OMAP3630-HS rev 2, CPU-OPP2 L3-200MHz
OMAP3630 Strasbourg 1.3 Version + mDDR (Boot MMC)
DRAM: 512 MB
Using default environment

In: serial
Out: serial
Err: serial

[APTS Logo/]

## Executing script at 80a25a20
get_format
-------- 1 --------
## Executing script at 80a25ddc
get_format
-------- 1 --------
Using device mmc0, partition 2

Loading from block device mmc device 0, partition 2: Name: xxa2
Type: U-Boot File:/uboot.conf
** File not found /uboot.conf
'uboot.conf' ignored
Hit any key to stop autoboot: 0
## Executing script at 80a257d8
get_format
-------- 1 --------
Not executing bootloader applet
Loaded device-tree at address 83300000 of length 2616 bytes
Using device mmc0, partition 2

Loading from block device mmc device 0, partition 2: Name: xxa2
Type: U-Boot File:/zImage

2584680 bytes read
Boot with gzipped Image
Verifying device tree...
libfdt fdt_setprop() failed
Verifying executable image signature ...

Starting kernel ...

Resetting boot powerdown watchdog
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32.9 (svc_quickbuild@nlsrvup-qbs08) (gcc version 4.3.3 (TomTom CipherWizardry 2009q1_203-474426) ) #2 PREEMPT Wed May 29 11:06:08 CEST 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Strasbourg A2
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] factory data: bootmem reserved successful
[ 0.000000] DIE ID: 118C0002FE380000015EEBD90501901A
[ 0.000000] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
[ 0.000000] omap_sam_base (VA) == 0xfe40f000
[ 0.000000] omap_sram_start (PA) == 0x4020f000
[ 0.000000] omap_sram_size (SIZE) == 0x1000
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
[ 0.000000] Reserving 3145728 bytes SDRAM for VRAM
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: root=/dev/mmcblk0p2 console=ttyO2,115200 androidboot.console=ttyO2 sysboot_mode=cold init=/init videoout=omap24xxvout vram=0x300000,0x83000000 lpj=2334720 brick=0
[ 0.000000]
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 512MB = 512MB total
[ 0.000000] Memory: 504064KB available (4304K code, 1106K data, 492K init, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0083000 ( 492 kB)
[ 0.000000] .text : 0xc0083000 - 0xc04b7000 (4304 kB)
[ 0.000000] .data : 0xc04d2000 - 0xc0518d60 ( 284 kB)
[ 0.000000] SLUB: Genslabs=9, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:402
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
[ 0.000000] Total of 96 interrupts on 1 active controller
[ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
[ 0.000000] Reprogramming SDRC clock to 400000000 Hz
[ 0.000000] GPMC revision 5.0
[ 0.000000] OMAP GPIO hardware version 2.5
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Calibrating delay loop (skipped) preset value.. 597.64 BogoMIPS (lpj=2334720)
[ 0.000000] Security Framework initialized
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Initializing cgroup subsys freezer
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 0.000000] vgpio vgpio.0: pin #403 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: pin #412 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: pin #413 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: pin #415 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: pin #423 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: pin #458 is tagged as not connected!
[ 0.000000] vgpio vgpio.0: registered 59 GPIOs (@400)
[ 0.000000] Strasbourg_tvp515x: Driver registration Starting
[ 0.000000] Strasbourg_tvp515x: Driver registration complete
[ 1.390869] OMAP DMA hardware revision 5.0
[ 1.390930] Reserving DMA channels 0 and 1 for HS ROM code
[ 1.391937] offenburg::flipflop: Registered
[ 1.392333] omap_vout: Driver registration starting
[ 1.411132] bio: create slab <bio-0> at 0
[ 1.413055] SCSI subsystem initialized
[ 1.415679] usbcore: registered new interface driver usbfs
[ 1.415924] usbcore: registered new interface driver hub
[ 1.416168] usbcore: registered new device driver usb
[ 1.416595] i2c_omap i2c_omap.1: bus 1 rev4.0 at 400 kHz
[ 1.441986] twl4030: PIH (irq 7) chaining IRQs 368..375
[ 1.442016] twl4030: power (irq 373) chaining IRQs 376..383
[ 1.442382] twl4030: gpio (irq 368) chaining IRQs 384..401
[ 1.444244] vgpio vgpio.1: pin #600 is tagged as not connected!
[ 1.444396] vgpio vgpio.1: pin #602 is tagged as not connected!
[ 1.444641] vgpio vgpio.1: registered 5 GPIOs (@600)
[ 1.445709] regulator: VUSB1V5: 1500 mV normal standby
[ 1.446166] regulator: VUSB1V8: 1800 mV normal standby
[ 1.446594] regulator: VUSB3V1: 3100 mV normal standby
[ 1.448333] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[ 1.449188] regulator: VMMC1: 3000 mV normal standby
[ 1.449645] regulator: VDAC: 1800 mV normal standby
[ 1.450561] regulator: VAUX2: 1800 mV normal standby
[ 1.451019] regulator: VDVI: 1800 mV normal standby
[ 1.451934] regulator: VAUX1: 3000 mV normal standby
[ 1.452911] regulator: VAUX3: 1800 mV normal standby
[ 1.453094] i2c_omap i2c_omap.2: bus 2 rev4.0 at 100 kHz
[ 1.453582] i2c_omap i2c_omap.3: bus 3 rev4.0 at 50 kHz
[ 1.454193] LinuxPPS API ver. 1 registered
[ 1.454193] Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 1.455871] Bluetooth: Core ver 2.15
[ 1.456115] NET: Registered protocol family 31
[ 1.456146] Bluetooth: HCI device and connection manager initialized
[ 1.456146] Bluetooth: HCI socket layer initialized
[ 1.961791] Switching to clocksource 32k_counter
[ 1.964508] musb_hdrc: version 6.0, musb-dma, peripheral, debug=0
[ 1.964569] musb_init_controller: doing clk_get
[ 1.964721] musb_hdrc: USB Peripheral mode controller at fa0ab000 using DMA, IRQ 92
[ 1.965118] NET: Registered protocol family 2
[ 1.965240] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 1.965454] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 1.965881] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 1.966186] TCP: Hash tables configured (established 16384 bind 16384)
[ 1.966217] TCP reno registered
[ 1.966308] NET: Registered protocol family 1
[ 1.973419] dspbridge_init: 600000 bytes @ 80a00000
[ 1.975097] Strasbourg: power supply driver loaded
[ 1.975311] omap-iommu omap-iommu.0: isp registered
[ 1.976104] iovmm-omap initialized isp, major: 252, base-minor: 0
[ 1.976715] fdtexport driver, (c) 2009 TomTom BV
[ 1.977416] ttcrypto: found version 1 tt_crypto context
[ 1.991088] ashmem: initialized
[ 1.991424] msgmni has been set to 985
[ 1.992340] alg: No test for stdrng (krng)
[ 1.992401] io scheduler noop registered (default)
[ 2.047912] OMAP DSS rev 2.0
[ 2.047973] OMAP DISPC rev 3.0
[ 2.048034] OMAP VENC rev 2
[ 2.048370] OMAP DSI rev 1.0
[ 2.066467] Loop count exceeded in check SR I2C write
[ 2.067687] omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
[ 2.068206] omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
[ 2.068572] omap-hsuart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
[ 2.757598] console [ttyO2] enabled
[ 2.761505] Hiding boot partition 0...
[ 2.767150] mmc0: new high speed MMC card at address 0001
[ 2.773956] mmcblk0: mmc0:0001 M2G1HF 1.86 GiB
[ 2.780364] mmcblk0: p2
[ 2.786499] loop: module loaded
[ 2.792358] PPP generic driver version 2.4.2
[ 2.797332] PPP Deflate Compression module registered
[ 2.802795] PPP BSD Compression module registered
[ 2.807769] tun: Universal TUN/TAP device driver, 1.6
[ 2.813079] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 2.819915] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.828460] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 2.834564] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
[ 2.842529] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 2.860382] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 2.867065] usb usb1: configuration #1 chosen from 1 choice
[ 2.873382] hub 1-0:1.0: USB hub found
[ 2.877441] hub 1-0:1.0: 3 ports detected
[ 2.985351] ehci-omap ehci-omap.0: Resetting the 5V75 VBUS line...
[ 3.040557] usbcore: registered new interface driver cdc_acm
[ 3.046508] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 3.055511] Initializing USB Mass Storage driver...
[ 3.061065] usbcore: registered new interface driver usb-storage
[ 3.067443] USB Mass Storage support registered.
[ 3.072570] usbcore: registered new interface driver libusual
[ 3.079071] usbcore: registered new interface driver usbserial
[ 3.085235] usbserial: USB Serial Driver core
[ 3.090057] USB Serial support registered for GSM modem (1-port)
[ 3.096679] usbcore: registered new interface driver option
[ 3.102539] option: v0.7.2:USB Driver for GSM modems
[ 3.107971] USB Serial support registered for Sierra USB modem
[ 3.114318] usbcore: registered new interface driver sierra
[ 3.120239] sierra: v.1.3.8:USB Driver for Sierra Wireless USB modems
[ 3.127227] usbcore: registered new interface driver usb_ehset_test
[ 3.134185] android_register_function acm
[ 3.140350] using rtc device, twl_rtc, for alarms
[ 3.145294] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[ 3.152130] twl_rtc twl_rtc: Power up reset detected.
[ 3.158111] twl_rtc twl_rtc: Enabling TWL-RTC.
[ 3.163452] i2c /dev entries driver
[ 3.170501] Linux video capture interface: v2.00
[ 3.177001] omap-previewer omap-previewer: omap-previewer: Registered preview wrapper
[ 3.186859] omap3isp omap3isp: Revision 15.0 found
[ 3.192047] omap-iommu omap-iommu.0: isp: version 1.1
[ 3.201599] OMAP hwmon driver
[ 3.207458] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
[ 3.214660] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 3.223632] Bluetooth: HCI UART driver ver 2.2
[ 3.228332] Bluetooth: HCI H4 protocol initialized
[ 3.233367] Bluetooth: HCI BCSP protocol initialized
[ 3.238586] Bluetooth: HCILL protocol initialized
[ 3.243560] cpuidle: using governor ladder
[ 3.247863] cpuidle: using governor menu
[ 3.253631] usbcore: registered new interface driver usbhid
[ 3.259582] usbhid: v2.6:USB HID core driver
[ 3.264831] logger: created 64K log 'log_main'
[ 3.269897] logger: created 256K log 'log_events'
[ 3.275146] logger: created 64K log 'log_radio'
[ 3.280151] logger: created 64K log 'log_system'
[ 3.285614] CSR_BC: csr-bc: Probing CSR BlueCore mode driver.
[ 3.292388] tomtom-gps Driver: Probed.
[ 3.296325] gps: device registration: name="offenburg"
[ 3.302124] tomtom-gps Driver: Registering rfkill for GPS.
[ 3.308135] tomtom-gps Driver: Initialized.
[ 3.312744] flipflop driver, (c) 2009 TomTom BV
[ 3.317810] TomTom CAN-Microprocessor Driver, (C) 2008 TomTom BV
[ 3.325408] new PPS source tomtom-pps at ID 0
[ 3.330108] tomtom-pps tomtom-pps: successfully registered pps source at 0.
[ 3.337646] tomtom-pps: successfully registered driver.
[ 3.343139] suicide_alarm driver, (c) 2011 TomTom BV
[ 3.348937] Advanced Linux Sound Architecture Driver Version 1.0.21.
[ 3.356353] ALSA device list:
[ 3.359466] No soundcards found.
[ 3.363128] Netfilter messages via NETLINK v0.30.
[ 3.368194] nf_conntrack version 0.5.0 (7882 buckets, 31528 max)
[ 3.374755] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[ 3.382568] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[ 3.390899] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 3.397521] ctnetlink v0.93: registering with nfnetlink.
[ 3.403320] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.409057] TCP cubic registered
[ 3.412475] NET: Registered protocol family 17
[ 3.417205] Bluetooth: L2CAP ver 2.14
[ 3.421051] Bluetooth: L2CAP socket layer initialized
[ 3.426391] Bluetooth: SCO (Voice Link) ver 0.6
[ 3.431152] Bluetooth: SCO socket layer initialized
[ 3.436492] Bluetooth: RFCOMM TTY layer initialized
[ 3.441680] Bluetooth: RFCOMM socket layer initialized
[ 3.447113] Bluetooth: RFCOMM ver 1.11
[ 3.451049] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.456665] Bluetooth: BNEP filters: protocol multicast
[ 3.462188] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.469024] Power Management for TI OMAP3.
[ 3.475189] Unable to Changelevel for resource vdd1_opp to 0
[ 3.481201] Error: could not refresh resources
[ 3.486450] SR: Nvalues not fused for 1.2G, disabled
[ 3.491668] SR: Nvalues not fused for 1G, disabled
[ 3.496795] SR2:Fused Nvalues for VDD1OPP3 11193534
[ 3.501953] SR2:Fused Nvalues for VDD1OPP2 10126585
[ 3.507080] SR2:Fused Nvalues for VDD1OPP1 10082000
[ 3.512207] sr1_opp_margin[1]=37500
[ 3.515869] sr1_opp_margin[2]=37500
[ 3.519561] sr1_opp_margin[3]=37500
[ 3.523223] steps added, volt will be recaliberated automatically
[ 3.529663] SR2:Fused Nvalues for VDD2OPP1 99f2eb
[ 3.534637] SR2:Fused Nvalues for VDD2OPP2 10066063
[ 3.539794] SmartReflex driver initialized
[ 4.865386] clock: dpll2_ck failed transition to 'bypassed'
[ 4.919281] at24 3-0050: 8192 byte at24 EEPROM (writable)
[ 4.928222] input: TSC2007 Touchscreen as /devices/virtual/input/input0
[ 4.935974] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 4.945037] DMA transaction error with device 0
[ 4.950378] OMAP DISPCONTROL read (stallmode)0
[ 4.955108] OMAP DISPCONTROL read (gpout)1
[ 4.959381] OMAP DISPCONTROL read (stallmode)1
[ 4.964721] DPI set dsi clk
[ 5.110778] DPI set dsi clk
[ 5.123504] regulator_init_complete: incomplete constraints, leaving VAUX3 on
[ 5.131378] regulator_init_complete: incomplete constraints, leaving VAUX1 on
[ 5.139038] regulator_init_complete: incomplete constraints, leaving VAUX2 on
[ 5.148986] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
[ 5.157836] omap3 omap3isp CSI memvs initted
[ 5.163146] Registered led device: lcd-backlight
[ 5.168304] Freeing init memory: 492K
[APTS InitRamFS]

TOMTOM initramfs compiled on May 29 2013 11:04:56

initramfs: BOOTMODE: cold

AUTOTEST: root=/dev/mmcblk0p2

initramfs: Checking filesystem on: /dev/mmcblk0p2

Opening the watchdog...
Kicking the watchdog... (3)

/dev/mmcblk0p2: recovering journal
/dev/mmcblk0p2: Superblock last mount time is in the future. FIXED.
/dev/mmcblk0p2: clean, 2246/122400 files, 104805/488416 bl[ 7.011779] omap_wdt: Unexpected close, not stopping!
ocks
initramfs: fsck returned: 0
initramfs: Attempti[ 7.021881] kjournald starting. Commit interval 5 seconds
ng to mount /dev/mmcblk0p2 on /internalstorage...

initramfs: [ 7.033050] EXT3 FS on mmcblk0p2, Trying to mount internal journal
/dev/mmcblk0p2 a[ 7.040832] EXT3-fs: mounted filesystem with ordered data mode.
s ext3 (options=barrier=1)
initramfs: Checking for system update from directory[ 7.054595] signedloop: using 76866 data pages, 377 L0 pages and 2 L1 pages
data/ttcontent/common/installed.

initramfs: Failed to stat zImage due to No such file or directory.

initramfs: Checking for system update from directory data/ttcontent.

initramfs: Failed to stat zImage due to No such file or directory.

initramfs: Setting up loop device /dev/loop0 using rootfs.img

initramfs: Creating root filesystem...

initramfs: Trying to mount /dev/loop0 as squashfs (options=none)
[ 7.116546] signedloop: activated hash checking on device loop0
initramfs: Trying to mount /dev/loop0 as ext3 (options=barrier=1)
[ 7.130493] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.136749] kjournald starting. Commit interval 5 seconds
AUTOTEST: NAVCORE starting

[ 7.151153] omap_wdt: Unexpected close, not stopping!
initramfs: Checking CAN firmware

[ 7.169647] Process /system/bin/can_firmware_tool requested an executable stack, ignoring...
can_swl: GetDesiredSwVersion(): No file named /system/ttdaemon/can_micro_firmware/mfd_can_app1.img
can_swl: File /system/ttdaemon/can_micro_fir[ 7.229034] omap_wdt: Unexpected close, not stopping!
mware/mfd_can_app1.img not available, try the backward compatible file /system/ttdaemon/can_micro_firmware/strasbourg_can_app1.img.
can_swl: GetDesiredSwVersion(): No file named /system/ttdaemon/can_micro_firmware/strasbourg_can_app1.img
can_swl: DoCanMicroVersionCheck: bootloader:1177652->0 application:1177652->1177652
can_swl: There is no desired CAN micro bootloader SW version. The CAN micro bootloader SW upgrade mechanism is blocked.
can_swl: Actual CAN micro application SW version is as desired: 1177652
initramfs: can firmware matches

initramfs: Checking EOL settings

initramfs: EOL s[ 7.439331] omap_wdt: Unexpected close, not stopping!
ettings: CONFIGURED

[/APTS InitRamFS]

AUTOTEST: starting init

[ 7.772521] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 8.050537] Process /system/bin/fortytwo requested an executable stack, ignoring...
[ 8.578277] No device for DAI BC6
[ 8.668670] proc_load: Processor Loaded /system/lib/dsp/baseimage.dof
[ 8.676116] omap mailbox rev 4.0
[ 8.682373] proc_start: dsp in running state
[ 8.687194] procwrap_detach: deprecated dspbridge ioctl
[ 8.698944] No device for DAI omap-mcbsp-dai-0
[ 8.704040] No device for DAI omap-mcbsp-dai-1
[ 8.708862] No device for DAI omap-mcbsp-dai-2
[ 8.714385] No device for DAI omap-mcbsp-dai-3
[ 8.719085] No device for DAI omap-mcbsp-dai-4
[ 8.801971] No device for DAI twl4030
[ 8.806121] No device for DAI twl4030 Voice
[ 8.810607] No device for DAI twl4030 Clock
[ 8.921630] No device for DAI UDA1334
[ 9.001617] Strasbourg SoC init
[ 9.008483] TWL4030 Audio Codec init
[ 9.014129] asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
[ 9.020324] asoc: BC6 <-> omap-mcbsp-dai-2 mapping ok
[ 9.132324] UDA1334 Audio Codec 0.1
[ 9.136566] asoc: UDA1334 <-> omap-mcbsp-dai-1 mapping ok
[ 9.455963] usbcore: registered new interface driver snd-usb-audio
[ 9.646820] Video decoder chip id 5151 detected!
[ 9.666351] Registered tvp5150 video decoder
[ 9.746856] omap_vout: registered and initialized video device 3 [v4l2]
[ 9.920623] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 9.927612] ohci-omap3 ohci-omap3.0: OMAP3 OHCI Host Controller
[ 9.934906] ohci-omap3 ohci-omap3.0: new USB bus registered, assigned bus number 2
[ 9.942993] ohci-omap3 ohci-omap3.0: irq 76, io mem 0x48064400
[ 10.055938] usb usb2: configuration #1 chosen from 1 choice
[ 10.062408] hub 2-0:1.0: USB hub found
[ 10.071594] hub 2-0:1.0: 3 ports detected
[ 10.094787] ohci-omap3 ohci-omap3.0: trigging poll (state: 1)...
[ 10.263977] omapflash: Found 1 x16 devices at 0x0 in 16-bit bank
[ 10.270996] Intel/Sharp Extended Query Table at 0x0039
[ 10.276641] Intel/Sharp Extended Query Table at 0x0039
[ 10.282104] Intel/Sharp Extended Query Table at 0x0039
[ 10.287658] Intel/Sharp Extended Query Table at 0x0039
[ 10.293212] Intel/Sharp Extended Query Table at 0x0039
[ 10.298767] Intel/Sharp Extended Query Table at 0x0039
[ 10.304321] Using auto-unlock on power-up/resume
[ 10.309295] cfi_cmdset_0001: Erase suspend on write enabled
[ 10.315917] cmdlinepart partition parsing not available
[ 10.321502] Creating 1 MTD partitions on "omapflash":
[ 10.326782] 0x000000000000-0x000000400000 : "nor_part0"
[ 10.344787] ohci-omap3 ohci-omap3.0: trigging poll (state: 1)...
[ 10.594757] ohci-omap3 ohci-omap3.0: trigging poll (state: 1)...
[ 10.844757] ohci-omap3 ohci-omap3.0: trigging poll (state: 1)...
[ 11.094787] ohci-omap3 ohci-omap3.0: trigging poll (state: 1)...
[ 11.240936] input: MSM-keypad as /devices/virtual/input/input1
[ 11.249267] input: CSW-keypad as /devices/virtual/input/input2
[ 11.817779] Callback set_scenario not implemented in /opt/buildagent/workspace/root/platform/Froyo/Nightly/p-a-strasbourgmfd10-kz/ngl-strbdev-main/Strasbourg-build-noprepare/platform/mydroid/kernel/android-2.6.32/drivers/tomtom/sound/uda1334.c
[ 12.720703] warning: `zygote' uses 32-bit capabilities (legacy support in use)
[/APTS Android started][ 20.658660] request_suspend_state: wakeup (3->0) at 19314056442 (2000-01-01 00:00:17.009674064 UTC)
[ 27.700958] Callback set_scenario not implemented in /opt/buildagent/workspace/root/platform/Froyo/Nightly/p-a-strasbourgmfd10-kz/ngl-strbdev-main/Strasbourg-build-noprepare/platform/mydroid/kernel/android-2.6.32/drivers/tomtom/sound/uda1334.c
[ 28.014892] OMAP DISPCONTROL read (stallmode)0
[ 28.026184] OMAP DISPCONTROL read (gpout)1
[ 28.052947] OMAP DISPCONTROL read (stallmode)1
[ 28.066070] DPI set dsi clk
[ 28.243804] DPI set dsi clk

NovaS:
Bad night, Bad mood last day ! Sorry.
Thanks for your continuons support.

It's ok ;) Thanks :)

Well, let's start the day with some very very stupid questions:
1: of course no chance of interrupt/inject some code in bootloader, right?

2: 7.772521] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' of course se can not just put sh file for recovery, right?

3:[ 1.454193] LinuxPPS API ver. 1 registered
[ 1.454193] Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> of course, It wouldn't be helpful asking this guy for anythig, right?

End of stupid questions...

1. There is no chance to interrupt booting process.
You can only change boot order - resistors and tespoints on PCB

3. It is standard linux distribution, so this guy has nothing to do with our R-Link.

Depending on sys_boot pin
configuration during the reset (leftmost column), the ROM code tries to boot on the first booting device
listed. If the boot fails on this first booting device, the ROM code tries the second booting device, then the
third, then the fourth.


Now it's worth:

Booting Sequence When SYS.BOOT [5] = 0
0b10011 = XIP -> UART3


If you change SYS.BOOT [5] to 1, it will be: UART3 -> XIP.
Then you can load your bootloader via uart, change the kernel, patch navcore, etc.


My friend Vèon found this on russian forum, there'also the link to cpu datasheet... 3k and more pages...

Yes, you're right.
TI deliver some development tools and booting software. Also you can boot from USB (USB Gadget/Ethernet)

This looks like a white list of devices that can be connected to R-Link.
https://github.com/egonalter/R-Link_ker ... hitelist.h
I'm thinking about two solutions now. USB-USB bridge (USB networking cable) or usb networking adapter (CONFIG_USB_USBNET).