Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Sansa Fuze+
« previous next »
  • Print
Pages: 1 ... 5 6 [7] 8 9 ... 54

Author Topic: Sansa Fuze+  (Read 308261 times)

Offline danger355

  • Member
  • *
  • Posts: 5
Re: Sansa Fuze+
« Reply #90 on: July 11, 2011, 07:03:56 PM »
Quote from: pamaury on July 11, 2011, 06:00:40 AM
Hello,
the normal steps to build sbtoelf is to have an up to date svn checkout and to type make in utils/sbtools. You error definitely indicate something wrong; are you sure you have the sbtoelf.c ?
Then you should follow the steps in the wiki SansaFuzePlusPort page, everything is written. The directory in which is happen is not important, a fresh one will do.

Hi pamaury,

yes, i definitely have sbtoelf.c in the /sbtools folder. i followed the steps in the wiki, but it's still very possible i did something incorrect, so i'll try starting from scratch soon and see if that changes anything
Logged

Offline metaphys

  • Member
  • *
  • Posts: 133
Re: Sansa Fuze+
« Reply #91 on: July 15, 2011, 06:04:56 AM »
@danger355
Starting from scratch can you give the exact sequence of command you type?

@Pamaury
ok I suppose I've build the stuff correctly and transfert it to the device:
Code: [Select]
root@debian:/home/jean-louis/Informatique/Rockboxfuse+/rockbox/build# ../utils/imx_hid_recovery/imx_hid_recovery 1024 bootloader.sb
Transfer size: 1024
ret 0
root@debian:/home/jean-louis/Informatique/Rockboxfuse+/rockbox/build#

But nothing hapen... Screen stay black nothing responding. Same after uplugging it. It stayed not responding for awhile and finally after several attempt repluging it bring the OF control back
for info here the dmesg sequence:
Code: [Select]
[  885.657178] usb 1-2: new high speed USB device using ehci_hcd and address 11
[  885.772049] usb 1-2: New USB device found, idVendor=066f, idProduct=3780
[  885.772058] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  885.772065] usb 1-2: Product: ROM Recovery
[  885.772069] usb 1-2: Manufacturer: Sigmatel, Inc.
[  885.773332] generic-usb: probe of 0003:066F:3780.0004 failed with error -22
[ 1151.536349] usb 1-2: USB disconnect, address 11
[ 1184.911095] usb 1-2: new high speed USB device using ehci_hcd and address 12
[ 1190.021141] usb 1-2: device descriptor read/64, error -71
[ 1195.232065] usb 1-2: device descriptor read/64, error -71
[ 1195.435091] usb 1-2: new high speed USB device using ehci_hcd and address 13
[ 1200.545136] usb 1-2: device descriptor read/64, error -71
[ 1205.756061] usb 1-2: device descriptor read/64, error -71
[ 1205.959102] usb 1-2: new high speed USB device using ehci_hcd and address 14
[ 1209.184143] usb 1-2: device not accepting address 14, error -71
[ 1209.235413] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1215.166156] usb 1-2: new high speed USB device using ehci_hcd and address 16
[ 1220.276168] usb 1-2: device descriptor read/64, error -71
[ 1225.487141] usb 1-2: device descriptor read/64, error -71
[ 1225.690165] usb 1-2: new high speed USB device using ehci_hcd and address 17
[ 1230.800052] usb 1-2: device descriptor read/64, error -71
[ 1233.338240] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1239.412152] usb 1-2: new high speed USB device using ehci_hcd and address 18
[ 1244.522150] usb 1-2: device descriptor read/64, error -71
[ 1249.733077] usb 1-2: device descriptor read/64, error -71
[ 1249.936105] usb 1-2: new high speed USB device using ehci_hcd and address 19
[ 1250.744340] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1261.633078] usb 1-2: new high speed USB device using ehci_hcd and address 20
[ 1266.743069] usb 1-2: device descriptor read/64, error -71
[ 1271.954073] usb 1-2: device descriptor read/64, error -71
[ 1272.157078] usb 1-2: new high speed USB device using ehci_hcd and address 21
[ 1277.267168] usb 1-2: device descriptor read/64, error -71
[ 1282.478151] usb 1-2: device descriptor read/64, error -71
[ 1282.681140] usb 1-2: new high speed USB device using ehci_hcd and address 22
[ 1286.033143] usb 1-2: device not accepting address 22, error -71
[ 1286.084330] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1290.087183] usb 1-2: new high speed USB device using ehci_hcd and address 24
[ 1295.197139] usb 1-2: device descriptor read/64, error -71
[ 1300.408075] usb 1-2: device descriptor read/64, error -71
[ 1300.611121] usb 1-2: new high speed USB device using ehci_hcd and address 25
[ 1305.721057] usb 1-2: device descriptor read/64, error -71
[ 1310.932142] usb 1-2: device descriptor read/64, error -71
[ 1311.135048] usb 1-2: new high speed USB device using ehci_hcd and address 26
[ 1316.541049] usb 1-2: device not accepting address 26, error -71
[ 1316.643103] usb 1-2: new high speed USB device using ehci_hcd and address 27
[ 1322.049060] usb 1-2: device not accepting address 27, error -71
[ 1322.049097] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1323.576058] usb 1-5: new high speed USB device using ehci_hcd and address 28
[ 1328.686082] usb 1-5: device descriptor read/64, error -71
[ 1333.897118] usb 1-5: device descriptor read/64, error -71
[ 1334.100098] usb 1-5: new high speed USB device using ehci_hcd and address 29
[ 1339.210124] usb 1-5: device descriptor read/64, error -71
[ 1343.022333] hub 1-0:1.0: unable to enumerate USB device on port 5
[ 1345.970065] usb 1-5: new high speed USB device using ehci_hcd and address 30
[ 1351.080122] usb 1-5: device descriptor read/64, error -71
[ 1356.291129] usb 1-5: device descriptor read/64, error -71
[ 1356.494118] usb 1-5: new high speed USB device using ehci_hcd and address 31
[ 1361.604119] usb 1-5: device descriptor read/64, error -71
[ 1366.815142] usb 1-5: device descriptor read/64, error -71
[ 1367.018124] usb 1-5: new high speed USB device using ehci_hcd and address 32
[ 1372.424057] usb 1-5: device not accepting address 32, error -71
[ 1372.526073] usb 1-5: new high speed USB device using ehci_hcd and address 33
[ 1377.932139] usb 1-5: device not accepting address 33, error -71
[ 1377.932177] hub 1-0:1.0: unable to enumerate USB device on port 5
[ 1378.174179] usb 4-1: new full speed USB device using uhci_hcd and address 2
[ 1383.286094] usb 4-1: device descriptor read/64, error -71
[ 1388.498142] usb 4-1: device descriptor read/64, error -71
[ 1388.701175] usb 4-1: new full speed USB device using uhci_hcd and address 3
[ 1393.812150] usb 4-1: device descriptor read/64, error -71
[ 1399.023136] usb 4-1: device descriptor read/64, error -71
[ 1399.226156] usb 4-1: new full speed USB device using uhci_hcd and address 4
[ 1404.632075] usb 4-1: device not accepting address 4, error -71
[ 1404.734138] usb 4-1: new full speed USB device using uhci_hcd and address 5
[ 1410.140052] usb 4-1: device not accepting address 5, error -71
[ 1410.140095] hub 4-0:1.0: unable to enumerate USB device on port 1
[ 1482.158176] usb 1-5: new high speed USB device using ehci_hcd and address 34
[ 1482.273176] usb 1-5: New USB device found, idVendor=0781, idProduct=74e0
[ 1482.273184] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1482.273191] usb 1-5: Product: Sansa Fuze+
[ 1482.273196] usb 1-5: Manufacturer: SanDisk
[ 1482.273200] usb 1-5: SerialNumber: 0000000100001C150002DCDF27F55C15
[ 1482.274204] scsi8 : usb-storage 1-5:1.0
[ 1483.274939] scsi 8:0:0:0: Direct-Access     SanDisk  Sansa Fuze+      0100 PQ: 0 ANSI: 4
[ 1483.275556] scsi 8:0:0:1: Direct-Access     SanDisk  Sansa Fuze+      0100 PQ: 0 ANSI: 4
[ 1483.279931] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.280521] sd 8:0:0:0: [sdb] Write Protect is off
[ 1483.280529] sd 8:0:0:0: [sdb] Mode Sense: 3e 00 00 00
[ 1483.285855] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.285861] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.288148] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 1483.292763] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.294408] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.294413] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.295711]  sdb: sdb1
[ 1483.298043] sd 8:0:0:0: [sdb] 7748864 2048-byte logical blocks: (15.8 GB/14.7 GiB)
[ 1483.299414] sd 8:0:0:0: [sdb] Incomplete mode parameter data
[ 1483.299418] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 1483.299422] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1483.727360] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 1561.041434] WARNING! power/level is deprecated; use power/control instead
[ 1561.100383] usb 1-5: USB disconnect, address 34
« Last Edit: July 15, 2011, 06:07:17 AM by metaphys »
Logged

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #92 on: July 15, 2011, 06:08:48 AM »
@metaphys
It used to work on your device, didn't it ? I haven't change much in the lcd code recently :-/
Did you account for the change in the bootloader.db file ? I'm now using the first 3 stages. Without the first one, usb is likely to not work properly. But that doesn't explain why the screen stays black.
« Last Edit: July 15, 2011, 06:13:15 AM by pamaury »
Logged
Please don't PM me, use our IRC channel instead.

Offline metaphys

  • Member
  • *
  • Posts: 133
Re: Sansa Fuze+
« Reply #93 on: July 15, 2011, 06:28:01 AM »
Yes it used to work  :-\

I did this new build from scratch and followed the instruction on the port's page so I guess i did have the new db file... Confusing indeed. Let me know if I should test something else  :D
Logged

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #94 on: July 15, 2011, 06:32:28 AM »
If you are motivated, you could try to bisect to see which revision of the svn caused that. You can also try to change this in lcd-fuzeplus.c:
replace
Code: [Select]
default:
            lcd_kind = LCD_KIND_9325;
by
Code: [Select]
default:
            lcd_kind = LCD_KIND_7783;

Logged
Please don't PM me, use our IRC channel instead.

Offline metaphys

  • Member
  • *
  • Posts: 133
Re: Sansa Fuze+
« Reply #95 on: July 15, 2011, 06:56:33 AM »
Quote from: pamaury on July 15, 2011, 06:32:28 AM
If you are motivated, you could try to bisect to see which revision of the svn caused that. You can also try to change this in lcd-fuzeplus.c:
replace
Code: [Select]
default:
            lcd_kind = LCD_KIND_9325;
by
Code: [Select]
default:
            lcd_kind = LCD_KIND_7783;

I just tried this, same problem (actually as it used to work it would have been surprising)

How can I bisect ? I'm not very familiar with svn, where can I read doc about it ? is it just
Code: [Select]
man svn ?
Logged

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #96 on: July 15, 2011, 07:00:55 AM »
There is the svn-bisect tool. If you are using git, there git-bisect.
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #97 on: July 18, 2011, 12:41:07 PM »
Any news about this screen problem ?
Logged
Please don't PM me, use our IRC channel instead.

Offline metaphys

  • Member
  • *
  • Posts: 133
Re: Sansa Fuze+
« Reply #98 on: July 19, 2011, 04:56:22 AM »
Sorry but i'm again travelling around... I will tell you as soon as possible. But do you mean it works on your device? Isn't it strange?  :-\
Logged

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #99 on: July 19, 2011, 05:02:06 AM »
I *think* I would have noticed if the screen didn't work on my device :)
the only thing I changed (except if I did a mistake) is that if the type of screen is not detected, it falls back the type 9xxx instead of 7xxx (don't remember the number). So it's a bit strange :-/
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #100 on: July 19, 2011, 08:03:49 AM »
Hum, my mistake, the wiki is not up to date. Thinking about it, I made two important changes:
- one about memory layout
- one about elftosb
Be sure to have the latest elftosb complied from the SVN.

I've updated the wiki. sorry for the mess :)
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #101 on: July 27, 2011, 06:02:16 AM »
Hi all,
As you may have seen for the SVN log, I've made some progress toward actually compiling the main firmware. I've also investigated dual-boot. The good point is that it is possible to build a firmware.sb file such that the OF will upgrade itself :D That means that installing the bootloader will be easy. However, I did it on mine and dual-boot doesn't work for some rason. I do not quite understand how the OF is booting, this is weird.
Anyway, I'm still working on that.
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #102 on: August 21, 2011, 03:56:40 AM »
Hi all,
I've been in holydays for the last 3 weeks and I probably won't be able to work on the Fuze+ next week but then I'll be back. Please don't send private messages to ask for some news.
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #103 on: September 12, 2011, 03:43:11 AM »
Hi,
again some news from the port ! I'm recently reworked mainy things about memory and the bootloader. I've implemented some ADC related stuff and I'm working on battery charging (not so easy with this chip). I've also fixed the USB tricky details so the bootloader now has USB support and works perfectly. I've tweaked it so one can access either only the main partition or the whole disk (to update the bootloader). Once charging is implemented, I'll move on to the audio drivers and to the touchpad one.
As a side note, for those who are interested, Freescale released the source code of eltosb2 as well as the documentation of the sb file format on their website (download section of the IMX233, perhaps need to register).
Please note that the wiki page is *not* up to date, and I still have some non-committed stuff.
Logged
Please don't PM me, use our IRC channel instead.

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Sansa Fuze+
« Reply #104 on: September 12, 2011, 10:14:33 AM »
Hum,
I tried to flash the bootloader myself to what i thought was the bootloader partition and apparently it doesn't work. So I only have recovery mode working on my device now \o/ This is weird because either the ROM doesn't follow the documentation I have either I misunderstood it.

To recover from this situation, I would need a clean flash image. Could someone run recovery mode on some file I provide and do a partial dump of the disk ? This is completely safe and only requires linux + dd.
Thansk in advances.
Logged
Please don't PM me, use our IRC channel instead.

  • Print
Pages: 1 ... 5 6 [7] 8 9 ... 54
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Sansa Fuze+
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.109 seconds with 20 queries.