Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Vogtinator

Pages: 1 ... 73 74 [75] 76 77 ... 83
1111
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 11:28:21 am »
You are not using the right rootfs image.

1112
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 11:23:43 am »
Quote
TI's OS does not lock the LED when it's overwritten by Linux; it's just that Linux doesn't activate it.
Partially wrong: We don't know how the OS can unlock the LED. Whether the LED registers are locked is saved somewhere in hardware.

In my adc test prog I had to do the following:
Code: [Select]
*((uint32_t*)0x900B0018) = 0;
*((uint32_t*)0x900B0020) = 0;
What is this register "0x900B0020"? In nspire_emu *(0x900B0020) & 0x10 is tested, if it returns false, the adc value is 0x3ff=1023.

1113
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 10:16:55 am »
You only have to run "startx" on your calc.

BTW: 0x1ACCE551 is sent to the watchdog for unlocking, problably not related to the leds.

Edit: I can read the ADC via ndless, but the driver does still not work :-(

1114
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 07:30:27 am »
Ok, I'll try that.
Edit: Nope, zero.
I'm reading directly from 0xC4000100 + 0x10 (measured voltage) + 0x20*channel, or am I too dumb to read the wiki page?
The OS should have started a measurement already, so something should be there..
Edit2: On nspire_emu it works (ADC0 = 930), but not on the actual hardware
Edit3: In the diagnostics menu, there are some GPIOs higher than 32 (GPIO39). Why are these not mentioned in the wiki?

1115
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 07:25:28 am »
What if I make the same mistakes again and it's returning the wrong values?

1116
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 07:21:15 am »
Is there already a program for ndless to test it or I do I have to do it wrong again? :D

1117
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 02, 2012, 07:17:04 am »
Quote
Good work on the GPIO and power management interfaces though
I don't know whether it actually works..
Turning off by disabling access to all peripherals is likely to be a bug or it's not off at all, but we can't see it's actually on.
Also I don't know whether GPIOs do work, I can't test it, but some values make sense.
But what could be the cause for the adc always returning 0?

1118
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 03:42:29 pm »
FFFFFFFFFFFFUUUUUUU
I WANT TO GET OUT OF THIS HELL
BTW: No, the led's don't work, still 0x1643 (what seems absolutely right)

Edit: Maintenance Menu and cleared /documents.. I hope it boots again..
Edit2: Nope, reboot loop because of ndless_resources.tns missing..
Edit3: Reinstalling OS now..
Edit4: Didn't work, hangs at clock screen, doing complete reformat.
Edit5: Diagnostics menu -> ADC Test displays following:
ADC0: LBAT 4,07 V
ADC1: VBATT 0V <-WTF The wiki is wrong here
ADC2: VSYS 4.01V
ADC3: KBID 0.2V
ADC4: B12 0.3V
ADC5: VBUS 0.006V
ADC6: VSLED 0.09V

Edit6: YEAH Finally I'm out! Now I can test I²C!
Edit9001: Tangrs linuxloader from github doesn't work.. Only few colored pixels on top of the screen
Edit9002: Which frequency is correct for the touchpad?

1119
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 02:57:14 pm »
Ok, I'll try that, too.
But for now, I did it and GPIOs are working :D
At least GPIO 8 is low the whole time and GPIO 1 high.
Touchpad, we are coming to you  :devil:

Edit: With rootDoc it only displays "Documents (empty folder)" in press-to-test mode..
Edit 2: HELP! I can't get out of Press-to-test anymore :-( Holding ESC at startup doesn't work at all and rootdoc seems to block "Exit Test Mode.tns"
Edit 3: I tried esc twice and after that it wouldn't boot at all :-( I had to take out the battery.. But now I can send the linux kernel to "/exammode/usr/zImage.tns".

1120
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 02:33:59 pm »
Quote
Try starting linucx in Press-to-test Mode. If you put the linuxloader (or the script) in the ndless startup folder, it should be executed, even in Press-to-test Mode. I am not sure if it works with linuxloader, but other things in ndless startup folder are executed in Press-to-test Mode.
The reason why I write this, is that Norse (the cool app for morsing around with the LED, not compiled for 3.1) worked sometimes when started i Press-to-test Mode, as I read somewhere.
Yes, I knew already (guess why ;-) )

Quote
You can exit Press-to-test Mode anytime by sending a complete EMPTY file with the file name 'Exit Test Mode.tns' (just create a empty text file and rename it, but watch out, it's case-sensitive!) to the - regulary only and empty - folder in the CAS.
To start this Mode, just hold Esc+On when calc is off.
I had to do this once already, because I thought, "Press-to-test" is like a lcd- and keypad test mode.
I was like "F**k, how can I get out from here!?".

Quote
Then try your LED code again and try reading if the values in the memory are different from normal mode (they should be, even before writing new values), because the LED blinks in Press-to-test mode.
I'll try that.

Quote
Also cool news with the power management
I'd rather call that stupidity ;-)

Edit: Nope, linuxloader can't find the kernel image. At least not if I load it with "kernel linux/zImage.tns", maybe the path is different.

1121
TI-Nspire / Re: nspire Linux Questions
« on: December 01, 2012, 02:28:19 pm »
The latest version from github should work.

1122
TI-Nspire / Re: nspire Linux Questions
« on: December 01, 2012, 02:18:42 pm »
You have to do the same as with cx's.
Just there is no kernel image online for non-cx's yet, so you have to build one yourself.

1123
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 12:06:58 pm »
Not if you want to do it :P

1124
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 11:55:06 am »
ACCE55? Very funny, TI..
I just found a way how to turn the device into standby:
Code: [Select]
writel(~0, NSPIRE_APB_VIRTIO(NSPIRE_APB_POWER + 0x18));Display is off, only reset turns on (and resets). ;-)

1125
TI-Nspire / Re: Calling all Linux Kernel developers!
« on: December 01, 2012, 08:07:23 am »
The struct clcd_panel classic_lcd_panel uses values < 6 for margin's and hsync_len too, so clcdfb_check will return -EINVAL.
Could you test whether X and directfb work on touch- and clickpads?

Edit: I just wrote the driver for the adc, but reads from 0xC4000000 - 0xC40001DF (mapped to 0xfed7ee21 - 0xfed7f000) always return 0.
Frustrated I began to write a driver for the LEDs (in AHB region), but they're always off, even if I turn them on manually.
# echo 1 > /proc/red_led
Red LED turned ON
# cat /proc/red_led
Red LED is OFF
Same for green LEDs.
Could the problems be related?

Edit 2: Everytime reads from the led control register return 0x1643 (0b01011001000011: Green blink data, green iteration, red blink data, red iteration).
I think writes are just ignored.
Could the cause be
Quote
900B0018 (R/W): Disable bus access to peripherals. Reads will just return the last word read from anywhere in the address range, and writes will be ignored.
?

Pages: 1 ... 73 74 [75] 76 77 ... 83